Re: Where are vmentry failure caugth?

[Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>]

Guillaume Thouvenin wrote:
> On Thu, 10 Jan 2008 11:19:58 +0100
> Guillaume Thouvenin <guillaume.thouvenin-Z51IpKcfGtLk1uMJSBkQmQ@public.gmane.org> wrote:
>
>   
>>   I tried but it didn't catch any vmentry failures (and I know that
>> there is at least one during the test).
>>     
>
>   I think that there is a vmentry failure because qemu-system-x86_64
> crashes with following error:
> "exception 13 (33)"
>
>   I interpreted this as a vmentry failure because 33 is the exit reason
> for a vmentry failure. The problem is that I don't find how to catch it
> in kvm. I thought that something like:
>   

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.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
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