From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qmp: handle stop/cont in INMIGRATE state
Date: Fri, 19 Oct 2012 11:02:01 -0300 [thread overview]
Message-ID: <20121019110201.28b3617a@doriath.home> (raw)
In-Reply-To: <50815A99.8040404@redhat.com>
On Fri, 19 Oct 2012 15:50:17 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 19/10/2012 15:23, Luiz Capitulino ha scritto:
> >> >
> >> > With HMP yes, with QMP no. You just get "An incoming migration is
> >> > expected before this command can be executed" and no clue that disks
> >> > are encrypted.
> > We could move the bdrv_iterate() calls before the RUN_STATE_INMIGRATE check
> > in qmp_cont(), but if this patch fixes all the cases you mention then let's
> > just apply it.
>
> I'm all for that. :)
I guess it won't have any affects on the -S races.
prev parent reply other threads:[~2012-10-19 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 9:14 [Qemu-devel] [PATCH] qmp: handle stop/cont in INMIGRATE state Paolo Bonzini
2012-10-18 16:42 ` Luiz Capitulino
2012-10-19 9:27 ` Paolo Bonzini
2012-10-19 13:23 ` Luiz Capitulino
2012-10-19 13:50 ` Paolo Bonzini
2012-10-19 14:02 ` Luiz Capitulino [this message]
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=20121019110201.28b3617a@doriath.home \
--to=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).