public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Guillaume Thouvenin
	<guillaume.thouvenin-Z51IpKcfGtLk1uMJSBkQmQ@public.gmane.org>
Subject: Re: Where are vmentry failure caugth?
Date: Sat, 12 Jan 2008 14:34:12 -0600	[thread overview]
Message-ID: <47892444.2070903@codemonkey.ws> (raw)
In-Reply-To: <47891F36.1080903-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Avi Kivity wrote:
> Guillaume Thouvenin wrote:
>   
>> On Thu, 10 Jan 2008 17:32:35 +0200
>> Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> 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.
>
>   


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

  parent reply	other threads:[~2008-01-12 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 10:19 Where are vmentry failure caugth? Guillaume Thouvenin
2008-01-10 14:26 ` Guillaume Thouvenin
2008-01-10 15:32   ` Avi Kivity
     [not found]     ` <47863A93.2030707-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-11  7:44       ` Guillaume Thouvenin
2008-01-12 20:12         ` Avi Kivity
     [not found]           ` <47891F36.1080903-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-12 20:34             ` Anthony Liguori [this message]
     [not found]               ` <47892444.2070903-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2008-01-14  7:11                 ` Guillaume Thouvenin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47892444.2070903@codemonkey.ws \
    --to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=guillaume.thouvenin-Z51IpKcfGtLk1uMJSBkQmQ@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox