From: Avi Kivity <avi@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
Cc: kvm@vger.kernel.org
Subject: Re: WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1
Date: Sun, 24 Jan 2010 09:40:58 +0200 [thread overview]
Message-ID: <4B5BF98A.5040408@redhat.com> (raw)
In-Reply-To: <4B45AFA1.6090008@siriusit.co.uk>
On 01/07/2010 11:55 AM, Mark Cave-Ayland wrote:
> Avi Kivity wrote:
>
>>> I think the issue is probably similar to that explained in the
>>> article above; with a new processor reported to the guest, the
>>> internal processor driver tries to upload some kind of microcode to
>>> the new device which fails and causes the guest to fall over. Can we
>>> teach KVM to silently discard these kinds of updates?
>>>
>>
>> Can you try loading kvm.ko with the ignore_msrs module parameter set?
>
> Hi Avi,
>
> I've just done a quick test re-enabling processor.sys on my WinXP
> guest and then did the following:
>
> virsh stop winxp
> rmmod kvm_intel
> rmmod kvm
> modprobe kvm ignore_msrs=1
> modprobe kvm_intel
> virsh start winxp
>
> Unfortunately it still crashes with the same
> "DRIVER_UNLOADED_WITHOUT_CANCELING_PENDING_OPERATIONS" BSOD :(
Well, don't do that then. Is there any specific functionality in
processor.sys that you're missing?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-01-24 7:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 16:09 WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1 Mark Cave-Ayland
2010-01-05 17:15 ` Avi Kivity
2010-01-05 17:25 ` Mark Cave-Ayland
2010-01-06 11:25 ` Mark Cave-Ayland
2010-01-06 12:29 ` Marcelo Tosatti
2010-01-06 12:33 ` Gleb Natapov
2010-01-06 12:39 ` Gleb Natapov
2010-01-06 12:46 ` Mark Cave-Ayland
2010-01-06 12:41 ` Avi Kivity
2010-01-06 12:50 ` Mark Cave-Ayland
2010-01-06 12:54 ` Gleb Natapov
2010-01-06 13:14 ` Mark Cave-Ayland
2010-01-06 13:47 ` Yaniv Kaul
2010-01-06 12:56 ` Gleb Natapov
2010-01-06 13:02 ` Avi Kivity
2010-01-06 15:45 ` Mark Cave-Ayland
2010-01-06 17:08 ` Mark Cave-Ayland
2010-01-07 8:51 ` Avi Kivity
2010-01-07 9:57 ` Mark Cave-Ayland
2010-01-07 12:34 ` Avi Kivity
2010-01-07 8:50 ` Avi Kivity
2010-01-07 9:55 ` Mark Cave-Ayland
2010-01-24 7:40 ` Avi Kivity [this message]
2010-01-25 15:15 ` Mark Cave-Ayland
2010-01-25 15:27 ` Avi Kivity
2010-01-25 16:06 ` Mark Cave-Ayland
2010-01-25 16:09 ` Avi Kivity
2010-01-25 16:18 ` Mark Cave-Ayland
2010-01-25 16:22 ` Avi Kivity
2010-01-25 16:54 ` Mark Cave-Ayland
2010-01-25 17:37 ` Avi Kivity
2010-01-25 22:25 ` Mark Cave-Ayland
2010-01-26 6:18 ` Avi Kivity
2010-01-26 9:56 ` Mark Cave-Ayland
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=4B5BF98A.5040408@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mark.cave-ayland@siriusit.co.uk \
/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