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:57:33 +0000 Message-ID: <4B45B00D.6000103@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> <4B44C3AA.1000308@siriusit.co.uk> <4B45A080.4060305@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]:49217 "EHLO ra.siriusit.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751185Ab0AGJ5q (ORCPT ); Thu, 7 Jan 2010 04:57:46 -0500 In-Reply-To: <4B45A080.4060305@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: >> I've just re-created the KVM image fresh from the VDI image once again >> and can confirm that disabling just the Processor driver is enough to >> allow the guest WinXP VM to function in qemu-kvm-0.12.1.2. Perhaps the >> default for "-cpu host" should not be changed in a micro release as >> there is a risk of breaking existing VMs? >> > > That was actually a fix for a regression relative to 0.11. Really? Damn :( Any pointers towards the relevant bug in the bug tracker? ATB, 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