From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org,
Luiz Capitulino <lcapitulino@redhat.com>,
blauwirbel@gmail.com, jan.kiszka@web.de, avi@redhat.com,
amit.shah@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/7] QemuState: Add additional states
Date: Thu, 04 Aug 2011 14:32:27 +0200 [thread overview]
Message-ID: <4E3A915B.4030906@redhat.com> (raw)
In-Reply-To: <m3oc05eei9.fsf@blackfin.pond.sub.org>
Am 04.08.2011 11:02, schrieb Markus Armbruster:
> Luiz Capitulino <lcapitulino@redhat.com> writes:
>
>> Currently, only vm_start() and vm_stop() change the VM state. That's,
>> the state is only changed when starting or stopping the VM.
>>
>> This commit adds the qemu_state_set() function, making it possible
>> to also do state transitions when qemu is stopped or running.
>>
>> Additional states are also added and the current state is stored.
>> This is going to be used by the next commits.
>>
>> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
>> ---
>> cpus.c | 1 +
>> migration.c | 8 +++++++-
>> sysemu.h | 10 +++++++++-
>> vl.c | 20 ++++++++++++++++++++
>> 4 files changed, 37 insertions(+), 2 deletions(-)
>>
>> diff --git a/cpus.c b/cpus.c
>> index ebbb8b9..48e6ca1 100644
>> --- a/cpus.c
>> +++ b/cpus.c
>> @@ -124,6 +124,7 @@ static void do_vm_stop(QemuState state)
>> cpu_disable_ticks();
>> vm_running = 0;
>> pause_all_vcpus();
>> + qemu_state_set(state);
>> vm_state_notify(0, state);
>> qemu_aio_flush();
>> bdrv_flush_all();
>> diff --git a/migration.c b/migration.c
>> index 9724ce0..8aacf64 100644
>> --- a/migration.c
>> +++ b/migration.c
>> @@ -72,8 +72,11 @@ void process_incoming_migration(QEMUFile *f)
>>
>> incoming_expected = false;
>>
>> - if (autostart)
>> + if (autostart) {
>> vm_start();
>> + } else {
>> + qemu_state_set(QSTATE_PRELAUNCH);
>> + }
>> }
>>
>> int do_migrate(Monitor *mon, const QDict *qdict, QObject **ret_data)
>> @@ -394,6 +397,9 @@ void migrate_fd_put_ready(void *opaque)
>> }
>> state = MIG_STATE_ERROR;
>> }
>> + if (state == MIG_STATE_COMPLETED) {
>> + qemu_state_set(QSTATE_POSTMIGRATE);
>> + }
>> s->state = state;
>> notifier_list_notify(&migration_state_notifiers, NULL);
>> }
>> diff --git a/sysemu.h b/sysemu.h
>> index 2c3ea3d..32c9abb 100644
>> --- a/sysemu.h
>> +++ b/sysemu.h
>> @@ -11,16 +11,22 @@
>> /* vl.c */
>>
>> typedef enum {
>> + QSTATE_NOSTATE,
>
> QSTATE_NO_STATE?
>
>> QSTATE_DEBUG, /* qemu is running under gdb */
>> + QSTATE_INMIGRATE, /* paused waiting for an incoming migration */
>
> QSTATE_IN_MIGRATE?
>
>> QSTATE_INTERROR, /* paused due to an internal error */
>
> QSTATE_PANICKED?
>
>> QSTATE_IOERROR, /* paused due to an I/O error */
>
> QSTATE_IO_ERROR?
>
>> QSTATE_PAUSED, /* paused by the user (ie. the 'stop' command) */
>> + QSTATE_POSTMIGRATE, /* paused following a successful migration */
>
> QSTATE_POST_MIGRATE?
>
>> + QSTATE_PRELAUNCH, /* qemu was started with -S and haven't started */
>
> QSTATE_PRE_LAUNCH?
>
>> QSTATE_PREMIGRATE, /* paused preparing to finish migrate */
>
> QSTATE_PRE_MIGRATE?
>
>> QSTATE_RESTVM, /* paused restoring the VM state */
>> + QSTATE_RESTVMFAILED, /* paused due to a failed attempt to load state */
>
> QSTATE_RESTVM_FAILED?
QSTATE_RESTORE_FAILED?
It's hard to interpret RESTVM without having read the comment.
Kevin
next prev parent reply other threads:[~2011-08-04 12:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 15:17 [Qemu-devel] [PATCH 0/7]: Introduce the QemuState type Luiz Capitulino
2011-08-03 15:17 ` [Qemu-devel] [PATCH 1/7] Move vm_state_notify() prototype from cpus.h to sysemu.h Luiz Capitulino
2011-08-03 15:17 ` [Qemu-devel] [PATCH 2/7] Replace VMSTOP macros with a proper QemuState type Luiz Capitulino
2011-08-04 9:55 ` Avi Kivity
2011-08-04 10:17 ` Jan Kiszka
2011-08-04 10:27 ` Jan Kiszka
2011-08-04 14:06 ` Luiz Capitulino
2011-08-08 11:22 ` Avi Kivity
2011-08-08 13:25 ` Luiz Capitulino
2011-08-08 13:27 ` Avi Kivity
2011-08-08 13:28 ` Luiz Capitulino
2011-08-08 13:40 ` Avi Kivity
2011-08-08 13:47 ` Luiz Capitulino
2011-08-08 13:54 ` Avi Kivity
2011-08-08 14:06 ` Luiz Capitulino
2011-08-08 14:27 ` Avi Kivity
2011-08-08 20:25 ` Luiz Capitulino
2011-08-03 15:17 ` [Qemu-devel] [PATCH 3/7] QemuState: Add additional states Luiz Capitulino
2011-08-04 9:02 ` Markus Armbruster
2011-08-04 12:32 ` Kevin Wolf [this message]
2011-08-04 13:23 ` Anthony Liguori
2011-08-04 13:54 ` Luiz Capitulino
2011-08-08 6:02 ` Markus Armbruster
2011-08-03 15:17 ` [Qemu-devel] [PATCH 4/7] Drop the incoming_expected global variable Luiz Capitulino
2011-08-03 15:17 ` [Qemu-devel] [PATCH 5/7] Drop the vm_running " Luiz Capitulino
2011-08-03 15:17 ` [Qemu-devel] [PATCH 6/7] Monitor: Don't allow cont on bad VM state Luiz Capitulino
2011-08-03 15:32 ` Jan Kiszka
2011-08-03 17:32 ` Luiz Capitulino
2011-08-04 8:42 ` Jan Kiszka
2011-08-03 15:17 ` [Qemu-devel] [PATCH 7/7] QMP: query-status: Introduce 'status' key Luiz Capitulino
2011-08-04 9:06 ` [Qemu-devel] [PATCH 0/7]: Introduce the QemuState type Markus Armbruster
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=4E3A915B.4030906@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@web.de \
--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).