2009-11-27 03:59:08 +03:00
|
|
|
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 DEBUG
|
|
|
|
|
-------
|
|
|
|
|
|
|
|
|
|
Description: Issued when the Virtual Machine enters debug mode.
|
|
|
|
|
Data: None.
|
QMP: Introduce VNC_CONNECTED event
It's emitted when a VNC client connects to QEMU, client's information
such as port and IP address are provided.
Note that this event is emitted right when the connection is
established. This means that it happens before authentication
procedure and session initialization.
Event example:
{ "event": "VNC_CONNECTED",
"timestamp": { "seconds": 1262976601, "microseconds": 975795 },
"data": {
"server": { "auth": "sasl", "family": "ipv4",
"service": "5901", "host": "0.0.0.0" },
"client": { "family": "ipv4", "service": "58425",
"host": "127.0.0.1" } } }
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-01-14 19:50:57 +03:00
|
|
|
|
|
|
|
|
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.
|
QMP: Introduce VNC_DISCONNECTED event
It's emitted when a VNC client disconnects from QEMU, client's
information such as port and IP address are provided.
Event example:
{ "event": "VNC_DISCONNECTED",
"timestamp": { "seconds": 1262976601, "microseconds": 975795 },
"data": {
"server": { "auth": "sasl", "family": "ipv4",
"service": "5901", "host": "0.0.0.0" },
"client": { "family": "ipv4", "service": "58425",
"host": "127.0.0.1", "sasl_username": "foo" } } }
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-01-14 19:50:58 +03:00
|
|
|
|
|
|
|
|
5 VNC_DISCONNECTED
|
|
|
|
|
------------------
|
|
|
|
|
|
|
|
|
|
Description: Issued when the conection is closed.
|
|
|
|
|
Data: 'server' and 'client' keys with the same keys as 'query-vnc'.
|
QMP: Introduce VNC_INITIALIZED event
It's emitted when a VNC client session is activated by QEMU,
client's information such as port, IP and auth ID (if the
session is authenticated) are provided.
Event example:
{ "event": "VNC_INITIALIZED",
"timestamp": {"seconds": 1263475302, "microseconds": 150772},
"data": {
"server": { "auth": "sasl", "family": "ipv4",
"service": "5901", "host": "0.0.0.0"},
"client": { "family": "ipv4", "service": "46089",
"host": "127.0.0.1", "sasl_username": "lcapitulino" } } }
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-01-14 19:50:59 +03:00
|
|
|
|
|
|
|
|
6 VNC_INITIALIZED
|
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
|
|
Description: Issued when the VNC session is made active.
|
|
|
|
|
Data: 'server' and 'client' keys with the same keys as 'query-vnc'.
|
2010-02-03 17:41:00 +03:00
|
|
|
|
|
|
|
|
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 } }
|
