From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: What changed since kvm-72 resulting in winNT to fail to boot (STOP 0x0000001E) ? Date: Sat, 01 May 2010 00:36:51 +0400 Message-ID: <4BDB3F63.60900@msgid.tls.msk.ru> References: <4BDB3847.60107@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: KVM list Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:57499 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759194Ab0D3Ugx (ORCPT ); Fri, 30 Apr 2010 16:36:53 -0400 In-Reply-To: <4BDB3847.60107@msgid.tls.msk.ru> Sender: kvm-owner@vger.kernel.org List-ID: 01.05.2010 00:06, Michael Tokarev wrote: > I've a bugreport handy, see > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575439 > about the apparent problem booting winNT 4 in kvm 0.12. > At least 2 people were hit by this issue. In short, when > booting winNT 4.0, it BSODs with error code 0x0000001E, > which means "inaccessible boot device". > > Note that it is when upgrading from -72 to 0.12. But the > second person on the bug page also tried to reinstall the > OS, and that failed as well, now with a different error > message. > > I'll try to find an nt4 cdrom here to try it, but I can't > promise anything.... I found an old winNT-4.0 install CD-Rom and tried that. But it stops right at "Inspecting your hardware configuration" stage, with the error: "STOP: 0x0000003E" (BSOD). According to MS -- http://msdn.microsoft.com/en-us/library/ms819006.aspx -- this means "multiprocessor configuration is not supported. For example, not all processors are at the same level or of the same type. There might also be mismatched coprocessor support." Obviously I'm running it with -smp 1, here's the complete kvm command line: kvm -hda winNT.raw -m 512 -cdrom Win_NT_4_Enterprise.iso -localtime -vga std (with default vga - cirrus - it displays garbage) And the complete BSOD: http://www.corpit.ru/mjt/winnt4_1.gif > Thanks! > > /mjt