From: Liu Yuan <namei.unix@gmail.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, stefanha@redhat.com, sheepdog@lists.wpkg.org,
qemu-devel@nongnu.org,
MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Subject: Re: [Qemu-devel] [sheepdog] [PATCH 0/3] sheepdog: support online snapshot from qemu-img
Date: Thu, 25 Apr 2013 22:01:23 +0800 [thread overview]
Message-ID: <51793733.8050900@gmail.com> (raw)
In-Reply-To: <5179333D.1040501@redhat.com>
On 04/25/2013 09:44 PM, Eric Blake wrote:
> Is that even safe? We specifically recommend that users NOT use
> qemu-img on any image that is in-use by a qemu process, and instead only
> use qemu monitor commands; since qemu-img may see inconsistent state,
> and worse, any writes that qemu-img do may cause qemu to see
> inconsistent state and cause corruption to the running guest.
Then why not disable ( qemu-im snapshoting live VM) this behavior
completely?
Thanks,
Yuan
next prev parent reply other threads:[~2013-04-25 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 10:37 [Qemu-devel] [PATCH 0/3] sheepdog: support online snapshot from qemu-img MORITA Kazutaka
2013-04-25 10:37 ` [Qemu-devel] [PATCH 1/3] sheepdog: cleanup find_vdi_name MORITA Kazutaka
2013-04-25 10:37 ` [Qemu-devel] [PATCH 2/3] sheepdog: add SD_RES_READONLY result code MORITA Kazutaka
2013-04-25 10:37 ` [Qemu-devel] [PATCH 3/3] sheepdog: resend write requests when SD_RES_READONLY is received MORITA Kazutaka
2013-04-25 13:08 ` [Qemu-devel] [sheepdog] " Liu Yuan
2013-04-25 16:16 ` MORITA Kazutaka
2013-04-25 13:56 ` [Qemu-devel] " Stefan Hajnoczi
2013-04-25 13:44 ` [Qemu-devel] [PATCH 0/3] sheepdog: support online snapshot from qemu-img Eric Blake
2013-04-25 14:01 ` Liu Yuan [this message]
2013-04-25 14:06 ` Stefan Hajnoczi
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=51793733.8050900@gmail.com \
--to=namei.unix@gmail.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=morita.kazutaka@lab.ntt.co.jp \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.org \
--cc=stefanha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).