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

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

 



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 don't have any
>> /tmp/WindowsXP.img.backup file, and I would never put stuff inside
>> /tmp, especially not images, they belong to /data/virtualization/ on
>> my server and nowhere else....
>>    
> 
> 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/.

Whoops, I've been tricked by qemu-img. Sorry. I thought I had seen this
path in hexdump, but obviously that was wrong.

Kevin
--
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