0d2ed46af4
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>
46 lines
997 B
Plaintext
46 lines
997 B
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 DEBUG
|
|
-------
|
|
|
|
Description: Issued when the Virtual Machine enters debug mode.
|
|
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'.
|