From: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Another "unhandled vm exit: 0x9"
Date: Thu, 23 Aug 2007 09:47:56 -0600 [thread overview]
Message-ID: <46CDAC2C.6020709@cs.ualberta.ca> (raw)
In-Reply-To: <46CBF9E4.1020505-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
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/
next prev parent reply other threads:[~2007-08-23 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 14:38 Another "unhandled vm exit: 0x9" Weiyang Chen
[not found] ` <fd587d7f0708170738v45594ebdp77b43eef3f59b06a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-17 16:51 ` Izik Eidus
2007-08-19 8:47 ` Avi Kivity
[not found] ` <46C803A8.2020102-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-21 21:23 ` Cam Macdonell
[not found] ` <46CB57D8.5070500-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-08-22 8:55 ` Avi Kivity
[not found] ` <46CBF9E4.1020505-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-23 15:47 ` Cam Macdonell [this message]
[not found] ` <46CDAC2C.6020709-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-08-23 16:09 ` Avi Kivity
[not found] ` <46CDB143.1090602-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-23 16:18 ` Avi Kivity
2007-08-21 14:16 ` Weiyang Chen
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=46CDAC2C.6020709@cs.ualberta.ca \
--to=cam-edfdblatwiyxbbii50afww@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.