From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Eric Blake <eblake@redhat.com>,
quintela@trasno.org, KVM devel mailing list <kvm@vger.kernel.org>,
Developers qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 28th
Date: Mon, 27 Feb 2012 16:06:05 -0600 [thread overview]
Message-ID: <4F4BFE4D.8000409@codemonkey.ws> (raw)
In-Reply-To: <4F4BFC9A.1020300@redhat.com>
On 02/27/2012 03:58 PM, Paolo Bonzini wrote:
> Il 27/02/2012 18:21, Eric Blake ha scritto:
>>>> Please send in any agenda items you are interested in covering.
>> Given all the threads on snapshot/mirror/migrate/reopen in the blockdev
>> layer, that sounds like a worthwhile topic to discuss on a phone call.
>
> I put a description of the existing proposals here:
>
> http://wiki.qemu.org/Features/SnapshotsMultipleDevices/CommandSetProposals
Thanks! One thing I'm having trouble following on your proposal: What commands
are valid within blockdev-start-transaction/blockdev-commit-transaction?
If I do:
blockdev-start-transaction
stop
drive-reopen
drive-mirror
blockdev-end-transaction
What state should I expect that my guest is in (paused or running)?
Regards,
Anthony Liguori
>
> Paolo
>
next prev parent reply other threads:[~2012-02-27 22:06 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 [this message]
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
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=4F4BFE4D.8000409@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=eblake@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.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).