qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
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 23:09:30 +0100	[thread overview]
Message-ID: <4F4BFF1A.8040703@redhat.com> (raw)
In-Reply-To: <4F4BFE4D.8000409@codemonkey.ws>

Il 27/02/2012 23:06, Anthony Liguori ha scritto:
> 
> 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)?

Paused.  Only the two new commands and blockdev-snapshot-sync are part
of the transaction (edited the wiki now).

What I like most in Jeff's new command is that it's not even a question.
 On the other hand we have to be sure that we can extend it, and perhaps
change its name already in 1.1...

Paolo

  reply	other threads:[~2012-02-27 22:09 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 [this message]
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=4F4BFF1A.8040703@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=eblake@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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).