4 # Emitted when the virtual machine has shutdown, possibly indicating that QEMU
5 # is about about to exit.
7 # Note: If the command-line option "-no-shutdown" has been specified, qemu will
8 # not exit, and a STOP event will eventually follow the SHUTDOWN event
12 { 'event': 'SHUTDOWN' }
17 # Emitted when the virtual machine is powered down through the power control
18 # system, such as via ACPI.
22 { 'event': 'POWERDOWN' }
27 # Emitted when the virtual machine is reset
36 # Emitted when the virtual machine is stopped
45 # Emitted when the virtual machine resumes execution
54 # Emitted when guest enters a hardware suspension state, for example, S3 state,
55 # which is sometimes called standby state
59 { 'event': 'SUSPEND' }
64 # Emitted when guest enters a hardware suspension state with data saved on
65 # disk, for example, S4 state, which is sometimes called hibernate state
67 # Note: QEMU shuts down (similar to event @SHUTDOWN) when entering this state
71 { 'event': 'SUSPEND_DISK' }
76 # Emitted when the guest has woken up from suspend state and is running
85 # Emitted when the guest changes the RTC time.
87 # @offset: offset between base RTC clock (as specified by -rtc base), and
92 { 'event': 'RTC_CHANGE',
93 'data': { 'offset': 'int' } }
98 # Emitted when the watchdog device's timer is expired
100 # @action: action that has been taken
102 # Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is
103 # followed respectively by the RESET, SHUTDOWN, or STOP events
107 { 'event': 'WATCHDOG',
108 'data': { 'action': 'WatchdogExpirationAction' } }
113 # Emitted whenever the device removal completion is acknowledged by the guest.
114 # At this point, it's safe to reuse the specified device ID. Device removal can
115 # be initiated by the guest or by HMP/QMP commands.
117 # @device: #optional, device name
123 { 'event': 'DEVICE_DELETED',
124 'data': { '*device': 'str', 'path': 'str' } }