Re: SIGTERM to qemu-kvm process destroys qcow2 image?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2009/12/18 Avi Kivity <avi@xxxxxxxxxx>:
> 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 I can
>> see why it doesn't work, but I have _no_ idea why or how this file was
>> created (?!??) - even if I was doing a test with base-images, I would
>> do it directly in /data/virtualization/ and never in /tmp/
>>
>
> If it isn't there you can try to create it (qemu-img create
> /data/virtualization/WindowsXP.img.backup 31457280000).  If no data was
> actually stored there, your image will be recovered.

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.

I'm sorry for the false alarm, thanks a lot for your help :)

Best Regards
Kenni Lund
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux