From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Wolf Subject: Re: SIGTERM to qemu-kvm process destroys qcow2 image? Date: Fri, 18 Dec 2009 15:30:48 +0100 Message-ID: <4B2B9218.80207@redhat.com> References: <3b1f68ef0912161652l94ad986lc3f3ee380614c108@mail.gmail.com> <4B29C2EF.5010606@redhat.com> <3b1f68ef0912170138i29e356cax54897503c03f12c9@mail.gmail.com> <4B2A06AD.4020605@redhat.com> <4B2A0D79.9010900@redhat.com> <3b1f68ef0912180613u3cf9940ah790a74f67cc11d4e@mail.gmail.com> <4B2B9027.60102@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Kenni Lund , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4828 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754052AbZLROb6 (ORCPT ); Fri, 18 Dec 2009 09:31:58 -0500 In-Reply-To: <4B2B9027.60102@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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