Re: Another "unhandled vm exit: 0x9"

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

Cam Macdonell wrote:
> Avi Kivity wrote:
>> Cam Macdonell wrote:
>>> Avi Kivity wrote:
>>>
>>> Hi,
>>>
>>> I had this same problem.  I have an old XP image that would not run 
>>> under kvm-35.  It was installed with the kvm that is packaged with 
>>> Ubuntu Feisty (kvm-27, I believe).  After I upgraded, it crashes 
>>> during boot.
>>>
>>> How can I check the HAL it uses?
>>>
>> Windows device manager, under 'Computer'.
>
> I see MPS Uniprocessor PC.  This image was installed with kvm.
>
>>> I still have it around if you would like me to do some debugging 
>>> with it.
>>
>> Can you check which kvm version caused the regression?
>
> It works under KVM-16 (which is the version that ships with Feisty) 
> and up to kvm-24 (I did a manual binary search so a few versions were 
> skipped).  versions 25, 26, 27 stall at boot (I wait several minutes 
> but Windows never starts) and crashing with "unhandled vm exit: 0x9" 
> happens with KVM-33.  I'm not on which precise version where the 
> crashing begins (let me know if that would be useful).

That should be enough to start debugging.  However, with the kvm forum 
next week, I doubt it will happen soon.

>
> A possibly unimportant note, I noticed that the later versions (above 
> 27) compile the executable as "qemu-system-x86_64" where as earlier 
> versions build it as "qemu".  My system is a Centrino Duo, so it's a 
> i386.  I'm not sure if this matters but I just thought I would mention 
> it.
>

It is likely related.  You can check it by changing 'echo x86_64' to 
'echo i386' in ./configure.


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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/