All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Kenni Lund <kenni@kelu.dk>
Cc: kvm@vger.kernel.org, Kevin Wolf <kwolf@redhat.com>
Subject: Re: SIGTERM to qemu-kvm process destroys qcow2 image?
Date: Thu, 17 Dec 2009 12:23:41 +0200	[thread overview]
Message-ID: <4B2A06AD.4020605@redhat.com> (raw)
In-Reply-To: <3b1f68ef0912170138i29e356cax54897503c03f12c9@mail.gmail.com>

On 12/17/2009 11:38 AM, Kenni Lund wrote:
> 2009/12/17 Avi Kivity<avi@redhat.com>:
>    
>> 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


  reply	other threads:[~2009-12-17 10:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17  0:52 SIGTERM to qemu-kvm process destroys qcow2 image? Kenni Lund
2009-12-17  5:34 ` Avi Kivity
2009-12-17  9:38   ` Kenni Lund
2009-12-17 10:23     ` Avi Kivity [this message]
2009-12-17 10:52       ` Kevin Wolf
2009-12-18 14:13         ` Kenni Lund
2009-12-18 14:22           ` Avi Kivity
2009-12-18 14:30             ` Kevin Wolf
2009-12-18 14:35             ` Kenni Lund
2009-12-20  6:21               ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B2A06AD.4020605@redhat.com \
    --to=avi@redhat.com \
    --cc=kenni@kelu.dk \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.