qemu/QMP/qmp-events.txt
Luiz Capitulino 51a3bd71b3 QMP: Drop DEBUG event
This event has been introduced in the first round of QMP commits,
turns out that it's based on the usage of the EXCP_DEBUG macro,
which has discussable semantics when exposed through QMP.

As libvirt doesn't use this, let's just drop it.

Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-03-08 11:30:08 -06:00

61 lines
1.5 KiB
Plaintext

QEMU Monitor Protocol: Events
=============================
1 SHUTDOWN
-----------
Description: Issued when the Virtual Machine is powered down.
Data: None.
2 RESET
-------
Description: Issued when the Virtual Machine is reseted.
Data: None.
3 STOP
------
Description: Issued when the Virtual Machine is stopped.
Data: None.
4 VNC_CONNECTED
---------------
Description: Issued when a VNC client establishes a connection.
Data: 'server' and 'client' keys with the same keys as 'query-vnc',
except that authentication ID is not provided.
5 VNC_DISCONNECTED
------------------
Description: Issued when the conection is closed.
Data: 'server' and 'client' keys with the same keys as 'query-vnc'.
6 VNC_INITIALIZED
-----------------
Description: Issued when the VNC session is made active.
Data: 'server' and 'client' keys with the same keys as 'query-vnc'.
7 BLOCK_IO_ERROR
----------------
Description: Issued when a disk I/O error occurs
Data:
- 'device': device name (json-string)
- 'operation': I/O operation (json-string, "read" or "write")
- 'action': action that has been taken, it's one of the following:
"ignore": error has been ignored
"report": error has been reported to the device
"stop": error caused VM to be stopped
Example:
{ "event": "BLOCK_IO_ERROR",
"data": { "device": "ide0-hd1",
"operation": "write",
"action": "stop" },
"timestamp": { "seconds": 1265044230, "microseconds": 450486 } }