From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: What changed since kvm-72 resulting in winNT to fail to boot (STOP 0x0000001E) ? Date: Sun, 02 May 2010 09:06:48 +0300 Message-ID: <4BDD1678.1070509@redhat.com> References: <4BDB3847.60107@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list To: Michael Tokarev Return-path: Received: from mx1.redhat.com ([209.132.183.28]:55533 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754891Ab0EBGGy (ORCPT ); Sun, 2 May 2010 02:06:54 -0400 In-Reply-To: <4BDB3847.60107@msgid.tls.msk.ru> Sender: kvm-owner@vger.kernel.org List-ID: On 04/30/2010 11:06 PM, 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. > What about 0.11? Does it work? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.