2010-02-25 16:07:02 +01:00
|
|
|
QEMU Monitor Protocol Events
|
|
|
|
============================
|
2009-11-27 01:59:08 +01:00
|
|
|
|
2012-08-09 16:40:27 +02:00
|
|
|
BALLOON_CHANGE
|
|
|
|
--------------
|
|
|
|
|
|
|
|
Emitted when the guest changes the actual BALLOON level. This
|
|
|
|
value is equivalent to the 'actual' field return by the
|
|
|
|
'query-balloon' command
|
|
|
|
|
|
|
|
Data:
|
|
|
|
|
|
|
|
- "actual": actual level of the guest memory balloon in bytes (json-number)
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "BALLOON_CHANGE",
|
|
|
|
"data": { "actual": 944766976 },
|
|
|
|
"timestamp": { "seconds": 1267020223, "microseconds": 435656 } }
|
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
BLOCK_IO_ERROR
|
|
|
|
--------------
|
|
|
|
|
|
|
|
Emitted 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 (json-string):
|
|
|
|
"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 } }
|
|
|
|
|
|
|
|
Note: If action is "stop", a STOP event will eventually follow the
|
|
|
|
BLOCK_IO_ERROR event.
|
|
|
|
|
2012-08-09 16:40:27 +02:00
|
|
|
BLOCK_JOB_CANCELLED
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
Emitted when a block job has been cancelled.
|
|
|
|
|
|
|
|
Data:
|
|
|
|
|
QAPI: add command for live block commit, 'block-commit'
The command for live block commit is added, which has the following
arguments:
device: the block device to perform the commit on (mandatory)
base: the base image to commit into; optional (if not specified,
it is the underlying original image)
top: the top image of the commit - all data from inside top down
to base will be committed into base (mandatory for now; see
note, below)
speed: maximum speed, in bytes/sec
Note: Eventually this command will support merging down the active layer,
but that code is not yet complete. If the active layer is passed
in as top, then an error will be returned. Once merging down the
active layer is supported, the 'top' argument may become optional,
and default to the active layer.
The is done as a block job, so upon completion a BLOCK_JOB_COMPLETED will
be emitted.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
2012-09-27 19:29:16 +02:00
|
|
|
- "type": Job type (json-string; "stream" for image streaming
|
|
|
|
"commit" for block commit)
|
2012-08-09 16:40:27 +02:00
|
|
|
- "device": Device name (json-string)
|
|
|
|
- "len": Maximum progress value (json-int)
|
|
|
|
- "offset": Current progress value (json-int)
|
|
|
|
On success this is equal to len.
|
|
|
|
On failure this is less than len.
|
|
|
|
- "speed": Rate limit, bytes per second (json-int)
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "BLOCK_JOB_CANCELLED",
|
|
|
|
"data": { "type": "stream", "device": "virtio-disk0",
|
|
|
|
"len": 10737418240, "offset": 134217728,
|
|
|
|
"speed": 0 },
|
|
|
|
"timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
|
|
|
|
|
|
|
|
BLOCK_JOB_COMPLETED
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
Emitted when a block job has completed.
|
|
|
|
|
|
|
|
Data:
|
|
|
|
|
QAPI: add command for live block commit, 'block-commit'
The command for live block commit is added, which has the following
arguments:
device: the block device to perform the commit on (mandatory)
base: the base image to commit into; optional (if not specified,
it is the underlying original image)
top: the top image of the commit - all data from inside top down
to base will be committed into base (mandatory for now; see
note, below)
speed: maximum speed, in bytes/sec
Note: Eventually this command will support merging down the active layer,
but that code is not yet complete. If the active layer is passed
in as top, then an error will be returned. Once merging down the
active layer is supported, the 'top' argument may become optional,
and default to the active layer.
The is done as a block job, so upon completion a BLOCK_JOB_COMPLETED will
be emitted.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
2012-09-27 19:29:16 +02:00
|
|
|
- "type": Job type (json-string; "stream" for image streaming
|
|
|
|
"commit" for block commit)
|
2012-08-09 16:40:27 +02:00
|
|
|
- "device": Device name (json-string)
|
|
|
|
- "len": Maximum progress value (json-int)
|
|
|
|
- "offset": Current progress value (json-int)
|
|
|
|
On success this is equal to len.
|
|
|
|
On failure this is less than len.
|
|
|
|
- "speed": Rate limit, bytes per second (json-int)
|
|
|
|
- "error": Error message (json-string, optional)
|
|
|
|
Only present on failure. This field contains a human-readable
|
|
|
|
error message. There are no semantics other than that streaming
|
|
|
|
has failed and clients should not try to interpret the error
|
|
|
|
string.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "BLOCK_JOB_COMPLETED",
|
|
|
|
"data": { "type": "stream", "device": "virtio-disk0",
|
|
|
|
"len": 10737418240, "offset": 10737418240,
|
|
|
|
"speed": 0 },
|
|
|
|
"timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
|
|
|
|
|
block: introduce block job error
The following behaviors are possible:
'report': The behavior is the same as in 1.1. An I/O error,
respectively during a read or a write, will complete the job immediately
with an error code.
'ignore': An I/O error, respectively during a read or a write, will be
ignored. For streaming, the job will complete with an error and the
backing file will be left in place. For mirroring, the sector will be
marked again as dirty and re-examined later.
'stop': The job will be paused and the job iostatus will be set to
failed or nospace, while the VM will keep running. This can only be
specified if the block device has rerror=stop and werror=stop or enospc.
'enospc': Behaves as 'stop' for ENOSPC errors, 'report' for others.
In all cases, even for 'report', the I/O error is reported as a QMP
event BLOCK_JOB_ERROR, with the same arguments as BLOCK_IO_ERROR.
It is possible that while stopping the VM a BLOCK_IO_ERROR event will be
reported and will clobber the event from BLOCK_JOB_ERROR, or vice versa.
This is not really avoidable since stopping the VM completes all pending
I/O requests. In fact, it is already possible now that a series of
BLOCK_IO_ERROR events are reported with rerror=stop, because vm_stop
calls bdrv_drain_all and this can generate further errors.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
2012-09-28 17:22:58 +02:00
|
|
|
BLOCK_JOB_ERROR
|
|
|
|
---------------
|
|
|
|
|
|
|
|
Emitted when a block job encounters an error.
|
|
|
|
|
|
|
|
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 (json-string):
|
|
|
|
"ignore": error has been ignored, the job may fail later
|
|
|
|
"report": error will be reported and the job canceled
|
|
|
|
"stop": error caused job to be paused
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "BLOCK_JOB_ERROR",
|
|
|
|
"data": { "device": "ide0-hd1",
|
|
|
|
"operation": "write",
|
|
|
|
"action": "stop" },
|
|
|
|
"timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
|
|
|
|
|
2012-02-14 16:41:13 +01:00
|
|
|
DEVICE_TRAY_MOVED
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
It's emitted whenever the tray of a removable device is moved by the guest
|
|
|
|
or by HMP/QMP commands.
|
|
|
|
|
|
|
|
Data:
|
|
|
|
|
|
|
|
- "device": device name (json-string)
|
|
|
|
- "tray-open": true if the tray has been opened or false if it has been closed
|
|
|
|
(json-bool)
|
|
|
|
|
|
|
|
{ "event": "DEVICE_TRAY_MOVED",
|
|
|
|
"data": { "device": "ide1-cd0",
|
|
|
|
"tray-open": true
|
|
|
|
},
|
|
|
|
"timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
|
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
RESET
|
|
|
|
-----
|
|
|
|
|
|
|
|
Emitted when the Virtual Machine is reseted.
|
2009-11-27 01:59:08 +01:00
|
|
|
|
|
|
|
Data: None.
|
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "RESET",
|
|
|
|
"timestamp": { "seconds": 1267041653, "microseconds": 9518 } }
|
|
|
|
|
2010-04-28 01:35:59 +02:00
|
|
|
RESUME
|
|
|
|
------
|
|
|
|
|
|
|
|
Emitted when the Virtual Machine resumes execution.
|
|
|
|
|
|
|
|
Data: None.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "RESUME",
|
|
|
|
"timestamp": { "seconds": 1271770767, "microseconds": 582542 } }
|
|
|
|
|
2010-02-25 16:11:44 +01:00
|
|
|
RTC_CHANGE
|
|
|
|
----------
|
|
|
|
|
2010-03-24 21:24:37 +01:00
|
|
|
Emitted when the guest changes the RTC time.
|
2010-02-25 16:11:44 +01:00
|
|
|
|
|
|
|
Data:
|
|
|
|
|
|
|
|
- "offset": delta against the host UTC in seconds (json-number)
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "RTC_CHANGE",
|
|
|
|
"data": { "offset": 78 },
|
|
|
|
"timestamp": { "seconds": 1267020223, "microseconds": 435656 } }
|
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
SHUTDOWN
|
|
|
|
--------
|
|
|
|
|
|
|
|
Emitted when the Virtual Machine is powered down.
|
2009-11-27 01:59:08 +01:00
|
|
|
|
|
|
|
Data: None.
|
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "SHUTDOWN",
|
|
|
|
"timestamp": { "seconds": 1267040730, "microseconds": 682951 } }
|
|
|
|
|
|
|
|
Note: If the command-line option "-no-shutdown" has been specified, a STOP
|
|
|
|
event will eventually follow the SHUTDOWN event.
|
|
|
|
|
2012-08-09 16:40:27 +02:00
|
|
|
SPICE_CONNECTED, SPICE_DISCONNECTED
|
|
|
|
-----------------------------------
|
|
|
|
|
|
|
|
Emitted when a SPICE client connects or disconnects.
|
|
|
|
|
|
|
|
Data:
|
|
|
|
|
|
|
|
- "server": Server information (json-object)
|
|
|
|
- "host": IP address (json-string)
|
|
|
|
- "port": port number (json-string)
|
|
|
|
- "family": address family (json-string, "ipv4" or "ipv6")
|
|
|
|
- "client": Client information (json-object)
|
|
|
|
- "host": IP address (json-string)
|
|
|
|
- "port": port number (json-string)
|
|
|
|
- "family": address family (json-string, "ipv4" or "ipv6")
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "timestamp": {"seconds": 1290688046, "microseconds": 388707},
|
|
|
|
"event": "SPICE_CONNECTED",
|
|
|
|
"data": {
|
|
|
|
"server": { "port": "5920", "family": "ipv4", "host": "127.0.0.1"},
|
|
|
|
"client": {"port": "52873", "family": "ipv4", "host": "127.0.0.1"}
|
|
|
|
}}
|
|
|
|
|
|
|
|
SPICE_INITIALIZED
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
Emitted after initial handshake and authentication takes place (if any)
|
|
|
|
and the SPICE channel is up'n'running
|
|
|
|
|
|
|
|
Data:
|
|
|
|
|
|
|
|
- "server": Server information (json-object)
|
|
|
|
- "host": IP address (json-string)
|
|
|
|
- "port": port number (json-string)
|
|
|
|
- "family": address family (json-string, "ipv4" or "ipv6")
|
|
|
|
- "auth": authentication method (json-string, optional)
|
|
|
|
- "client": Client information (json-object)
|
|
|
|
- "host": IP address (json-string)
|
|
|
|
- "port": port number (json-string)
|
|
|
|
- "family": address family (json-string, "ipv4" or "ipv6")
|
|
|
|
- "connection-id": spice connection id. All channels with the same id
|
|
|
|
belong to the same spice session (json-int)
|
|
|
|
- "channel-type": channel type. "1" is the main control channel, filter for
|
|
|
|
this one if you want track spice sessions only (json-int)
|
|
|
|
- "channel-id": channel id. Usually "0", might be different needed when
|
|
|
|
multiple channels of the same type exist, such as multiple
|
|
|
|
display channels in a multihead setup (json-int)
|
|
|
|
- "tls": whevener the channel is encrypted (json-bool)
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "timestamp": {"seconds": 1290688046, "microseconds": 417172},
|
|
|
|
"event": "SPICE_INITIALIZED",
|
|
|
|
"data": {"server": {"auth": "spice", "port": "5921",
|
|
|
|
"family": "ipv4", "host": "127.0.0.1"},
|
|
|
|
"client": {"port": "49004", "family": "ipv4", "channel-type": 3,
|
|
|
|
"connection-id": 1804289383, "host": "127.0.0.1",
|
|
|
|
"channel-id": 0, "tls": true}
|
|
|
|
}}
|
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
STOP
|
|
|
|
----
|
|
|
|
|
|
|
|
Emitted when the Virtual Machine is stopped.
|
2009-11-27 01:59:08 +01:00
|
|
|
|
|
|
|
Data: None.
|
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
Example:
|
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 17:50:57 +01:00
|
|
|
|
2010-10-14 02:51:02 +02:00
|
|
|
{ "event": "STOP",
|
2010-02-25 16:07:02 +01:00
|
|
|
"timestamp": { "seconds": 1267041730, "microseconds": 281295 } }
|
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 17:50:58 +01:00
|
|
|
|
2012-08-09 17:02:21 +02:00
|
|
|
SUSPEND
|
|
|
|
-------
|
|
|
|
|
|
|
|
Emitted when guest enters S3 state.
|
|
|
|
|
|
|
|
Data: None.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "SUSPEND",
|
|
|
|
"timestamp": { "seconds": 1344456160, "microseconds": 309119 } }
|
|
|
|
|
2012-08-08 22:03:01 +02:00
|
|
|
SUSPEND_DISK
|
|
|
|
------------
|
|
|
|
|
|
|
|
Emitted when the guest makes a request to enter S4 state.
|
|
|
|
|
|
|
|
Data: None.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "SUSPEND_DISK",
|
|
|
|
"timestamp": { "seconds": 1344456160, "microseconds": 309119 } }
|
|
|
|
|
|
|
|
Note: QEMU shuts down when entering S4 state.
|
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
VNC_CONNECTED
|
|
|
|
-------------
|
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 17:50:58 +01:00
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
Emitted when a VNC client establishes a connection.
|
|
|
|
|
|
|
|
Data:
|
|
|
|
|
|
|
|
- "server": Server information (json-object)
|
|
|
|
- "host": IP address (json-string)
|
|
|
|
- "service": port number (json-string)
|
|
|
|
- "family": address family (json-string, "ipv4" or "ipv6")
|
|
|
|
- "auth": authentication method (json-string, optional)
|
|
|
|
- "client": Client information (json-object)
|
|
|
|
- "host": IP address (json-string)
|
|
|
|
- "service": port number (json-string)
|
|
|
|
- "family": address family (json-string, "ipv4" or "ipv6")
|
|
|
|
|
|
|
|
Example:
|
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 17:50:59 +01:00
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
{ "event": "VNC_CONNECTED",
|
|
|
|
"data": {
|
|
|
|
"server": { "auth": "sasl", "family": "ipv4",
|
|
|
|
"service": "5901", "host": "0.0.0.0" },
|
|
|
|
"client": { "family": "ipv4", "service": "58425",
|
|
|
|
"host": "127.0.0.1" } },
|
|
|
|
"timestamp": { "seconds": 1262976601, "microseconds": 975795 } }
|
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 17:50:59 +01:00
|
|
|
|
2010-02-03 15:41:00 +01:00
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
Note: This event is emitted before any authentication takes place, thus
|
|
|
|
the authentication ID is not provided.
|
|
|
|
|
|
|
|
VNC_DISCONNECTED
|
2010-02-03 15:41:00 +01:00
|
|
|
----------------
|
|
|
|
|
2011-11-22 11:06:19 +01:00
|
|
|
Emitted when the connection is closed.
|
2010-02-25 16:07:02 +01:00
|
|
|
|
2010-02-03 15:41:00 +01:00
|
|
|
Data:
|
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
- "server": Server information (json-object)
|
|
|
|
- "host": IP address (json-string)
|
|
|
|
- "service": port number (json-string)
|
|
|
|
- "family": address family (json-string, "ipv4" or "ipv6")
|
|
|
|
- "auth": authentication method (json-string, optional)
|
|
|
|
- "client": Client information (json-object)
|
|
|
|
- "host": IP address (json-string)
|
|
|
|
- "service": port number (json-string)
|
|
|
|
- "family": address family (json-string, "ipv4" or "ipv6")
|
|
|
|
- "x509_dname": TLS dname (json-string, optional)
|
|
|
|
- "sasl_username": SASL username (json-string, optional)
|
2010-02-03 15:41:00 +01:00
|
|
|
|
|
|
|
Example:
|
|
|
|
|
2010-02-25 16:07:02 +01:00
|
|
|
{ "event": "VNC_DISCONNECTED",
|
|
|
|
"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": "luiz" } },
|
|
|
|
"timestamp": { "seconds": 1262976601, "microseconds": 975795 } }
|
|
|
|
|
|
|
|
VNC_INITIALIZED
|
|
|
|
---------------
|
|
|
|
|
|
|
|
Emitted after authentication takes place (if any) and the VNC session is
|
|
|
|
made active.
|
|
|
|
|
|
|
|
Data:
|
|
|
|
|
|
|
|
- "server": Server information (json-object)
|
|
|
|
- "host": IP address (json-string)
|
|
|
|
- "service": port number (json-string)
|
|
|
|
- "family": address family (json-string, "ipv4" or "ipv6")
|
|
|
|
- "auth": authentication method (json-string, optional)
|
|
|
|
- "client": Client information (json-object)
|
|
|
|
- "host": IP address (json-string)
|
|
|
|
- "service": port number (json-string)
|
|
|
|
- "family": address family (json-string, "ipv4" or "ipv6")
|
|
|
|
- "x509_dname": TLS dname (json-string, optional)
|
|
|
|
- "sasl_username": SASL username (json-string, optional)
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "VNC_INITIALIZED",
|
|
|
|
"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": "luiz" } },
|
|
|
|
"timestamp": { "seconds": 1263475302, "microseconds": 150772 } }
|
2010-02-25 16:13:04 +01:00
|
|
|
|
2012-08-09 16:27:30 +02:00
|
|
|
WAKEUP
|
|
|
|
------
|
|
|
|
|
|
|
|
Emitted when the guest has woken up from S3 and is running.
|
|
|
|
|
|
|
|
Data: None.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "WATCHDOG",
|
|
|
|
"timestamp": { "seconds": 1344522075, "microseconds": 745528 } }
|
|
|
|
|
2010-02-25 16:13:04 +01:00
|
|
|
WATCHDOG
|
|
|
|
--------
|
|
|
|
|
|
|
|
Emitted when the watchdog device's timer is expired.
|
|
|
|
|
|
|
|
Data:
|
|
|
|
|
|
|
|
- "action": Action that has been taken, it's one of the following (json-string):
|
|
|
|
"reset", "shutdown", "poweroff", "pause", "debug", or "none"
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
{ "event": "WATCHDOG",
|
|
|
|
"data": { "action": "reset" },
|
|
|
|
"timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
|
|
|
|
|
|
|
|
Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is
|
|
|
|
followed respectively by the RESET, SHUTDOWN, or STOP events.
|