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
130 # <- { "event": "WAKEUP",
131 # "timestamp": { "seconds": 1344522075, "microseconds": 745528 } }
134 { 'event': 'WAKEUP' }
139 # Emitted when the guest changes the RTC time.
141 # @offset: offset between base RTC clock (as specified by -rtc base), and
142 # new RTC clock value
144 # Note: This event is rate-limited.
150 # <- { "event": "RTC_CHANGE",
151 # "data": { "offset": 78 },
152 # "timestamp": { "seconds": 1267020223, "microseconds": 435656 } }
155 { 'event': 'RTC_CHANGE',
156 'data': { 'offset': 'int' } }
161 # Emitted when the watchdog device's timer is expired
163 # @action: action that has been taken
165 # Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is
166 # followed respectively by the RESET, SHUTDOWN, or STOP events
168 # Note: This event is rate-limited.
174 # <- { "event": "WATCHDOG",
175 # "data": { "action": "reset" },
176 # "timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
179 { 'event': 'WATCHDOG',
180 'data': { 'action': 'WatchdogExpirationAction' } }
185 # Emitted whenever the device removal completion is acknowledged by the guest.
186 # At this point, it's safe to reuse the specified device ID. Device removal can
187 # be initiated by the guest or by HMP/QMP commands.
189 # @device: #optional, device name
197 # <- { "event": "DEVICE_DELETED",
198 # "data": { "device": "virtio-net-pci-0",
199 # "path": "/machine/peripheral/virtio-net-pci-0" },
200 # "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
203 { 'event': 'DEVICE_DELETED',
204 'data': { '*device': 'str', 'path': 'str' } }
207 # @NIC_RX_FILTER_CHANGED:
209 # Emitted once until the 'query-rx-filter' command is executed, the first event
210 # will always be emitted
212 # @name: #optional, net client name
220 # <- { "event": "NIC_RX_FILTER_CHANGED",
221 # "data": { "name": "vnet0",
222 # "path": "/machine/peripheral/vnet0/virtio-backend" },
223 # "timestamp": { "seconds": 1368697518, "microseconds": 326866 } }
227 { 'event': 'NIC_RX_FILTER_CHANGED',
228 'data': { '*name': 'str', 'path': 'str' } }
233 # Emitted when a VNC client establishes a connection
235 # @server: server information
237 # @client: client information
239 # Note: This event is emitted before any authentication takes place, thus
240 # the authentication ID is not provided
246 # <- { "event": "VNC_CONNECTED",
248 # "server": { "auth": "sasl", "family": "ipv4",
249 # "service": "5901", "host": "0.0.0.0" },
250 # "client": { "family": "ipv4", "service": "58425",
251 # "host": "127.0.0.1" } },
252 # "timestamp": { "seconds": 1262976601, "microseconds": 975795 } }
255 { 'event': 'VNC_CONNECTED',
256 'data': { 'server': 'VncServerInfo',
257 'client': 'VncBasicInfo' } }
262 # Emitted after authentication takes place (if any) and the VNC session is
265 # @server: server information
267 # @client: client information
273 # <- { "event": "VNC_INITIALIZED",
275 # "server": { "auth": "sasl", "family": "ipv4",
276 # "service": "5901", "host": "0.0.0.0"},
277 # "client": { "family": "ipv4", "service": "46089",
278 # "host": "127.0.0.1", "sasl_username": "luiz" } },
279 # "timestamp": { "seconds": 1263475302, "microseconds": 150772 } }
282 { 'event': 'VNC_INITIALIZED',
283 'data': { 'server': 'VncServerInfo',
284 'client': 'VncClientInfo' } }
289 # Emitted when the connection is closed
291 # @server: server information
293 # @client: client information
297 { 'event': 'VNC_DISCONNECTED',
298 'data': { 'server': 'VncServerInfo',
299 'client': 'VncClientInfo' } }
304 # Emitted when a SPICE client establishes a connection
306 # @server: server information
308 # @client: client information
312 { 'event': 'SPICE_CONNECTED',
313 'data': { 'server': 'SpiceBasicInfo',
314 'client': 'SpiceBasicInfo' } }
317 # @SPICE_INITIALIZED:
319 # Emitted after initial handshake and authentication takes place (if any)
320 # and the SPICE channel is up and running
322 # @server: server information
324 # @client: client information
328 { 'event': 'SPICE_INITIALIZED',
329 'data': { 'server': 'SpiceServerInfo',
330 'client': 'SpiceChannel' } }
333 # @SPICE_DISCONNECTED:
335 # Emitted when the SPICE connection is closed
337 # @server: server information
339 # @client: client information
343 { 'event': 'SPICE_DISCONNECTED',
344 'data': { 'server': 'SpiceBasicInfo',
345 'client': 'SpiceBasicInfo' } }
348 # @SPICE_MIGRATE_COMPLETED:
350 # Emitted when SPICE migration has completed
354 { 'event': 'SPICE_MIGRATE_COMPLETED' }
359 # Emitted when a migration event happens
361 # @status: @MigrationStatus describing the current migration status.
365 { 'event': 'MIGRATION',
366 'data': {'status': 'MigrationStatus'}}
371 # Emitted from the source side of a migration at the start of each pass
372 # (when it syncs the dirty bitmap)
374 # @pass: An incrementing count (starting at 1 on the first pass)
378 { 'event': 'MIGRATION_PASS',
379 'data': { 'pass': 'int' } }
384 # Emitted when guest executes ACPI _OST method.
386 # @info: ACPIOSTInfo type as described in qapi-schema.json
390 { 'event': 'ACPI_DEVICE_OST',
391 'data': { 'info': 'ACPIOSTInfo' } }
396 # Emitted when the guest changes the actual BALLOON level. This value is
397 # equivalent to the @actual field return by the 'query-balloon' command
399 # @actual: actual level of the guest memory balloon in bytes
403 { 'event': 'BALLOON_CHANGE',
404 'data': { 'actual': 'int' } }
409 # Emitted when guest OS panic is detected
411 # @action: action that has been taken, currently always "pause"
415 { 'event': 'GUEST_PANICKED',
416 'data': { 'action': 'GuestPanicAction' } }
421 # Emitted by the Quorum block driver if it fails to establish a quorum
423 # @reference: device name if defined else node name
425 # @sector-num: number of the first sector of the failed read operation
427 # @sectors-count: failed read operation sector count
431 { 'event': 'QUORUM_FAILURE',
432 'data': { 'reference': 'str', 'sector-num': 'int', 'sectors-count': 'int' } }
435 # @QUORUM_REPORT_BAD:
437 # Emitted to report a corruption of a Quorum file
439 # @type: quorum operation type (Since 2.6)
441 # @error: #optional, error message. Only present on failure. This field
442 # contains a human-readable error message. There are no semantics other
443 # than that the block layer reported an error and clients should not
444 # try to interpret the error string.
446 # @node-name: the graph node name of the block driver state
448 # @sector-num: number of the first sector of the failed read operation
450 # @sectors-count: failed read operation sector count
454 { 'event': 'QUORUM_REPORT_BAD',
455 'data': { 'type': 'QuorumOpType', '*error': 'str', 'node-name': 'str',
456 'sector-num': 'int', 'sectors-count': 'int' } }
461 # Emitted when the guest opens or closes a virtio-serial port.
463 # @id: device identifier of the virtio-serial port
465 # @open: true if the guest has opened the virtio-serial port
469 { 'event': 'VSERPORT_CHANGE',
470 'data': { 'id': 'str', 'open': 'bool' } }
475 # Emitted when memory hot unplug error occurs.
477 # @device: device name
479 # @msg: Informative message
483 { 'event': 'MEM_UNPLUG_ERROR',
484 'data': { 'device': 'str', 'msg': 'str' } }
489 # Emitted when background dump has completed
491 # @result: DumpQueryResult type described in qapi-schema.json.
493 # @error: #optional human-readable error string that provides
494 # hint on why dump failed. Only presents on failure. The
495 # user should not try to interpret the error string.
499 { 'event': 'DUMP_COMPLETED' ,
500 'data': { 'result': 'DumpQueryResult', '*error': 'str' } }