From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, Ian Main <imain@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
dietmar@proxmox.com
Subject: Re: [Qemu-devel] [PATCH 0/3] block: block-backup live backup command
Date: Tue, 23 Apr 2013 10:49:35 -0600 [thread overview]
Message-ID: <5176BB9F.5060003@redhat.com> (raw)
In-Reply-To: <1366734308-11724-1-git-send-email-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
On 04/23/2013 10:25 AM, Stefan Hajnoczi wrote:
> This series adds a new QMP command, block-backup, which takes a point-in-time
> snapshot of a block device. The snapshot is copied out to a target block
> device. A simple example is:
>
> block-backup device=virtio0 format=qcow2 target=backup-20130401.qcow2
> What's next for block-backup?
> -----------------------------
> The following enhancements are left for future patches:
>
> 1. QMP 'transaction' support. It is handy to atomically snapshot multiple
> block devices. We need qmp_transaction() support for this. Wenchao Xia is
> currently making qmp_transaction() extensible so new action types, like
> block-backup, can be added.
>
> 2. Sync modes like drive-mirror (top, full, none). This makes it possible to
> preserve the backing file chain.
Based on today's phone call, it sounds like this would mean adding
optional parameters to the QMP command. We already did that for
drive-mirror (1.4 has more parameters than 1.3), but without a way to
introspect when those parameters are available, the new parameters
aren't quite as useful. So we don't repeat that mistake, we need to
decide whether this should still go into 1.5 with a plan of adding
parameters for 1.6, or whether we should add a counterpart query-*
command that makes it easy to determine how much of block-backup is
supported, or [your suggestion here]....
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-04-23 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 16:25 [Qemu-devel] [PATCH 0/3] block: block-backup live backup command Stefan Hajnoczi
2013-04-23 16:25 ` [Qemu-devel] [PATCH 1/3] block: add basic backup support to block driver Stefan Hajnoczi
2013-04-23 16:25 ` [Qemu-devel] [PATCH 2/3] block: add block_backup QMP command Stefan Hajnoczi
2013-04-26 22:52 ` Eric Blake
2013-04-26 22:53 ` Eric Blake
2013-04-26 22:58 ` Eric Blake
2013-04-29 7:21 ` Stefan Hajnoczi
2013-04-29 9:27 ` Paolo Bonzini
2013-04-29 15:51 ` Eric Blake
2013-05-01 11:55 ` Stefan Hajnoczi
2013-04-23 16:25 ` [Qemu-devel] [PATCH 3/3] qemu-iotests: add 054 block-backup test case Stefan Hajnoczi
2013-04-23 16:49 ` Eric Blake [this message]
2013-04-23 16:57 ` [Qemu-devel] [PATCH 0/3] block: block-backup live backup command Paolo Bonzini
2013-04-24 7:41 ` Stefan Hajnoczi
2013-04-24 12:44 ` Eric Blake
2013-04-27 5:37 ` Wenchao Xia
2013-04-29 7:22 ` 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=5176BB9F.5060003@redhat.com \
--to=eblake@redhat.com \
--cc=dietmar@proxmox.com \
--cc=famz@redhat.com \
--cc=imain@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).