From: Yaniv Kaul <ykaul@redhat.com>
To: Andrew Olney <aolney@memphis.edu>
Cc: Avi Kivity <avi@redhat.com>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: xp guest, blue screen c0000221 on boot
Date: Wed, 28 Oct 2009 17:41:04 +0200 [thread overview]
Message-ID: <4AE86610.3010706@redhat.com> (raw)
In-Reply-To: <4AE862E9.9000701@memphis.edu>
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
next prev parent reply other threads:[~2009-10-28 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 21:09 xp guest, blue screen c0000221 on boot Andrew Olney
2009-10-27 9:33 ` Avi Kivity
2009-10-28 15:27 ` Andrew Olney
2009-10-28 15:32 ` Avi Kivity
2009-11-04 0:18 ` Andrew Olney
2009-11-04 3:45 ` Andrew Olney
2009-11-04 7:39 ` Avi Kivity
2009-11-04 17:06 ` Andrew Olney
2009-11-08 12:15 ` Avi Kivity
2009-11-09 16:26 ` Andrew Olney
2009-10-28 15:41 ` Yaniv Kaul [this message]
2009-10-29 10:29 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE86610.3010706@redhat.com \
--to=ykaul@redhat.com \
--cc=aolney@memphis.edu \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.