Revision 432d29db qapi-schema-guest.json
b/qapi-schema-guest.json | ||
---|---|---|
395 | 395 |
# command. Thus, it's *required* to query QEMU for the presence of the |
396 | 396 |
# 'system_wakeup' command before issuing guest-suspend-ram. |
397 | 397 |
# |
398 |
# Returns: nothing on success |
|
398 |
# This command does NOT return a response on success. There are two options |
|
399 |
# to check for success: |
|
400 |
# 1. Wait for the SUSPEND QMP event from QEMU |
|
401 |
# 2. Issue the query-status QMP command to confirm the VM status is |
|
402 |
# "suspended" |
|
403 |
# |
|
404 |
# The following errors may be returned: |
|
399 | 405 |
# If suspend to ram is not supported, Unsupported |
400 | 406 |
# |
401 |
# Notes: o This is an asynchronous request. There's no guarantee a response |
|
402 |
# will be sent |
|
403 |
# o It's strongly recommended to issue the guest-sync command before |
|
404 |
# sending commands when the guest resumes |
|
407 |
# Notes: It's strongly recommended to issue the guest-sync command before |
|
408 |
# sending commands when the guest resumes |
|
405 | 409 |
# |
406 | 410 |
# Since: 1.1 |
407 | 411 |
## |
408 |
{ 'command': 'guest-suspend-ram' } |
|
412 |
{ 'command': 'guest-suspend-ram', 'success-response': 'no' }
|
|
409 | 413 |
|
410 | 414 |
## |
411 | 415 |
# @guest-suspend-hybrid |
Also available in: Unified diff