Lines Matching +full:suspend +full:- +full:to +full:- +full:disk

1 # -*- Mode: Python -*-
18 # @finish-migrate: guest is paused to finish the migration process
22 # the end of the migration. This depends on the command-line -S
26 # @internal-error: An internal error that prevents further guest
29 # @io-error: the last IOP has failed and the device is configured to
36 # @prelaunch: QEMU was started with -S and guest has not started
38 # @restore-vm: guest is paused to restore VM state
42 # @save-vm: guest is paused to save the VM state
44 # @shutdown: guest is shut down (and -no-shutdown is in use)
48 # @watchdog: the watchdog action is configured to pause and has been
51 # @guest-panicked: guest has been panicked as a result of guest OS
54 # @colo: guest is paused to save/restore VM state under colo
59 'data': [ 'debug', 'inmigrate', 'internal-error', 'io-error', 'paused',
60 'postmigrate', 'prelaunch', 'finish-migrate', 'restore-vm',
61 'running', 'save-vm', 'shutdown', 'suspended', 'watchdog',
62 'guest-panicked', 'colo' ] }
71 # @host-error: An error prevents further use of guest
73 # @host-qmp-quit: Reaction to the QMP command `quit`
75 # @host-qmp-system-reset: Reaction to the QMP command `system_reset`
77 # @host-signal: Reaction to a signal, such as SIGINT
79 # @host-ui: Reaction to a UI event, like window close
81 # @guest-shutdown: Guest shutdown/suspend request, via ACPI or other
82 # hardware-specific means
84 # @guest-reset: Guest reset request, and command line turns that into
87 # @guest-panic: Guest panicked, and command line turns that into a
90 # @subsystem-reset: Partial guest reset that does not trigger QMP
91 # events and ignores --no-reboot. This is useful for sanitizing
94 # @snapshot-load: A snapshot is being loaded by the record & replay
100 'data': [ 'none', 'host-error', 'host-qmp-quit', 'host-qmp-system-reset',
101 'host-signal', 'host-ui', 'guest-shutdown', 'guest-reset',
102 'guest-panic', 'subsystem-reset', 'snapshot-load'] }
120 # @query-status:
126 # .. qmp-example::
128 # -> { "execute": "query-status" }
129 # <- { "return": { "running": true,
132 { 'command': 'query-status', 'returns': 'StatusInfo',
133 'allow-preconfig': true }
139 # is about to exit.
142 # as a guest-initiated ACPI shutdown request or other
143 # hardware-specific action) rather than a host request (such as
149 # .. note:: If the command-line option ``-no-shutdown`` has been
155 # .. qmp-example::
157 # <- { "event": "SHUTDOWN",
158 # "data": { "guest": true, "reason": "guest-shutdown" },
171 # .. qmp-example::
173 # <- { "event": "POWERDOWN",
184 # a guest-initiated ACPI reboot request or other hardware-specific
192 # .. qmp-example::
194 # <- { "event": "RESET",
195 # "data": { "guest": false, "reason": "guest-reset" },
207 # .. qmp-example::
209 # <- { "event": "STOP",
221 # .. qmp-example::
223 # <- { "event": "RESUME",
229 # @SUSPEND:
236 # .. qmp-example::
238 # <- { "event": "SUSPEND",
241 { 'event': 'SUSPEND' }
247 # saved on disk, for example, S4 state, which is sometimes called
250 # .. note:: QEMU shuts down (similar to event `SHUTDOWN`) when entering
255 # .. qmp-example::
257 # <- { "event": "SUSPEND_DISK",
265 # Emitted when the guest has woken up from suspend state and is
270 # .. qmp-example::
272 # <- { "event": "WAKEUP",
288 # .. note:: This event is rate-limited.
292 # .. qmp-example::
294 # <- { "event": "WATCHDOG",
309 # @shutdown: system shutdown, note that it is similar to @powerdown,
310 # which tries to set to system status and notify guest
314 # @pause: system pauses, similar to @stop
320 # @inject-nmi: a non-maskable interrupt is injected into the first
327 'inject-nmi' ] }
336 # @shutdown: Shutdown the VM and exit, according to the shutdown
365 # @shutdown: Shutdown the VM and exit, according to the shutdown
368 # @exit-failure: Shutdown the VM and exit with nonzero status
374 'data': [ 'pause', 'shutdown', 'exit-failure', 'none' ] }
377 # @watchdog-set-action:
385 # .. qmp-example::
387 # -> { "execute": "watchdog-set-action",
388 # "arguments": { "action": "inject-nmi" } }
389 # <- { "return": {} }
391 { 'command': 'watchdog-set-action', 'data' : {'action': 'WatchdogAction'} }
394 # @set-action:
396 # Set the actions that will be taken by the emulator in response to
409 # .. qmp-example::
411 # -> { "execute": "set-action",
415 # "watchdog": "inject-nmi" } }
416 # <- { "return": {} }
418 { 'command': 'set-action',
423 'allow-preconfig': true }
436 # .. qmp-example::
438 # <- { "event": "GUEST_PANICKED",
456 # .. qmp-example::
458 # <- { "event": "GUEST_CRASHLOADED",
472 # .. qmp-example::
474 # <- { "event": "GUEST_PVSHUTDOWN",
488 # @run: system continues to run (since 5.0)
500 # @hyper-v: hyper-v guest panic information type
509 'data': [ 'hyper-v', 's390', 'tdx' ] }
523 'data': {'hyper-v': 'GuestPanicInformationHyperV',
530 # Hyper-V specific guest panic information (HV crash MSRs)
536 # guest OS ID, which has the kernel version in bits 16-47 and
537 # 0x8100 in bits 48-63.
564 # @disabled-wait: the CPU has entered a disabled wait state
566 # @extint-loop: clock comparator or cpu timer interrupt with new PSW
569 # @pgmint-loop: program interrupt with BAD new PSW
571 # @opint-loop: operation exception interrupt with invalid code at the
578 'disabled-wait',
579 'extint-loop',
580 'pgmint-loop',
581 'opint-loop' ] }
590 # @psw-mask: control fields of guest PSW
592 # @psw-addr: guest instruction address
600 'psw-mask': 'uint64',
601 'psw-addr': 'uint64',
607 # TDX Guest panic information specific to TDX, as specified in the
608 # "Guest-Hypervisor Communication Interface (GHCI) Specification",
611 # @error-code: TD-specific error code
613 # @message: Human-readable error message provided by the guest. Not
614 # to be trusted.
616 # @gpa: guest-physical address of a page that contains more verbose
617 # error information, as zero-terminated string. Present when the
618 # "GPA valid" bit (bit 63) is set in @error-code.
624 'data': {'error-code': 'uint32',
641 # .. qmp-example::
643 # <- { "event": "MEMORY_FAILURE",
646 # "flags": { "action-required": false,
674 # Actions taken by QEMU in response to a hardware memory failure.
677 # case for action-optional failures.
684 # action-required failures if the recipient is the hypervisor;
687 # @reset: the failure is unrecoverable but confined to the guest.
689 # to handle memory failures.
704 # @action-required: whether a memory failure event is action-required
705 # or action-optional (e.g. a failure during memory scrub).
713 'data': { 'action-required': 'bool',
724 # @internal-error: enable the feature, raise a internal error if the
732 'data': [ 'run', 'internal-error', 'disable' ] }