From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Cave-Ayland Subject: Re: WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1 Date: Thu, 07 Jan 2010 09:55:45 +0000 Message-ID: <4B45AFA1.6090008@siriusit.co.uk> References: <4B43643F.8090303@siriusit.co.uk> <4B4373A8.8050807@redhat.com> <4B44731A.4020405@siriusit.co.uk> <4B448513.6070505@redhat.com> <4B448715.9000602@siriusit.co.uk> <4B4489F5.4000409@redhat.com> <4B44B018.90003@siriusit.co.uk> <4B45A05A.5020304@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from ra.siriusit.co.uk ([217.207.197.130]:49197 "EHLO ra.siriusit.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751468Ab0AGJ4A (ORCPT ); Thu, 7 Jan 2010 04:56:00 -0500 In-Reply-To: <4B45A05A.5020304@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 :( HTH, Mark. -- Mark Cave-Ayland - Senior Technical Architect PostgreSQL - PostGIS Sirius Corporation plc - control through freedom http://www.siriusit.co.uk t: +44 870 608 0063 Sirius Labs: http://www.siriusit.co.uk/labs