From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1 Date: Thu, 07 Jan 2010 10:50:34 +0200 Message-ID: <4B45A05A.5020304@redhat.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Mark Cave-Ayland Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50362 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752604Ab0AGIul (ORCPT ); Thu, 7 Jan 2010 03:50:41 -0500 In-Reply-To: <4B44B018.90003@siriusit.co.uk> Sender: kvm-owner@vger.kernel.org List-ID: On 01/06/2010 05:45 PM, Mark Cave-Ayland wrote: > Avi Kivity wrote: > >> It probably did make some kind of difference. Please try a clean >> install. > > After several hours of testing, I've finally found out what the > problem is. > > I tried a clean WinXP guest install and that worked, so it was > obviously a driver issue. After disabling various drivers in the WinXP > guest, I didn't get anywhere so I decided to take a break and test > Marcelo's VNC patch. With this applied, I could actually see all of > the information in the BSOD which showed the error was in intelppm.sys. > > A quick search took me to this page here: > http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/24/484461.aspx > which explains the issue in more detail. I first tried disabling the > intelppm driver and rebooting, but that didn't make a difference; > however disabling the Processor driver worked and my guest VM booted > in Normal Mode :) > > 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? -- error compiling committee.c: too many arguments to function