From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
Jeff Cody <jcody@redhat.com>,
Developers qemu-devel <qemu-devel@nongnu.org>,
Federico Simoncelli <fsimonce@redhat.com>,
quintela@trasno.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] blockdev operations [was: KVM call agenda for Tuesday 28th]
Date: Tue, 28 Feb 2012 17:12:25 +0100 [thread overview]
Message-ID: <4F4CFCE9.7040401@redhat.com> (raw)
In-Reply-To: <4F4CFBB7.9060707@redhat.com>
Il 28/02/2012 17:07, Eric Blake ha scritto:
> { 'enum': 'BlockdevOp',
> 'data': [ 'snapshot', 'snapshot-mirror', 'reopen' ] }
> { 'type': 'BlockdevAction',
> 'data': {'device': 'str', 'op': 'BlockdevOp',
> 'file': 'str', '*format': 'str', '*reuse': 'bool',
> '*mirror': 'str', '*mirror-format': 'str' } }
> { 'command': 'blkdev-group-action-sync',
> 'data': { 'actionlist': [ 'BlockdevAction' ] } }
>
>
> The overall command is atomic - either all operations will succeed, or
> the command returns an error pointing to the name of the device that
> failed leaving all devices in their pre-command state. Then, for each
> requested operation:
>
> If op is 'snapshot', then 'file' names the new snapshot file; 'reuse' is
> optional (defaults to false) to say whether qemu creates the file from
> scratch, or opens an existing file with the backing file already
> populated correctly. 'format' gives the format of 'file', defaulting to
> qcow2. 'mirror' and 'mirror-format' must not be given.
>
> If op is 'snapshot-mirror', then 'mirror' is mandatory; and both 'file'
> and 'mirror' are opened as a new mirrored snapshot. Again, 'reuse'
> affects whether qemu creates the new files from scratch or trusts oVirt
> to pre-create both files with backing file information; and 'format' and
> 'mirror-format' allow control over the image format being opened.
Could snapshot-mirror be done as two separate commands for snapshot (or
reopen) and mirror? This removes the need for mirror and mirror-format.
> If op is 'reopen', then 'file' is the name of the file to be opened to
> replace the current file tied to the blockdev, with type given by
> 'format'. 'reuse', 'mirror', and 'mirror-format' must not be given.
Otherwise looks good.
Paolo
next prev parent reply other threads:[~2012-02-28 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 12:22 [Qemu-devel] KVM call agenda for Tuesday 28th Juan Quintela
2012-02-27 17:21 ` Eric Blake
2012-02-27 21:58 ` Paolo Bonzini
2012-02-27 22:06 ` Anthony Liguori
2012-02-27 22:09 ` Paolo Bonzini
2012-02-28 14:39 ` Stefan Hajnoczi
2012-02-28 14:47 ` Paolo Bonzini
2012-02-28 14:58 ` Stefan Hajnoczi
2012-02-28 16:07 ` [Qemu-devel] blockdev operations [was: KVM call agenda for Tuesday 28th] Eric Blake
2012-02-28 16:12 ` Paolo Bonzini [this message]
2012-02-29 10:16 ` Kevin Wolf
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=4F4CFCE9.7040401@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=eblake@redhat.com \
--cc=fsimonce@redhat.com \
--cc=jcody@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.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).