From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yaniv Kaul Subject: Re: xp guest, blue screen c0000221 on boot Date: Wed, 28 Oct 2009 17:41:04 +0200 Message-ID: <4AE86610.3010706@redhat.com> References: <4AE6100F.6040705@memphis.edu> <4AE6BE76.2010503@redhat.com> <4AE862E9.9000701@memphis.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , "kvm@vger.kernel.org" To: Andrew Olney Return-path: Received: from mx1.redhat.com ([209.132.183.28]:26680 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752083AbZJ1PlH (ORCPT ); Wed, 28 Oct 2009 11:41:07 -0400 In-Reply-To: <4AE862E9.9000701@memphis.edu> Sender: kvm-owner@vger.kernel.org List-ID: On 10/28/2009 5:27 PM, Andrew Olney wrote: > Thanks. In pursuing this suggestion I discovered that I also can't > make new XP VMs. Setup fails with "the disk may be damaged". > > The image was created with > > qemu-img create xp_new.img 13G > > And the setup command is > > kvm -cdrom xp/xp_pro.iso -hda xp_new.img -boot d -m 512 -no-acpi -usb > -usbdevice tablet Any specific reason you are using -no-acpi ? Y. > > Avi Kivity wrote: >> On 10/26/2009 11:09 PM, Andrew Olney wrote: >>> Hangs on boot, xp guest: >>> >>> STOP: c0000221 Unknown Hard Error >>> \SystemRoot\System32\ntdll.dll >>> >>> Will boot into safe mode, but _not_ into safe mode with networking. >>> >> >> According to http://support.microsoft.com/kb/314474, this file is >> corrupted. If you have another VM with the same service pack, you >> might try copying the file over in safe mode, or you can try >> extracting it from the service pack and copying it. >> > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html