From: Avi Kivity <avi@redhat.com>
To: Kenni Lund <kenni@kelu.dk>
Cc: Kevin Wolf <kwolf@redhat.com>, kvm@vger.kernel.org
Subject: Re: SIGTERM to qemu-kvm process destroys qcow2 image?
Date: Sun, 20 Dec 2009 08:21:39 +0200 [thread overview]
Message-ID: <4B2DC273.6080101@redhat.com> (raw)
In-Reply-To: <3b1f68ef0912180635hc9e97bbw6ccfa8fcd29d0960@mail.gmail.com>
On 12/18/2009 04:35 PM, Kenni Lund wrote:
>
> Thanks, this explains the whole thing - this is own mistake, I move
> all the backups into a subdirectory, I didn't know that I had based
> the image on a backup-image, bad design decision on my part.
>
Note you can undo it using qemu-img convert, if you have the free space
and the patience.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2009-12-20 6:21 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
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 [this message]
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=4B2DC273.6080101@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.