On 12/18/2009 04:35 PM, Kenni Lund wrote:
Thanks, this explains the whole thing - this is own mistake, I move
all the backups into a subdirectory, I didn't know that I had based
the image on a backup-image, bad design decision on my part.
Note you can undo it using qemu-img convert, if
2009/12/17 Kevin Wolf kw...@redhat.com:
Am 17.12.2009 11:23, schrieb Avi Kivity:
On 12/17/2009 11:38 AM, Kenni Lund wrote:
2009/12/17 Avi Kivitya...@redhat.com:
On 12/17/2009 02:52 AM, Kenni Lund wrote:
Yesterday I entered an invalid boot device as an argument to my
qemu-kvm command for my
On 12/18/2009 04:13 PM, Kenni Lund wrote:
Huh? Backing file? Is that the same as a base image? Eg. a write
protected image on which other images can be based?
Yes.
If so, I'm quite confused...this should be a standalone image created
with a command like qemu-img create -f WindowsXP.img
Am 18.12.2009 15:22, schrieb Avi Kivity:
If so, I'm quite confused...this should be a standalone image created
with a command like qemu-img create -f WindowsXP.img 50G half a year
ago on kvm 8x. I don't use libvirt/virt-manager etc. I start qemu-kvm
directly from a homemade bash script. I
2009/12/18 Avi Kivity a...@redhat.com:
On 12/18/2009 04:13 PM, Kenni Lund wrote:
The '/tmp' was prefixed by qemu-img, the actual path is
'WindowsXP.img.backup', so on your setup qemu-img would look for it in
/data/virtualization/.
If the image needs another image in /tmp/WindowsXP.img.backup
2009/12/17 Avi Kivity a...@redhat.com:
On 12/17/2009 02:52 AM, Kenni Lund wrote:
Yesterday I entered an invalid boot device as an argument to my
qemu-kvm command for my Windows XP machine, causing an error about a
missing boot device in the qemu BIOS/POST. As I didn't have any
filesystems
On 12/17/2009 11:38 AM, Kenni Lund wrote:
2009/12/17 Avi Kivitya...@redhat.com:
On 12/17/2009 02:52 AM, Kenni Lund wrote:
Yesterday I entered an invalid boot device as an argument to my
qemu-kvm command for my Windows XP machine, causing an error about a
missing boot device in the
Am 17.12.2009 11:23, schrieb Avi Kivity:
On 12/17/2009 11:38 AM, Kenni Lund wrote:
2009/12/17 Avi Kivitya...@redhat.com:
On 12/17/2009 02:52 AM, Kenni Lund wrote:
Yesterday I entered an invalid boot device as an argument to my
qemu-kvm command for my Windows XP machine, causing an
Hi
Sorry if this is a stupid question, but is it expected behaviour that
a qcow2 image will/can get damaged by killing the qemu-kvm process
with a SIGTERM signal?
I would expect data on filesystems within the virtual machine to
potentially get damaged if it's in use, but I though that the
On 12/17/2009 02:52 AM, Kenni Lund wrote:
Hi
Sorry if this is a stupid question, but is it expected behaviour that
a qcow2 image will/can get damaged by killing the qemu-kvm process
with a SIGTERM signal?
If it does, that's a serious bug. qcow2 should survive SIGTERM,
SIGKILL, and host
10 matches
Mail list logo
