diff options
| author | Luiz Capitulino <lcapitulino@redhat.com> | 2012-04-27 13:33:36 -0300 |
|---|---|---|
| committer | Luiz Capitulino <lcapitulino@redhat.com> | 2012-05-08 14:30:09 -0300 |
| commit | ad02b96ad86baf6dd72a43b04876b2d6ea957112 (patch) | |
| tree | 3f069ea707475c64c7aa8e306b9bfbe2c27f2395 /qapi-schema.json | |
| parent | 0a24c7b18eefcd1138a5c60fc77bc9b653c64082 (diff) | |
| download | qemu-ad02b96ad86baf6dd72a43b04876b2d6ea957112.zip qemu-ad02b96ad86baf6dd72a43b04876b2d6ea957112.tar.gz qemu-ad02b96ad86baf6dd72a43b04876b2d6ea957112.tar.bz2 | |
runstate: introduce suspended state
QEMU enters in this state when the guest suspends to ram (S3).
This is important so that HMP users and QMP clients can know that
the guest is suspended. QMP also has an event for this, but events
are not reliable and are limited (ie. a client can connect to QEMU
after the event has been emitted).
Having a different state for S3 brings a new issue, though. Every
device that doesn't run when the VM is stopped but wants to run
when the VM is suspended has to check for RUN_STATE_SUSPENDED
explicitly. This is the case for the keyboard and mouse devices,
for example.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'qapi-schema.json')
| -rw-r--r-- | qapi-schema.json | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/qapi-schema.json b/qapi-schema.json index 33f2f92..2ca7195 100644 --- a/qapi-schema.json +++ b/qapi-schema.json @@ -116,12 +116,14 @@ # # @shutdown: guest is shut down (and -no-shutdown is in use) # +# @suspended: guest is suspended (ACPI S3) +# # @watchdog: the watchdog action is configured to pause and has been triggered ## { 'enum': 'RunState', 'data': [ 'debug', 'inmigrate', 'internal-error', 'io-error', 'paused', 'postmigrate', 'prelaunch', 'finish-migrate', 'restore-vm', - 'running', 'save-vm', 'shutdown', 'watchdog' ] } + 'running', 'save-vm', 'shutdown', 'suspended', 'watchdog' ] } ## # @StatusInfo: |