* xp guest, blue screen c0000221 on boot
@ 2009-10-26 21:09 Andrew Olney
2009-10-27 9:33 ` Avi Kivity
0 siblings, 1 reply; 12+ messages in thread
From: Andrew Olney @ 2009-10-26 21:09 UTC (permalink / raw)
To: kvm
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.
Boots into non-MS VMs fine.
* what cpu model (examples: Intel Core Duo, Intel Core 2 Duo, AMD
Opteron 2210). See /proc/cpuinfo if you're not sure.
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU L2400 @ 1.66GHz
stepping : 8
cpu MHz : 1000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc
arch_perfmon bts pni monitor vmx est tm2 xtpr pdcm
bogomips : 3324.92
clflush size : 64
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU L2400 @ 1.66GHz
stepping : 8
cpu MHz : 1000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc
arch_perfmon bts pni monitor vmx est tm2 xtpr pdcm
bogomips : 3324.97
clflush size : 64
power management:
* what kvm version you are using. If you're using git directly,
provide the output of 'git describe'.
Same behavior with ubuntu package 0.11.0-0ubuntu6 (karmic)
and source qemu-kvm-0.11.0
* the host kernel version
Linux monkamu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC
2009 i686 GNU/Linux
* what host kernel arch you are using (i386 or x86_64)
i386
* what guest you are using, including OS type (Linux, Windows,
Solaris, etc.), bitness (32 or 64), kernel version
XP Pro 32 SP 3
* the qemu command line you are using to start the guest
kvm -cpu coreduo,-nx -hda /z/xp.img -boot c -usb -usbdevice tablet -m 512
* whether the problem goes away if using the -no-kvm-irqchip or
-no-kvm-pit switch.
No
* whether the problem also appears with the -no-kvm switch.
No
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
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
0 siblings, 1 reply; 12+ messages in thread
From: Avi Kivity @ 2009-10-27 9:33 UTC (permalink / raw)
To: Andrew Olney; +Cc: kvm
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.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
2009-10-27 9:33 ` Avi Kivity
@ 2009-10-28 15:27 ` Andrew Olney
2009-10-28 15:32 ` Avi Kivity
` (2 more replies)
0 siblings, 3 replies; 12+ messages in thread
From: Andrew Olney @ 2009-10-28 15:27 UTC (permalink / raw)
To: Avi Kivity; +Cc: kvm
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
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.
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
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-10-28 15:41 ` Yaniv Kaul
2009-10-29 10:29 ` Gerd Hoffmann
2 siblings, 2 replies; 12+ messages in thread
From: Avi Kivity @ 2009-10-28 15:32 UTC (permalink / raw)
To: Andrew Olney; +Cc: kvm
On 10/28/2009 05: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
What happens if you use a new qcow2 disk? Does it fail in the same way?
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
2009-10-28 15:27 ` Andrew Olney
2009-10-28 15:32 ` Avi Kivity
@ 2009-10-28 15:41 ` Yaniv Kaul
2009-10-29 10:29 ` Gerd Hoffmann
2 siblings, 0 replies; 12+ messages in thread
From: Yaniv Kaul @ 2009-10-28 15:41 UTC (permalink / raw)
To: Andrew Olney; +Cc: Avi Kivity, kvm
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
2009-10-28 15:27 ` Andrew Olney
2009-10-28 15:32 ` Avi Kivity
2009-10-28 15:41 ` Yaniv Kaul
@ 2009-10-29 10:29 ` Gerd Hoffmann
2 siblings, 0 replies; 12+ messages in thread
From: Gerd Hoffmann @ 2009-10-29 10:29 UTC (permalink / raw)
To: Andrew Olney; +Cc: Avi Kivity, kvm
On 10/28/09 16:27, 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
I had trouble getting winxp installed within kvm too. Stopped with all
sorts of funny errors depending on how I started it (with/without acpi,
...). Don't remember the exact errors, but one disk-related was among them.
Happended only on my AMD box though, on the Intel machine it worked
fine. Both ran a quite simliar setup (Fedora 11). Which made me
suspect hardware problems. Tried to upgrade the BIOS -> works fine now.
HTH,
Gerd
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
2009-10-28 15:32 ` Avi Kivity
@ 2009-11-04 0:18 ` Andrew Olney
2009-11-04 3:45 ` Andrew Olney
1 sibling, 0 replies; 12+ messages in thread
From: Andrew Olney @ 2009-11-04 0:18 UTC (permalink / raw)
To: Avi Kivity; +Cc: kvm
Thanks for the suggestion. I've successfully installed on a new qcow2 image.
Strangely all of my xp raw images no longer work. That makes me think
that this is more than just a corrupt image.
I've been using kvm for several years with raw images, so I don't think
the BIOS could be a factor either.
If there's a way to get my raw images to work, that would be nice. I'm
trying to convert one of the raw images to qcow2 -- perhaps that will work.
Avi Kivity wrote:
> On 10/28/2009 05: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
>
> What happens if you use a new qcow2 disk? Does it fail in the same way?
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
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
1 sibling, 1 reply; 12+ messages in thread
From: Andrew Olney @ 2009-11-04 3:45 UTC (permalink / raw)
To: Avi Kivity; +Cc: kvm
OK, if I convert the raw image to qcow2, it boots fine.
Why should a raw image give a blue screen?
Avi Kivity wrote:
> On 10/28/2009 05: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
>
> What happens if you use a new qcow2 disk? Does it fail in the same way?
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
2009-11-04 3:45 ` Andrew Olney
@ 2009-11-04 7:39 ` Avi Kivity
2009-11-04 17:06 ` Andrew Olney
0 siblings, 1 reply; 12+ messages in thread
From: Avi Kivity @ 2009-11-04 7:39 UTC (permalink / raw)
To: Andrew Olney; +Cc: kvm
On 11/04/2009 05:45 AM, Andrew Olney wrote:
> OK, if I convert the raw image to qcow2, it boots fine.
>
> Why should a raw image give a blue screen?
Sounds like a serious bug. What is the host filesystem? Did you
upgrade the host kernel or qemu?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
2009-11-04 7:39 ` Avi Kivity
@ 2009-11-04 17:06 ` Andrew Olney
2009-11-08 12:15 ` Avi Kivity
0 siblings, 1 reply; 12+ messages in thread
From: Andrew Olney @ 2009-11-04 17:06 UTC (permalink / raw)
To: Avi Kivity; +Cc: kvm
Host is ext3
Linux monkamu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC
2009 i686 GNU/Linux
QEMU PC emulator version 0.11.0 (qemu-kvm-0.11.0), Copyright (c)
2003-2008 Fabrice Bellard
Avi Kivity wrote:
> On 11/04/2009 05:45 AM, Andrew Olney wrote:
>> OK, if I convert the raw image to qcow2, it boots fine.
>>
>> Why should a raw image give a blue screen?
>
> Sounds like a serious bug. What is the host filesystem? Did you
> upgrade the host kernel or qemu?
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
2009-11-04 17:06 ` Andrew Olney
@ 2009-11-08 12:15 ` Avi Kivity
2009-11-09 16:26 ` Andrew Olney
0 siblings, 1 reply; 12+ messages in thread
From: Avi Kivity @ 2009-11-08 12:15 UTC (permalink / raw)
To: Andrew Olney; +Cc: kvm
On 11/04/2009 07:06 PM, Andrew Olney wrote:
> Host is ext3
>
> Linux monkamu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC
> 2009 i686 GNU/Linux
>
> QEMU PC emulator version 0.11.0 (qemu-kvm-0.11.0), Copyright (c)
> 2003-2008 Fabrice Bellard
>
>
If you convert a qcow image back to raw on ext3, does it fail?
Similarly, converting it into an lvm volume, works or not?
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: xp guest, blue screen c0000221 on boot
2009-11-08 12:15 ` Avi Kivity
@ 2009-11-09 16:26 ` Andrew Olney
0 siblings, 0 replies; 12+ messages in thread
From: Andrew Olney @ 2009-11-09 16:26 UTC (permalink / raw)
To: Avi Kivity; +Cc: kvm
qemu-img convert -O raw xp.qcow2 xp.img
using the same command on the raw image gives a blue screen on startup
(same error as before)
So converting from raw to qcow2 fixes the error, and converting back to
raw reintroduces the error
I'm not set up to use LVM volumes
Avi Kivity wrote:
> On 11/04/2009 07:06 PM, Andrew Olney wrote:
>> Host is ext3
>>
>> Linux monkamu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC
>> 2009 i686 GNU/Linux
>>
>> QEMU PC emulator version 0.11.0 (qemu-kvm-0.11.0), Copyright (c)
>> 2003-2008 Fabrice Bellard
>>
>>
>
> If you convert a qcow image back to raw on ext3, does it fail?
>
> Similarly, converting it into an lvm volume, works or not?
>
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2009-11-09 16:26 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2009-10-29 10:29 ` Gerd Hoffmann
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.