From: Juan Quintela <quintela@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, laine@redhat.com,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH 4/7] runstate: migration allows more transitions now
Date: Wed, 15 Oct 2014 17:50:21 +0200 [thread overview]
Message-ID: <87bnpdfi2q.fsf@elfo.elfo> (raw)
In-Reply-To: <543E87CD.9010305@redhat.com> (Eric Blake's message of "Wed, 15 Oct 2014 08:42:21 -0600")
Eric Blake <eblake@redhat.com> wrote:
> On 10/15/2014 01:55 AM, Juan Quintela wrote:
>> Next commit would allow to move from incoming migration to error
>> happening on source.
>>
>> Should we add more states to this transition? Luiz?
>
> Does this mean we can finally do S3 migration without forcing the guest
> to wake up from S3 on the destination?
I haven't tested, but it should just work (famous last words).
Would test.
Later, Juan.
>
>>
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>> ---
>> vl.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/vl.c b/vl.c
>> index c4bc43c..1788b6a 100644
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -618,6 +618,8 @@ static const RunStateTransition runstate_transitions_def[] = {
>>
>> { RUN_STATE_INMIGRATE, RUN_STATE_RUNNING },
>> { RUN_STATE_INMIGRATE, RUN_STATE_PAUSED },
>> + { RUN_STATE_INMIGRATE, RUN_STATE_INTERNAL_ERROR },
>> + { RUN_STATE_INMIGRATE, RUN_STATE_IO_ERROR },
>>
>> { RUN_STATE_INTERNAL_ERROR, RUN_STATE_PAUSED },
>> { RUN_STATE_INTERNAL_ERROR, RUN_STATE_FINISH_MIGRATE },
>>
next prev parent reply other threads:[~2014-10-15 15:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 7:55 [Qemu-devel] [RFC 0/7] Optional toplevel sections Juan Quintela
2014-10-15 7:55 ` [Qemu-devel] [PATCH 1/7] migration: Create optional sections Juan Quintela
2014-10-15 7:55 ` [Qemu-devel] [PATCH 2/7] runstate: Add runstate store Juan Quintela
2014-10-20 10:24 ` Dr. David Alan Gilbert
2014-10-20 10:52 ` Juan Quintela
2014-10-20 15:18 ` Eric Blake
2014-10-22 11:18 ` Dr. David Alan Gilbert
2014-10-22 11:40 ` Markus Armbruster
2014-10-22 15:52 ` Eric Blake
2014-10-15 7:55 ` [Qemu-devel] [PATCH 3/7] runstate: create runstate_index function Juan Quintela
2014-10-15 7:55 ` [Qemu-devel] [PATCH 4/7] runstate: migration allows more transitions now Juan Quintela
2014-10-15 14:42 ` Eric Blake
2014-10-15 15:50 ` Juan Quintela [this message]
2014-11-03 12:46 ` Amit Shah
2014-10-15 7:55 ` [Qemu-devel] [PATCH 5/7] migration: create now section to store global state Juan Quintela
2014-10-20 10:52 ` Dr. David Alan Gilbert
2014-10-20 11:11 ` Kevin Wolf
2014-10-15 7:55 ` [Qemu-devel] [PATCH 6/7] global_state: Make section optional Juan Quintela
2014-10-15 7:55 ` [Qemu-devel] [PATCH 7/7] vmstate: Create optional sections Juan Quintela
2014-10-15 14:45 ` Eric Blake
2014-10-15 14:57 ` [Qemu-devel] [RFC 0/7] Optional toplevel sections Eric Blake
2014-10-15 15:59 ` Juan Quintela
2014-10-15 16:37 ` Eric Blake
2014-10-17 13:41 ` Paolo Bonzini
2014-10-20 14:59 ` Dr. David Alan Gilbert
2014-10-20 11:29 ` 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=87bnpdfi2q.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=laine@redhat.com \
--cc=lcapitulino@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).