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: Wed, 06 Jan 2010 14:41:55 +0200 Message-ID: <4B448513.6070505@redhat.com> References: <4B43643F.8090303@siriusit.co.uk> <4B4373A8.8050807@redhat.com> <4B44731A.4020405@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]:16184 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752987Ab0AFMmG (ORCPT ); Wed, 6 Jan 2010 07:42:06 -0500 In-Reply-To: <4B44731A.4020405@siriusit.co.uk> Sender: kvm-owner@vger.kernel.org List-ID: On 01/06/2010 01:25 PM, Mark Cave-Ayland wrote: > Good news - I downloaded the userspace git repository and managed to > identify the offending commit between 0.12.1.1 and 0.12.1.2 using git > bisect: > > > 4dad7ff32aa6dcf18cef0c606d8fb43ff0b939a1 is first bad commit > commit 4dad7ff32aa6dcf18cef0c606d8fb43ff0b939a1 > Author: Avi Kivity > Date: Mon Dec 28 10:48:00 2009 +0200 > > Reinstate cpuid vendor override when kvm is enabled > > Due to upstream qemu changes we no longer expose the host cpu > vendor id > to the guest. This leads to failures when the syscall/sysenter > instructions > are used in compatibility mode. > > Change the default to override when kvm is enabled. > > Signed-off-by: Avi Kivity > Signed-off-by: Marcelo Tosatti > Did you install using 0.12.1.1 and then run using 0.12.1.2? If so, it seems Windows XP is not able to move from AMD to Intel. -- error compiling committee.c: too many arguments to function