10 # Emitted when the virtual machine has shut down, indicating that qemu is
13 # Note: If the command-line option "-no-shutdown" has been specified, qemu will
14 # not exit, and a STOP event will eventually follow the SHUTDOWN event
20 # <- { "event": "SHUTDOWN",
21 # "timestamp": { "seconds": 1267040730, "microseconds": 682951 } }
24 { 'event': 'SHUTDOWN' }
29 # Emitted when the virtual machine is powered down through the power control
30 # system, such as via ACPI.
36 # <- { "event": "POWERDOWN",
37 # "timestamp": { "seconds": 1267040730, "microseconds": 682951 } }
40 { 'event': 'POWERDOWN' }
45 # Emitted when the virtual machine is reset
51 # <- { "event": "RESET",
52 # "timestamp": { "seconds": 1267041653, "microseconds": 9518 } }
60 # Emitted when the virtual machine is stopped
66 # <- { "event": "STOP",
67 # "timestamp": { "seconds": 1267041730, "microseconds": 281295 } }
75 # Emitted when the virtual machine resumes execution
81 # <- { "event": "RESUME",
82 # "timestamp": { "seconds": 1271770767, "microseconds": 582542 } }
90 # Emitted when guest enters a hardware suspension state, for example, S3 state,
91 # which is sometimes called standby state
97 # <- { "event": "SUSPEND",
98 # "timestamp": { "seconds": 1344456160, "microseconds": 309119 } }
101 { 'event': 'SUSPEND' }
106 # Emitted when guest enters a hardware suspension state with data saved on
107 # disk, for example, S4 state, which is sometimes called hibernate state
109 # Note: QEMU shuts down (similar to event @SHUTDOWN) when entering this state
115 # <- { "event": "SUSPEND_DISK",
116 # "timestamp": { "seconds": 1344456160, "microseconds": 309119 } }
119 { 'event': 'SUSPEND_DISK' }
124 # Emitted when the guest has woken up from suspend state and is running
128 { 'event': 'WAKEUP' }
133 # Emitted when the guest changes the RTC time.
135 # @offset: offset between base RTC clock (as specified by -rtc base), and
136 # new RTC clock value
140 { 'event': 'RTC_CHANGE',
141 'data': { 'offset': 'int' } }
146 # Emitted when the watchdog device's timer is expired
148 # @action: action that has been taken
150 # Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is
151 # followed respectively by the RESET, SHUTDOWN, or STOP events
155 { 'event': 'WATCHDOG',
156 'data': { 'action': 'WatchdogExpirationAction' } }
161 # Emitted whenever the device removal completion is acknowledged by the guest.
162 # At this point, it's safe to reuse the specified device ID. Device removal can
163 # be initiated by the guest or by HMP/QMP commands.
165 # @device: #optional, device name
171 { 'event': 'DEVICE_DELETED',
172 'data': { '*device': 'str', 'path': 'str' } }
175 # @NIC_RX_FILTER_CHANGED:
177 # Emitted once until the 'query-rx-filter' command is executed, the first event
178 # will always be emitted
180 # @name: #optional, net client name
186 { 'event': 'NIC_RX_FILTER_CHANGED',
187 'data': { '*name': 'str', 'path': 'str' } }
192 # Emitted when a VNC client establishes a connection
194 # @server: server information
196 # @client: client information
198 # Note: This event is emitted before any authentication takes place, thus
199 # the authentication ID is not provided
203 { 'event': 'VNC_CONNECTED',
204 'data': { 'server': 'VncServerInfo',
205 'client': 'VncBasicInfo' } }
210 # Emitted after authentication takes place (if any) and the VNC session is
213 # @server: server information
215 # @client: client information
219 { 'event': 'VNC_INITIALIZED',
220 'data': { 'server': 'VncServerInfo',
221 'client': 'VncClientInfo' } }
226 # Emitted when the connection is closed
228 # @server: server information
230 # @client: client information
234 { 'event': 'VNC_DISCONNECTED',
235 'data': { 'server': 'VncServerInfo',
236 'client': 'VncClientInfo' } }
241 # Emitted when a SPICE client establishes a connection
243 # @server: server information
245 # @client: client information
249 { 'event': 'SPICE_CONNECTED',
250 'data': { 'server': 'SpiceBasicInfo',
251 'client': 'SpiceBasicInfo' } }
254 # @SPICE_INITIALIZED:
256 # Emitted after initial handshake and authentication takes place (if any)
257 # and the SPICE channel is up and running
259 # @server: server information
261 # @client: client information
265 { 'event': 'SPICE_INITIALIZED',
266 'data': { 'server': 'SpiceServerInfo',
267 'client': 'SpiceChannel' } }
270 # @SPICE_DISCONNECTED:
272 # Emitted when the SPICE connection is closed
274 # @server: server information
276 # @client: client information
280 { 'event': 'SPICE_DISCONNECTED',
281 'data': { 'server': 'SpiceBasicInfo',
282 'client': 'SpiceBasicInfo' } }
285 # @SPICE_MIGRATE_COMPLETED:
287 # Emitted when SPICE migration has completed
291 { 'event': 'SPICE_MIGRATE_COMPLETED' }
296 # Emitted when a migration event happens
298 # @status: @MigrationStatus describing the current migration status.
302 { 'event': 'MIGRATION',
303 'data': {'status': 'MigrationStatus'}}
308 # Emitted from the source side of a migration at the start of each pass
309 # (when it syncs the dirty bitmap)
311 # @pass: An incrementing count (starting at 1 on the first pass)
315 { 'event': 'MIGRATION_PASS',
316 'data': { 'pass': 'int' } }
321 # Emitted when guest executes ACPI _OST method.
323 # @info: ACPIOSTInfo type as described in qapi-schema.json
327 { 'event': 'ACPI_DEVICE_OST',
328 'data': { 'info': 'ACPIOSTInfo' } }
333 # Emitted when the guest changes the actual BALLOON level. This value is
334 # equivalent to the @actual field return by the 'query-balloon' command
336 # @actual: actual level of the guest memory balloon in bytes
340 { 'event': 'BALLOON_CHANGE',
341 'data': { 'actual': 'int' } }
346 # Emitted when guest OS panic is detected
348 # @action: action that has been taken, currently always "pause"
352 { 'event': 'GUEST_PANICKED',
353 'data': { 'action': 'GuestPanicAction' } }
358 # Emitted by the Quorum block driver if it fails to establish a quorum
360 # @reference: device name if defined else node name
362 # @sector-num: number of the first sector of the failed read operation
364 # @sectors-count: failed read operation sector count
368 { 'event': 'QUORUM_FAILURE',
369 'data': { 'reference': 'str', 'sector-num': 'int', 'sectors-count': 'int' } }
372 # @QUORUM_REPORT_BAD:
374 # Emitted to report a corruption of a Quorum file
376 # @type: quorum operation type (Since 2.6)
378 # @error: #optional, error message. Only present on failure. This field
379 # contains a human-readable error message. There are no semantics other
380 # than that the block layer reported an error and clients should not
381 # try to interpret the error string.
383 # @node-name: the graph node name of the block driver state
385 # @sector-num: number of the first sector of the failed read operation
387 # @sectors-count: failed read operation sector count
391 { 'event': 'QUORUM_REPORT_BAD',
392 'data': { 'type': 'QuorumOpType', '*error': 'str', 'node-name': 'str',
393 'sector-num': 'int', 'sectors-count': 'int' } }
398 # Emitted when the guest opens or closes a virtio-serial port.
400 # @id: device identifier of the virtio-serial port
402 # @open: true if the guest has opened the virtio-serial port
406 { 'event': 'VSERPORT_CHANGE',
407 'data': { 'id': 'str', 'open': 'bool' } }
412 # Emitted when memory hot unplug error occurs.
414 # @device: device name
416 # @msg: Informative message
420 { 'event': 'MEM_UNPLUG_ERROR',
421 'data': { 'device': 'str', 'msg': 'str' } }
426 # Emitted when background dump has completed
428 # @result: DumpQueryResult type described in qapi-schema.json.
430 # @error: #optional human-readable error string that provides
431 # hint on why dump failed. Only presents on failure. The
432 # user should not try to interpret the error string.
436 { 'event': 'DUMP_COMPLETED' ,
437 'data': { 'result': 'DumpQueryResult', '*error': 'str' } }