From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Lieven <pl@kamp.de>
Cc: qemu-block@nongnu.org, kwolf@redhat.com, qemu-devel@nongnu.org,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [RFC PATCH] qemu-io: add drain/undrain cmd
Date: Wed, 17 May 2017 13:10:24 +0100 [thread overview]
Message-ID: <20170517121024.GD8260@stefanha-x1.localdomain> (raw)
In-Reply-To: <1494842563-6534-1-git-send-email-pl@kamp.de>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
On Mon, May 15, 2017 at 12:02:43PM +0200, Peter Lieven wrote:
> I would like to add a feature to Qemu to drain all traffic from a block so that
> I can take external snaphosts without the risk to that in the middle of a write
> operation. Its meant for cases where where QGA freeze/thaw is not available.
>
> For me its enough to have this through qemu-io, but Kevin asked me to check
> if its not worth to have a stable API for it and present it via QMP/HMP.
>
> What are your thoughts?
Are the existing snapshot and blockjobs not sufficient for taking
external snapshots?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2017-05-17 12:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 10:02 [Qemu-devel] [RFC PATCH] qemu-io: add drain/undrain cmd Peter Lieven
2017-05-15 10:50 ` Fam Zheng
2017-05-15 11:26 ` Peter Lieven
2017-05-15 11:53 ` Fam Zheng
2017-05-15 11:58 ` Peter Lieven
2017-05-15 12:28 ` Fam Zheng
2017-05-15 12:32 ` Peter Lieven
2017-05-15 12:52 ` Fam Zheng
2017-05-15 13:01 ` Peter Lieven
2017-05-15 13:35 ` Fam Zheng
2017-05-15 14:02 ` Peter Lieven
2017-05-15 14:11 ` Fam Zheng
2017-05-15 13:02 ` Kevin Wolf
2017-05-15 14:23 ` Peter Lieven
2017-05-17 12:10 ` Stefan Hajnoczi [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=20170517121024.GD8260@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).