Another "unhandled vm exit: 0x9"

Another "unhandled vm exit: 0x9"

[Weiyang Chen]

[-- Attachment #1.1: Type: text/plain, Size: 653 bytes --]

Hi,

I build kvm-35 from tarball successfully  on my Macbook core2due with a
2.6.22.3 kernel, Ubuntu 7.04. But when I try to start kvm with a Windows XP
image, it gets crushed with a  "unhandled vm exit:  0x9" error. Here are the
last 2 lines from dmesg:

kvm: guest NX capability removed
kvm_handle_exit: unexpected, valid vectoring info and exit reason is 0x9

I also have dig this maillist, and found this thread:
http://www.mail-archive.com/kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org/msg01940.html

But since the guest OS I used is windows xp, it shouldn't use "a hardware
task switch mechanism".

Any comments from you? Thank you!

[-- Attachment #1.2: Type: text/html, Size: 890 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: Another "unhandled vm exit: 0x9"

[Izik Eidus]

On Fri, 2007-08-17 at 22:38 +0800, Weiyang Chen wrote:
> Hi,
> 
> I build kvm-35 from tarball successfully  on my Macbook core2due with
> a 2.6.22.3 kernel, Ubuntu 7.04. But when I try to start kvm with a
> Windows XP image, it gets crushed with a  "unhandled vm exit:  0x9"
> error. Here are the last 2 lines from dmesg: 
> 
did it work to you in older kvm versions?

> kvm: guest NX capability removed
> kvm_handle_exit: unexpected, valid vectoring info and exit reason is
> 0x9

> I also have dig this maillist, and found this thread:
> http://www.mail-archive.com/kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org/msg01940.html
> 
> But since the guest OS I used is windows xp, it shouldn't use "a 
> hardware task switch mechanism".
> 

your host is 32 or 64bits plus what edition of windows xp is it and is
it 32 ot 64 bits?

> Any comments from you? Thank you! 
> 

windows xp should not do any task switch, it is probably bug, try to
provide more information like when is it crush,
was it in the installation, or in normal usage?, is it working with
--no-kvm?
 

> 
> 
> -------------------------------------------------------------------------
> 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/
> _______________________________________________ kvm-devel mailing list kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/kvm-devel


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

Re: Another "unhandled vm exit: 0x9"

[Avi Kivity]

Weiyang Chen wrote:
> Hi,
>
> I build kvm-35 from tarball successfully  on my Macbook core2due with 
> a 2.6.22.3 <http://2.6.22.3> kernel, Ubuntu 7.04. But when I try to 
> start kvm with a Windows XP image, it gets crushed with a  "unhandled 
> vm exit:  0x9" error. Here are the last 2 lines from dmesg:
>
> kvm: guest NX capability removed
> kvm_handle_exit: unexpected, valid vectoring info and exit reason is 0x9
>
> I also have dig this maillist, and found this thread: 
> http://www.mail-archive.com/kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org/msg01940.html
>
> But since the guest OS I used is windows xp, it shouldn't use "a 
> hardware task switch mechanism".

A hardware task switch is sometimes used when a guest detects a serious 
error and wants to switch to a known condition.  Sometimes it happens 
accidentally due to a previous error.

Was this image installed using kvm?  What HAL does it use?



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

Re: Another "unhandled vm exit: 0x9"

[Weiyang Chen]

[-- Attachment #1.1: Type: text/plain, Size: 94 bytes --]

Hi,

I rebuild a image with new kvm. Then I find it works!
Thanks a lot for your kindly help!

[-- Attachment #1.2: Type: text/html, Size: 115 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: Another "unhandled vm exit: 0x9"

[Cam Macdonell]

Avi Kivity wrote:
> Weiyang Chen wrote:
> 
> A hardware task switch is sometimes used when a guest detects a serious 
> error and wants to switch to a known condition.  Sometimes it happens 
> accidentally due to a previous error.
> 
> Was this image installed using kvm?  What HAL does it use?
> 

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?

I still have it around if you would like me to do some debugging with it.

Cam

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

Re: Another "unhandled vm exit: 0x9"

[Avi Kivity]

Cam Macdonell wrote:
> Avi Kivity wrote:
>> Weiyang Chen wrote:
>>
>> A hardware task switch is sometimes used when a guest detects a 
>> serious error and wants to switch to a known condition.  Sometimes it 
>> happens accidentally due to a previous error.
>>
>> Was this image installed using kvm?  What HAL does it use?
>>
>
> 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 still have it around if you would like me to do some debugging with it.
>

Can you check which kvm version caused the regression?


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

Re: Another "unhandled vm exit: 0x9"

[Cam Macdonell]

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

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.

Let me know if you have any more questions,

Cam

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

Re: Another "unhandled vm exit: 0x9"

[Avi Kivity]

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/

Re: Another "unhandled vm exit: 0x9"

[Avi Kivity]

Avi Kivity wrote:
> 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.

BTW, you can use -no-kvm (or an older kvm) to switch to the Standard PC 
HAL.  But please keep a copy of the failing image for future testing.

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