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: Wed, 05 May 2010 14:05:45 +0400 Message-ID: <4BE142F9.4090807@msgid.tls.msk.ru> References: <4BDB3847.60107@msgid.tls.msk.ru> <4BDD1678.1070509@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list To: Avi Kivity Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:60568 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932398Ab0EEKFr (ORCPT ); Wed, 5 May 2010 06:05:47 -0400 In-Reply-To: <4BDD1678.1070509@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 02.05.2010 10:06, Avi Kivity wrote: > 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 [...] > > What about 0.11? Does it work? After finding the cause of the other problem (in the thread "Booting/Installing Windows NT", all thanks going to Andre Przywara), I can proceed with this issue finally. I tried installing winNT here on old kvm and upgrading kvm. So far I can say that if winNT were installed with kvm-72 and later, it boots just fine in kvm-0.12. So I don't know what the problem is in this case. Maybe it is becauese the OP installed his winNT guest before kvm-72 and now in 0.12 the guest is not able to find its filesystem anymore, or maybe it's because there was some bug fixed in service pack 1 (which I used here) that makes the problem go away - I dunno. But having in mind how picky winNT was for the hardware changes, I don't think it's worth the effort to debug this problem further - winNT is really ancient system, and having upgrade path for kvm from some ancient development snapshot to current version isn't that important, IMHO. Yes, a few people will be hit by this issue, which is a sad thing, but seriously, we've more interesting things to do ;) Thanks! /mjt