From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Unable to boot guest on kernel 2.6.29.1 with kvm-84 or kvm-85 Date: Sun, 03 May 2009 15:07:44 +0300 Message-ID: <49FD8910.5070706@redhat.com> References: <43287.1241351387@kelu.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: kelu@kelu.dk Return-path: Received: from mx2.redhat.com ([66.187.237.31]:50266 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755137AbZECMIJ (ORCPT ); Sun, 3 May 2009 08:08:09 -0400 In-Reply-To: <43287.1241351387@kelu.dk> Sender: kvm-owner@vger.kernel.org List-ID: Kenni Lund wrote: >> >> It won't help - I reproduced the issue. Instead, try passing the >> parameter '-cpu qemu32' (or '-cpu qemu64,-nx'). >> > > Adding the parameter '-cpu qemu32' (32bit host + 32 bit guest) makes the WinXP guest boot. > ...but is this parameter equal to '-no-kvm'? Eg. with emulated CPU? > No, as you can tell from the speed (and 'info kvm' output). '-cpu qemu32' means use the cpu features exposed by the virtual qemu32 cpu. The default is qemu64, which includes 64-bit support and NX. Your host kernel doesn't have NX support, but qemu erronously reports that it does, causing Windows to get confused. -- error compiling committee.c: too many arguments to function