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

[Avi Kivity <avi@redhat.com>]

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 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/.

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


-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.