From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: SIGTERM to qemu-kvm process destroys qcow2 image? Date: Thu, 17 Dec 2009 12:23:41 +0200 Message-ID: <4B2A06AD.4020605@redhat.com> References: <3b1f68ef0912161652l94ad986lc3f3ee380614c108@mail.gmail.com> <4B29C2EF.5010606@redhat.com> <3b1f68ef0912170138i29e356cax54897503c03f12c9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Kevin Wolf To: Kenni Lund Return-path: Received: from mx1.redhat.com ([209.132.183.28]:18400 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761303AbZLQKXp (ORCPT ); Thu, 17 Dec 2009 05:23:45 -0500 In-Reply-To: <3b1f68ef0912170138i29e356cax54897503c03f12c9@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 12/17/2009 11:38 AM, Kenni Lund wrote: > 2009/12/17 Avi Kivity: > >> 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 mounted inside the virtual machine (since it was stuck at >>> the BIOS asking for a device to boot), I did a kill $pid, fixed the >>> boot device in the qemu-kvm command and tried booting again...but with >>> no luck, whatever I try now with qemu-kvm gives me the error: >>> qemu: could not open disk image /data/virtualization/WindowsXP.img >>> >>> And qemu-img (check, convert, etc) gives me: >>> qemu-img: Could not open 'WindowsXP.img' >>> >>> >> Can you post the first 4K of the image? It shouldn't contain private data, >> but go over it (or don't post) if you sensitive information there. >> > 4K dump attached. > > Seems fine. Kevin can you take a look? You have a backing file. Do qemu-img info and qemu-img check like it? -- error compiling committee.c: too many arguments to function