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
84 # Emitted when guest enters a hardware suspension state, for example, S3 state,
85 # which is sometimes called standby state
89 { 'event': 'SUSPEND' }
94 # Emitted when guest enters a hardware suspension state with data saved on
95 # disk, for example, S4 state, which is sometimes called hibernate state
97 # Note: QEMU shuts down (similar to event @SHUTDOWN) when entering this state
101 { 'event': 'SUSPEND_DISK' }
106 # Emitted when the guest has woken up from suspend state and is running
110 { 'event': 'WAKEUP' }
115 # Emitted when the guest changes the RTC time.
117 # @offset: offset between base RTC clock (as specified by -rtc base), and
118 # new RTC clock value
122 { 'event': 'RTC_CHANGE',
123 'data': { 'offset': 'int' } }
128 # Emitted when the watchdog device's timer is expired
130 # @action: action that has been taken
132 # Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is
133 # followed respectively by the RESET, SHUTDOWN, or STOP events
137 { 'event': 'WATCHDOG',
138 'data': { 'action': 'WatchdogExpirationAction' } }
143 # Emitted whenever the device removal completion is acknowledged by the guest.
144 # At this point, it's safe to reuse the specified device ID. Device removal can
145 # be initiated by the guest or by HMP/QMP commands.
147 # @device: #optional, device name
153 { 'event': 'DEVICE_DELETED',
154 'data': { '*device': 'str', 'path': 'str' } }
157 # @NIC_RX_FILTER_CHANGED:
159 # Emitted once until the 'query-rx-filter' command is executed, the first event
160 # will always be emitted
162 # @name: #optional, net client name
168 { 'event': 'NIC_RX_FILTER_CHANGED',
169 'data': { '*name': 'str', 'path': 'str' } }
174 # Emitted when a VNC client establishes a connection
176 # @server: server information
178 # @client: client information
180 # Note: This event is emitted before any authentication takes place, thus
181 # the authentication ID is not provided
185 { 'event': 'VNC_CONNECTED',
186 'data': { 'server': 'VncServerInfo',
187 'client': 'VncBasicInfo' } }
192 # Emitted after authentication takes place (if any) and the VNC session is
195 # @server: server information
197 # @client: client information
201 { 'event': 'VNC_INITIALIZED',
202 'data': { 'server': 'VncServerInfo',
203 'client': 'VncClientInfo' } }
208 # Emitted when the connection is closed
210 # @server: server information
212 # @client: client information
216 { 'event': 'VNC_DISCONNECTED',
217 'data': { 'server': 'VncServerInfo',
218 'client': 'VncClientInfo' } }
223 # Emitted when a SPICE client establishes a connection
225 # @server: server information
227 # @client: client information
231 { 'event': 'SPICE_CONNECTED',
232 'data': { 'server': 'SpiceBasicInfo',
233 'client': 'SpiceBasicInfo' } }
236 # @SPICE_INITIALIZED:
238 # Emitted after initial handshake and authentication takes place (if any)
239 # and the SPICE channel is up and running
241 # @server: server information
243 # @client: client information
247 { 'event': 'SPICE_INITIALIZED',
248 'data': { 'server': 'SpiceServerInfo',
249 'client': 'SpiceChannel' } }
252 # @SPICE_DISCONNECTED:
254 # Emitted when the SPICE connection is closed
256 # @server: server information
258 # @client: client information
262 { 'event': 'SPICE_DISCONNECTED',
263 'data': { 'server': 'SpiceBasicInfo',
264 'client': 'SpiceBasicInfo' } }
267 # @SPICE_MIGRATE_COMPLETED:
269 # Emitted when SPICE migration has completed
273 { 'event': 'SPICE_MIGRATE_COMPLETED' }
278 # Emitted when a migration event happens
280 # @status: @MigrationStatus describing the current migration status.
284 { 'event': 'MIGRATION',
285 'data': {'status': 'MigrationStatus'}}
290 # Emitted from the source side of a migration at the start of each pass
291 # (when it syncs the dirty bitmap)
293 # @pass: An incrementing count (starting at 1 on the first pass)
297 { 'event': 'MIGRATION_PASS',
298 'data': { 'pass': 'int' } }
303 # Emitted when guest executes ACPI _OST method.
305 # @info: ACPIOSTInfo type as described in qapi-schema.json
309 { 'event': 'ACPI_DEVICE_OST',
310 'data': { 'info': 'ACPIOSTInfo' } }
315 # Emitted when the guest changes the actual BALLOON level. This value is
316 # equivalent to the @actual field return by the 'query-balloon' command
318 # @actual: actual level of the guest memory balloon in bytes
322 { 'event': 'BALLOON_CHANGE',
323 'data': { 'actual': 'int' } }
328 # Emitted when guest OS panic is detected
330 # @action: action that has been taken, currently always "pause"
334 { 'event': 'GUEST_PANICKED',
335 'data': { 'action': 'GuestPanicAction' } }
340 # Emitted by the Quorum block driver if it fails to establish a quorum
342 # @reference: device name if defined else node name
344 # @sector-num: number of the first sector of the failed read operation
346 # @sectors-count: failed read operation sector count
350 { 'event': 'QUORUM_FAILURE',
351 'data': { 'reference': 'str', 'sector-num': 'int', 'sectors-count': 'int' } }
354 # @QUORUM_REPORT_BAD:
356 # Emitted to report a corruption of a Quorum file
358 # @type: quorum operation type (Since 2.6)
360 # @error: #optional, error message. Only present on failure. This field
361 # contains a human-readable error message. There are no semantics other
362 # than that the block layer reported an error and clients should not
363 # try to interpret the error string.
365 # @node-name: the graph node name of the block driver state
367 # @sector-num: number of the first sector of the failed read operation
369 # @sectors-count: failed read operation sector count
373 { 'event': 'QUORUM_REPORT_BAD',
374 'data': { 'type': 'QuorumOpType', '*error': 'str', 'node-name': 'str',
375 'sector-num': 'int', 'sectors-count': 'int' } }
380 # Emitted when the guest opens or closes a virtio-serial port.
382 # @id: device identifier of the virtio-serial port
384 # @open: true if the guest has opened the virtio-serial port
388 { 'event': 'VSERPORT_CHANGE',
389 'data': { 'id': 'str', 'open': 'bool' } }
394 # Emitted when memory hot unplug error occurs.
396 # @device: device name
398 # @msg: Informative message
402 { 'event': 'MEM_UNPLUG_ERROR',
403 'data': { 'device': 'str', 'msg': 'str' } }
408 # Emitted when background dump has completed
410 # @result: DumpQueryResult type described in qapi-schema.json.
412 # @error: #optional human-readable error string that provides
413 # hint on why dump failed. Only presents on failure. The
414 # user should not try to interpret the error string.
418 { 'event': 'DUMP_COMPLETED' ,
419 'data': { 'result': 'DumpQueryResult', '*error': 'str' } }