From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andre Przywara Subject: Re: Booting/installing WindowsNT Date: Tue, 4 May 2010 14:08:10 +0200 Message-ID: <4BE00E2A.2010901@amd.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> <4BDFE3A7.2050706@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: Michael Tokarev , KVM list To: Avi Kivity Return-path: Received: from tx2ehsobe002.messaging.microsoft.com ([65.55.88.12]:36618 "EHLO TX2EHSOBE003.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753562Ab0EDMLo (ORCPT ); Tue, 4 May 2010 08:11:44 -0400 In-Reply-To: <4BDFE3A7.2050706@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > 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. I managed to get a NT4 CD and can acknowledge the issues you see. I am about to debug this now. With -cpu host (on a AMD K8, similar to Michael's) I get to the point Michael mentioned: Microsoft (R) Windows NT (TM) Version 4.0 (Build 1381). 1 System Processor [512 MB Memory] Multiprocessor Kernel Then it _seems_ to hang, checking for getting beyond a certain TSC value in a tight loop. (rdtsc; cmp %edx, %edi; ja @rdtsc; jb bailout; cmp %eax, %ebx; ja @rdtsdc; bailout:) But after some time (when I got back from the monitor, but also without going into) I could proceed with the installation. Michael, can you confirm this? I will now try to get behind the STOP 3E error. Regards, Andre. -- Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 448-3567-12