4 # Emitted when the virtual machine has shut down, indicating that qemu is
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' } }
127 # @NIC_RX_FILTER_CHANGED
129 # Emitted once until the 'query-rx-filter' command is executed, the first event
130 # will always be emitted
132 # @name: #optional, net client name
138 { 'event': 'NIC_RX_FILTER_CHANGED',
139 'data': { '*name': 'str', 'path': 'str' } }
144 # Emitted when a VNC client establishes a connection
146 # @server: server information
148 # @client: client information
150 # Note: This event is emitted before any authentication takes place, thus
151 # the authentication ID is not provided
155 { 'event': 'VNC_CONNECTED',
156 'data': { 'server': 'VncServerInfo',
157 'client': 'VncBasicInfo' } }
162 # Emitted after authentication takes place (if any) and the VNC session is
165 # @server: server information
167 # @client: client information
171 { 'event': 'VNC_INITIALIZED',
172 'data': { 'server': 'VncServerInfo',
173 'client': 'VncClientInfo' } }
178 # Emitted when the connection is closed
180 # @server: server information
182 # @client: client information
186 { 'event': 'VNC_DISCONNECTED',
187 'data': { 'server': 'VncServerInfo',
188 'client': 'VncClientInfo' } }
193 # Emitted when a SPICE client establishes a connection
195 # @server: server information
197 # @client: client information
201 { 'event': 'SPICE_CONNECTED',
202 'data': { 'server': 'SpiceBasicInfo',
203 'client': 'SpiceBasicInfo' } }
208 # Emitted after initial handshake and authentication takes place (if any)
209 # and the SPICE channel is up and running
211 # @server: server information
213 # @client: client information
217 { 'event': 'SPICE_INITIALIZED',
218 'data': { 'server': 'SpiceServerInfo',
219 'client': 'SpiceChannel' } }
222 # @SPICE_DISCONNECTED
224 # Emitted when the SPICE connection is closed
226 # @server: server information
228 # @client: client information
232 { 'event': 'SPICE_DISCONNECTED',
233 'data': { 'server': 'SpiceBasicInfo',
234 'client': 'SpiceBasicInfo' } }
237 # @SPICE_MIGRATE_COMPLETED
239 # Emitted when SPICE migration has completed
243 { 'event': 'SPICE_MIGRATE_COMPLETED' }
248 # Emitted when a migration event happens
250 # @status: @MigrationStatus describing the current migration status.
254 { 'event': 'MIGRATION',
255 'data': {'status': 'MigrationStatus'}}
260 # Emitted when guest executes ACPI _OST method.
264 # @info: ACPIOSTInfo type as described in qapi-schema.json
266 { 'event': 'ACPI_DEVICE_OST',
267 'data': { 'info': 'ACPIOSTInfo' } }
272 # Emitted when the guest changes the actual BALLOON level. This value is
273 # equivalent to the @actual field return by the 'query-balloon' command
275 # @actual: actual level of the guest memory balloon in bytes
279 { 'event': 'BALLOON_CHANGE',
280 'data': { 'actual': 'int' } }
285 # Emitted when guest OS panic is detected
287 # @action: action that has been taken, currently always "pause"
291 { 'event': 'GUEST_PANICKED',
292 'data': { 'action': 'GuestPanicAction' } }
297 # Emitted by the Quorum block driver if it fails to establish a quorum
299 # @reference: device name if defined else node name
301 # @sector-num: number of the first sector of the failed read operation
303 # @sectors-count: failed read operation sector count
307 { 'event': 'QUORUM_FAILURE',
308 'data': { 'reference': 'str', 'sector-num': 'int', 'sectors-count': 'int' } }
313 # Emitted to report a corruption of a Quorum file
315 # @error: #optional, error message. Only present on failure. This field
316 # contains a human-readable error message. There are no semantics other
317 # than that the block layer reported an error and clients should not
318 # try to interpret the error string.
320 # @node-name: the graph node name of the block driver state
322 # @sector-num: number of the first sector of the failed read operation
324 # @sectors-count: failed read operation sector count
328 { 'event': 'QUORUM_REPORT_BAD',
329 'data': { '*error': 'str', 'node-name': 'str',
330 'sector-num': 'int', 'sectors-count': 'int' } }
335 # Emitted when the guest opens or closes a virtio-serial port.
337 # @id: device identifier of the virtio-serial port
339 # @open: true if the guest has opened the virtio-serial port
343 { 'event': 'VSERPORT_CHANGE',
344 'data': { 'id': 'str', 'open': 'bool' } }
349 # Emitted when memory hot unplug error occurs.
351 # @device: device name
353 # @msg: Informative message
357 { 'event': 'MEM_UNPLUG_ERROR',
358 'data': { 'device': 'str', 'msg': 'str' } }