From: Luiz Capitulino <lcapitulino@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, stefanha@gmail.com, qemu-devel@nongnu.org,
armbru@redhat.com, pbonzini@redhat.com, eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 2/2] QMP: Add qmp command for blockdev-group-snapshot-sync
Date: Wed, 29 Feb 2012 11:37:12 -0300 [thread overview]
Message-ID: <20120229113712.51a0d502@doriath.home> (raw)
In-Reply-To: <9c58cbefce49000b6716f61c2dd5ef3c7fc7fcbf.1330461199.git.jcody@redhat.com>
On Tue, 28 Feb 2012 15:54:07 -0500
Jeff Cody <jcody@redhat.com> wrote:
> This adds the QMP command for blockdev-group-snapshot-sync. It
> takes an array in as the input, for the argument devlist. The
> array consists of the following elements:
>
> + device: device to snapshot. e.g. "ide-hd0", "virtio0"
> + snapshot-file: path & file for the snapshot image. e.g. "/tmp/file.img"
> + format: snapshot format. e.g., "qcow2". Optional
>
> There is no HMP equivalent for the command.
>
> Signed-off-by: Jeff Cody <jcody@redhat.com>
Could have been squashed with the previous patch, but of course that you
don't have to respin because of that.
> ---
> qmp-commands.hx | 39 +++++++++++++++++++++++++++++++++++++++
> 1 files changed, 39 insertions(+), 0 deletions(-)
>
> diff --git a/qmp-commands.hx b/qmp-commands.hx
> index b5e2ab8..15d35c1 100644
> --- a/qmp-commands.hx
> +++ b/qmp-commands.hx
> @@ -665,6 +665,45 @@ EQMP
> .args_type = "device:B",
> .mhandler.cmd_new = qmp_marshal_input_block_job_cancel,
> },
> + {
> + .name = "blockdev-group-snapshot-sync",
> + .args_type = "devlist:O",
> + .params = "device:B,snapshot-file:s,format:s?",
> + .mhandler.cmd_new = qmp_marshal_input_blockdev_group_snapshot_sync,
> + },
> +
> +SQMP
> +blockdev-group-snapshot-sync
> +----------------------
> +
> +Synchronous snapshot of one or more block devices. A list array input
> +is accepted, that contains the device and snapshot file information for
> +each device in group. The default format, if not specified, is qcow2.
> +
> +If there is any failure creating or opening a new snapshot, all snapshots
> +for the group are abandoned, and the original disks pre-snapshot attempt
> +are used.
> +
> +
> +Arguments:
> +
> +devlist array:
> + - "device": device name to snapshot (json-string)
> + - "snapshot-file": name of new image file (json-string)
> + - "format": format of new image (json-string, optional)
> +
> +Example:
> +
> +-> { "execute": "blockdev-group-snapshot-sync", "arguments":
> + { "devlist": [{ "device": "ide-hd0",
> + "snapshot-file": "/some/place/my-image",
> + "format": "qcow2" },
> + { "device": "ide-hd1",
> + "snapshot-file": "/some/place/my-image2",
> + "format": "qcow2" }] } }
> +<- { "return": {} }
> +
> +EQMP
>
> {
> .name = "blockdev-snapshot-sync",
next prev parent reply other threads:[~2012-02-29 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 20:54 [Qemu-devel] [PATCH v5 0/2] Group Live Snapshots Jeff Cody
2012-02-28 20:54 ` [Qemu-devel] [PATCH v5 1/2] qapi: Introduce blockdev-group-snapshot-sync command Jeff Cody
2012-02-29 14:36 ` Luiz Capitulino
2012-02-28 20:54 ` [Qemu-devel] [PATCH v5 2/2] QMP: Add qmp command for blockdev-group-snapshot-sync Jeff Cody
2012-02-29 14:37 ` Luiz Capitulino [this message]
2012-02-29 11:54 ` [Qemu-devel] [PATCH v5 0/2] Group Live Snapshots Kevin Wolf
2012-02-29 14:37 ` Luiz Capitulino
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=20120229113712.51a0d502@doriath.home \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).