Hi,

the 2013-12-31 snapshot iso images don't work for me under qemu 1.7.0 
/ linux 3.12.6. They get this far and then reboot:

loadrandom: cd0a:/etc/random.seed
cannot open cd0a:/etc/random.seed
loadrandom: error -1
booting cd0a:/5.4/i386/bsd.rd: 6038744+426300 
[72+233616+222178]=0x699c6c
entry point at 0x210073


I have tried both i386 and amd64. sha256:
bdb45f421d4108ebf8da6896f23a1b23e81c968782e41da5529bce4d3146e5fa  
install54-amd64-snapshot-2013-12-31.iso
bbc58d620aff0d5f6c97c6d193c1646754c5479296b97a2ebb468729e8aa0c30  
install54-i386-snapshot-2013-12-31.iso

I still have snapshots isos from 2013-09-22 lying around, and those 
continue to work. Therefore I believe it is not a qemu/kvm problem.

The last things happening before the reboot seem to be these (amd64 
iso):

kvm_emulate_insn: 40120:1168:67 66 0f 01 15 88 0f 00 00 (real)                  
                                                                             
kvm_emulate_insn: 40120:1171:0f 20 c0 (real)                                    
                                                                             
kvm_emulate_insn: 40120:1174:66 83 c8 01 (real)                                 
                                                                             
kvm_emulate_insn: 40120:1178:0f 22 c0 (real)                                    
                                                                             
kvm_emulate_insn: 40120:117b:66 ea a3 12 04 00 08 00 (prot16)                   
                                                                             
kvm_emulate_insn: 0:412a3:b8 10 00 00 00 (prot32)                               
                                                                             
kvm_emulate_insn: 0:412a8:8e d8 (prot32)                                        
                                                                             
kvm_emulate_insn: 0:412aa:8e d0 (prot32)                                        
                                                                             
kvm_emulate_insn: 0:412ac:8e c0 (prot32)                                        
                                                                             
kvm_exit: reason EPT_VIOLATION rip 0x1010149 info 182 0                         
                                                                             
kvm_page_fault: address 15e8050 error_code 182                                  
                                                                             
kvm_exit: reason CPUID rip 0x10101ae info 0 0
kvm_cpuid: func 0 rax 4 rbx 756e6547 rcx 6c65746e rdx 49656e69
kvm_exit: reason CPUID rip 0x10101cf info 0 0
kvm_cpuid: func 1 rax 623 rbx 800 rcx 80802001 rdx 78bfbfd
kvm_exit: reason CPUID rip 0x10101e7 info 0 0
kvm_cpuid: func a rax 0 rbx 0 rcx 0 rdx 0
kvm_exit: reason CPUID rip 0x10101ff info 0 0
kvm_cpuid: func 80000001 rax 623 rbx 0 rcx 1 rdx 2191abfd
kvm_exit: reason CPUID rip 0x1010212 info 0 0
kvm_cpuid: func 80000007 rax 0 rbx 0 rcx 0 rdx 0
kvm_exit: reason CR_ACCESS rip 0x101042b info 4 0
kvm_cr: cr_write 4 = 0x6b0
kvm_exit: reason MSR_READ rip 0x1010433 info 0 0
kvm_msr: msr_read c0000080 = 0x0
kvm_exit: reason MSR_WRITE rip 0x101043c info 0 0
kvm_msr: msr_write c0000080 = 0x101
kvm_exit: reason CR_ACCESS rip 0x1010440 info 3 0
kvm_cr: cr_write 3 = 0x1b2b000
kvm_exit: reason CR_ACCESS rip 0x101044b info 0 0
kvm_cr: cr_write 0 = 0x8001003b
kvm_exit: reason TRIPLE_FAULT rip 0x101045d info 0 0
kvm_userspace_exit: reason KVM_EXIT_SHUTDOWN (8)
kvm_userspace_exit: reason restart (4)

Not sure if this is related to the actual problem or just the reboot 
after the problem happened earlier.


Cheers,
Stefan

Reply via email to