From: Paolo Bonzini <pbonzini@redhat.com>
To: quintela@redhat.com, Amit Shah <amit.shah@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] migration: yet more possible state transitions
Date: Tue, 28 Jul 2015 18:16:20 +0200 [thread overview]
Message-ID: <55B7AAD4.2040707@redhat.com> (raw)
In-Reply-To: <87a8ugtilm.fsf@neno.neno>
On 28/07/2015 17:19, Juan Quintela wrote:
>> > On destination, we move from INMIGRATE to FINISH_MIGRATE. Add that to
>> > the list of allowed states.
>> >
>> > Signed-off-by: Juan Quintela <quintela@redhat.com>
> Self-NAK.
>
> Somewhere I was able to test old + new qemu given this weird behaviour.
> behaviour makes no sense, and I am not able to reproduce anymore.
I think it makes sense. Did you migrate twice on the source? Then the
state was FINISH_MIGRATE at the beginning of the second migration.
Paolo
next prev parent reply other threads:[~2015-07-28 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 13:30 [Qemu-devel] [PATCH] migration: yet more possible state transitions Juan Quintela
2015-07-28 15:19 ` Juan Quintela
2015-07-28 16:16 ` Paolo Bonzini [this message]
2015-07-28 16:47 ` Juan Quintela
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=55B7AAD4.2040707@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).