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
54 # Emitted when the virtual machine is stopped
63 # Emitted when the virtual machine resumes execution
72 # Emitted when guest enters a hardware suspension state, for example, S3 state,
73 # which is sometimes called standby state
77 { 'event': 'SUSPEND' }
82 # Emitted when guest enters a hardware suspension state with data saved on
83 # disk, for example, S4 state, which is sometimes called hibernate state
85 # Note: QEMU shuts down (similar to event @SHUTDOWN) when entering this state
89 { 'event': 'SUSPEND_DISK' }
94 # Emitted when the guest has woken up from suspend state and is running
103 # Emitted when the guest changes the RTC time.
105 # @offset: offset between base RTC clock (as specified by -rtc base), and
106 # new RTC clock value
110 { 'event': 'RTC_CHANGE',
111 'data': { 'offset': 'int' } }
116 # Emitted when the watchdog device's timer is expired
118 # @action: action that has been taken
120 # Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is
121 # followed respectively by the RESET, SHUTDOWN, or STOP events
125 { 'event': 'WATCHDOG',
126 'data': { 'action': 'WatchdogExpirationAction' } }
131 # Emitted whenever the device removal completion is acknowledged by the guest.
132 # At this point, it's safe to reuse the specified device ID. Device removal can
133 # be initiated by the guest or by HMP/QMP commands.
135 # @device: #optional, device name
141 { 'event': 'DEVICE_DELETED',
142 'data': { '*device': 'str', 'path': 'str' } }
145 # @NIC_RX_FILTER_CHANGED:
147 # Emitted once until the 'query-rx-filter' command is executed, the first event
148 # will always be emitted
150 # @name: #optional, net client name
156 { 'event': 'NIC_RX_FILTER_CHANGED',
157 'data': { '*name': 'str', 'path': 'str' } }
162 # Emitted when a VNC client establishes a connection
164 # @server: server information
166 # @client: client information
168 # Note: This event is emitted before any authentication takes place, thus
169 # the authentication ID is not provided
173 { 'event': 'VNC_CONNECTED',
174 'data': { 'server': 'VncServerInfo',
175 'client': 'VncBasicInfo' } }
180 # Emitted after authentication takes place (if any) and the VNC session is
183 # @server: server information
185 # @client: client information
189 { 'event': 'VNC_INITIALIZED',
190 'data': { 'server': 'VncServerInfo',
191 'client': 'VncClientInfo' } }
196 # Emitted when the connection is closed
198 # @server: server information
200 # @client: client information
204 { 'event': 'VNC_DISCONNECTED',
205 'data': { 'server': 'VncServerInfo',
206 'client': 'VncClientInfo' } }
211 # Emitted when a SPICE client establishes a connection
213 # @server: server information
215 # @client: client information
219 { 'event': 'SPICE_CONNECTED',
220 'data': { 'server': 'SpiceBasicInfo',
221 'client': 'SpiceBasicInfo' } }
224 # @SPICE_INITIALIZED:
226 # Emitted after initial handshake and authentication takes place (if any)
227 # and the SPICE channel is up and running
229 # @server: server information
231 # @client: client information
235 { 'event': 'SPICE_INITIALIZED',
236 'data': { 'server': 'SpiceServerInfo',
237 'client': 'SpiceChannel' } }
240 # @SPICE_DISCONNECTED:
242 # Emitted when the SPICE connection is closed
244 # @server: server information
246 # @client: client information
250 { 'event': 'SPICE_DISCONNECTED',
251 'data': { 'server': 'SpiceBasicInfo',
252 'client': 'SpiceBasicInfo' } }
255 # @SPICE_MIGRATE_COMPLETED:
257 # Emitted when SPICE migration has completed
261 { 'event': 'SPICE_MIGRATE_COMPLETED' }
266 # Emitted when a migration event happens
268 # @status: @MigrationStatus describing the current migration status.
272 { 'event': 'MIGRATION',
273 'data': {'status': 'MigrationStatus'}}
278 # Emitted from the source side of a migration at the start of each pass
279 # (when it syncs the dirty bitmap)
281 # @pass: An incrementing count (starting at 1 on the first pass)
285 { 'event': 'MIGRATION_PASS',
286 'data': { 'pass': 'int' } }
291 # Emitted when guest executes ACPI _OST method.
293 # @info: ACPIOSTInfo type as described in qapi-schema.json
297 { 'event': 'ACPI_DEVICE_OST',
298 'data': { 'info': 'ACPIOSTInfo' } }
303 # Emitted when the guest changes the actual BALLOON level. This value is
304 # equivalent to the @actual field return by the 'query-balloon' command
306 # @actual: actual level of the guest memory balloon in bytes
310 { 'event': 'BALLOON_CHANGE',
311 'data': { 'actual': 'int' } }
316 # Emitted when guest OS panic is detected
318 # @action: action that has been taken, currently always "pause"
322 { 'event': 'GUEST_PANICKED',
323 'data': { 'action': 'GuestPanicAction' } }
328 # Emitted by the Quorum block driver if it fails to establish a quorum
330 # @reference: device name if defined else node name
332 # @sector-num: number of the first sector of the failed read operation
334 # @sectors-count: failed read operation sector count
338 { 'event': 'QUORUM_FAILURE',
339 'data': { 'reference': 'str', 'sector-num': 'int', 'sectors-count': 'int' } }
342 # @QUORUM_REPORT_BAD:
344 # Emitted to report a corruption of a Quorum file
346 # @type: quorum operation type (Since 2.6)
348 # @error: #optional, error message. Only present on failure. This field
349 # contains a human-readable error message. There are no semantics other
350 # than that the block layer reported an error and clients should not
351 # try to interpret the error string.
353 # @node-name: the graph node name of the block driver state
355 # @sector-num: number of the first sector of the failed read operation
357 # @sectors-count: failed read operation sector count
361 { 'event': 'QUORUM_REPORT_BAD',
362 'data': { 'type': 'QuorumOpType', '*error': 'str', 'node-name': 'str',
363 'sector-num': 'int', 'sectors-count': 'int' } }
368 # Emitted when the guest opens or closes a virtio-serial port.
370 # @id: device identifier of the virtio-serial port
372 # @open: true if the guest has opened the virtio-serial port
376 { 'event': 'VSERPORT_CHANGE',
377 'data': { 'id': 'str', 'open': 'bool' } }
382 # Emitted when memory hot unplug error occurs.
384 # @device: device name
386 # @msg: Informative message
390 { 'event': 'MEM_UNPLUG_ERROR',
391 'data': { 'device': 'str', 'msg': 'str' } }
396 # Emitted when background dump has completed
398 # @result: DumpQueryResult type described in qapi-schema.json.
400 # @error: #optional human-readable error string that provides
401 # hint on why dump failed. Only presents on failure. The
402 # user should not try to interpret the error string.
406 { 'event': 'DUMP_COMPLETED' ,
407 'data': { 'result': 'DumpQueryResult', '*error': 'str' } }