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
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,
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
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
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
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 ei
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 -b
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.i
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.
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
On 10/26/2009 11:09 PM, Andrew Olney wrote:
Hangs on boot, xp guest:
STOP: c221 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 hav
Hangs on boot, xp guest:
STOP: c221 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 i
12 matches
Mail list logo
