From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Booting/installing WindowsNT Date: Tue, 04 May 2010 12:06:47 +0300 Message-ID: <4BDFE3A7.2050706@redhat.com> References: <4BDB44C2.7090204@msgid.tls.msk.ru> <4BDB4E58.50805@msgid.tls.msk.ru> <4BDD4E32.2080503@redhat.com> <4BDDA455.8090001@msgid.tls.msk.ru> <4BDE882F.5000009@amd.com> <4BDE8DF4.8070604@redhat.com> <4BDE9757.8090809@amd.com> <4BDF01CA.80505@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andre Przywara , KVM list To: Michael Tokarev Return-path: Received: from mx1.redhat.com ([209.132.183.28]:41432 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757304Ab0EDJG7 (ORCPT ); Tue, 4 May 2010 05:06:59 -0400 In-Reply-To: <4BDF01CA.80505@msgid.tls.msk.ru> Sender: kvm-owner@vger.kernel.org List-ID: On 05/03/2010 08:03 PM, Michael Tokarev wrote: >> Michael, can you try to use -cpu host,-vme and see if that makes a >> difference? > > > With -cpu host,-vme winNT boots just fine as with just -cpu host. > > I also tried with -cpu qemu64 and kvm64, with +vme and -vme (4 > combinations in total) - in all cases winNT crashes with the > same 0x0000003E error. So it appears that vme makes no > difference. Please try again the model/vendor/family. I suggest using x86info on both to see what the differences are, using -cpu host with overrides to make it equivalent to qemu64 (and verifying it fails), then removing the overrides one by one until it works. -- error compiling committee.c: too many arguments to function