From: Stefan Hajnoczi <stefanha@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
imain@redhat.com, pbonzini@redhat.com, dietmar@proxmox.com
Subject: Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command
Date: Tue, 14 May 2013 10:48:57 +0200 [thread overview]
Message-ID: <20130514084857.GF8739@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <518DC2C6.5030500@redhat.com>
On Fri, May 10, 2013 at 10:02:14PM -0600, Eric Blake wrote:
> On 04/29/2013 01:42 AM, Stefan Hajnoczi wrote:
> > @block-backup
> >
> > +++ b/qapi-schema.json
> > @@ -1715,6 +1715,37 @@
> > '*speed': 'int' } }
> >
> > ##
> > +# @block-backup
> > +#
> > +# Start a point-in-time copy of a block device to a new destination. The
> > +# status of ongoing block backup operations can be checked with
> > +# query-block-jobs. The operation can be stopped before it has completed using
> > +# the block-job-cancel command.
>
> Still might be worth mentioning that 'query-block-jobs' will list it as
> a job of type 'backup'.
Will fix in v3.
> > +#
> > +# @device: the name of the device whose writes should be mirrored.
> > +#
> > +# @target: the target of the new image. If the file exists, or if it
> > +# is a device, the existing file/device will be used as the new
> > +# destination. If it does not exist, a new file will be created.
> > +#
> > +# @format: #optional the format of the new destination, default is to
> > +# probe if @mode is 'existing', else the format of the source
> > +#
> > +# @mode: #optional whether and how QEMU should create a new image, default is
> > +# 'absolute-paths'.
> > +#
> > +# @speed: #optional the maximum speed, in bytes per second
> > +#
> > +# Returns: nothing on success
> > +# If @device is not a valid block device, DeviceNotFound
> > +#
> > +# Since 1.6
> > +##
> > +{ 'command': 'block-backup',
> > + 'data': { 'device': 'str', 'target': 'str', '*format': 'str',
>
> Hmm - wondering if we should add an enum type for supported disk formats
> instead of using free-form strings. The wire representation would be
> the same, and now's the time to do it before we add introspection (it's
> more than just this command impacted).
Interesting discussion about dynamic schema. Since the wire format is
the same, I don't want to attempt solving the problem in the
block-backup series.
next prev parent reply other threads:[~2013-05-14 8:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 7:42 [Qemu-devel] [PATCH v2 0/3] block: block-backup live backup command Stefan Hajnoczi
2013-04-29 7:42 ` [Qemu-devel] [PATCH v2 1/3] block: add basic backup support to block driver Stefan Hajnoczi
2013-05-08 12:39 ` Kevin Wolf
2013-05-08 15:43 ` Paolo Bonzini
2013-05-14 8:51 ` Stefan Hajnoczi
2013-05-14 13:24 ` Stefan Hajnoczi
2013-05-14 13:43 ` Kevin Wolf
2013-05-14 15:12 ` Stefan Hajnoczi
2013-05-30 3:37 ` Fam Zheng
2013-05-30 12:27 ` Stefan Hajnoczi
2013-04-29 7:42 ` [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command Stefan Hajnoczi
2013-05-08 12:49 ` Kevin Wolf
2013-05-11 3:34 ` Eric Blake
2013-05-11 8:02 ` Paolo Bonzini
2013-05-13 8:23 ` Kevin Wolf
2013-05-14 8:44 ` Stefan Hajnoczi
2013-05-11 4:02 ` Eric Blake
2013-05-13 8:28 ` Kevin Wolf
2013-05-13 12:56 ` Eric Blake
2013-05-13 13:09 ` Kevin Wolf
2013-05-13 13:18 ` Luiz Capitulino
2013-05-13 14:14 ` Eric Blake
2013-05-13 14:27 ` Kevin Wolf
2013-05-13 14:50 ` Eric Blake
2013-05-14 2:18 ` Wenchao Xia
2013-05-14 8:48 ` Stefan Hajnoczi [this message]
2013-04-29 7:42 ` [Qemu-devel] [PATCH v2 3/3] qemu-iotests: add 054 block-backup test case 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=20130514084857.GF8739@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=dietmar@proxmox.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=imain@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiawenc@linux.vnet.ibm.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).