Re: [kvm-devel] Where are vmentry failure caugth?

[Anthony L. <an...@co...>]

Avi Kivity wrote:
> Guillaume Thouvenin wrote:
>   
>> On Thu, 10 Jan 2008 17:32:35 +0200
>> Avi Kivity <av...@qu...> wrote:
>>
>>   
>>     
>>> I think 33 is the error code, which means we got a general protection 
>>> fault while accessing segment 0x33.
>>>
>>> What guest code is running when this happens?  The dump sometimes 
>>> includes the current code.
>>>     
>>>       
>> When it happened I started an openSUSE-10.3 installation. Here is the complete dump:
>>     

What version of gfxboot does openSUSE 10.3 use?  gfxboot was broken for 
KVM until very recently.  This is probably what you're seeing.

Regards,

Anthony Liguori

>> [guill]$ ./qemu-system-x86_64 -hda ~/disk_images/openSUSE-10.3.qcow2 -cdrom ~/iso_images/openSUSE-10.3-GM-x86_64-mini.iso -boot d -m 1024
>> exception 13 (33)
>> rax 0000000000000671 rbx 0000000000800000 rcx 0000000000000000 rdx 00000000000013ca
>> rsi 0000000000055e1c rdi 0000000000055e1d rsp 00000000fffa0080 rbp 000000000000200b
>> r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 0000000000000000
>> r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
>> rip 000000000000b071 rflags 00033096
>> cs 4004 (00040040/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
>> ds 4004 (00040040/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
>> es 00ff (00000ff0/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
>> ss ff11 (000ff110/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
>> fs 3002 (00030020/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
>> gs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
>> tr 0000 (fffbd000/00002088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
>> ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
>> gdt 40920/47
>> idt 0/ffff
>> cr0 60000010 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
>> code: 17 06 29 4b 01 18 eb 18 a8 25 aa 19 28 4c 01 28 4d 01 01 17 --> 0f 17 0f 01 17 0f 17 12 01 17 2c 25 4b 19 21 00 02 17 1a 94 0a 76 67 61 3d 30 78 25 78 20
>> Aborted
>>
>> In the console I got:
>> [86955.117391] handle_exception: unexpected, vectoring info 0x80000306 intr info 0x80000b0d
>> [86955.193194] pending exception: not handled yet
>> [86955.219948] pending exception: not handled yet
>>   
>>     
>
> We probably need to understand the first handle_exception message; 
> things have probably gone very wrong afterwards.
>
>