> On 12/14/2009 09:04 AM, Luiz Capitulino wrote: >> On Sat, 12 Dec 2009 11:09:38 -0700 >> "David S. Ahern" <[email protected]> wrote: >> >>> Thanks for the responses. I had forgotten that SIGABRT==abort() which >>> means I have to get the core file to get to the root cause. To date the >>> only information I have is a shell exit status of 134 which from the >>> bash man pages means it died due to SIGABRT. >> >> Are you using qemu-kvm or upstream qemu? Which version? Don't you >> have any procedure which would make the bug more likely to happen? >> >> Thanks.
I still have not been able to capture a core, but I did get this from stderr: unhandled vm exit: 0x31 vcpu_id 3 ax 0000000000000000 rbx 00000000c0109120 rcx 0000000000000000 rdx 00000000c9ee2000 rsi 00000000c9ee2000 rdi 00000000c9ee2000 rsp 00000000c9ee3fb0 rbp 00000000c0109120 r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 00000000c0109149 rflags 00000246 cs 0060 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0) ds 0068 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) es 0068 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) ss 0068 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) fs 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gs 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) tr 0070 (c0433300/000000eb p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0078 (fff5c000/00000027 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt c0384300/ff idt c0436000/7ff cr0 8005003b cr2 ad2f77a0 cr3 36e72440 cr4 6f0 cr8 0 efer 800 David -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
