Expose whether a mouse is an absolute device via QMP and the human monitor.
[qemu/aliguori-queue.git] / QMP / qmp-events.txt
bloba94e9b464f6e229f9f0bc170fc4592f8091d971f
1                    QEMU Monitor Protocol Events
2                    ============================
4 BLOCK_IO_ERROR
5 --------------
7 Emitted when a disk I/O error occurs.
9 Data:
11 - "device": device name (json-string)
12 - "operation": I/O operation (json-string, "read" or "write")
13 - "action": action that has been taken, it's one of the following (json-string):
14     "ignore": error has been ignored
15     "report": error has been reported to the device
16     "stop": error caused VM to be stopped
18 Example:
20 { "event": "BLOCK_IO_ERROR",
21     "data": { "device": "ide0-hd1",
22               "operation": "write",
23               "action": "stop" },
24     "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
26 Note: If action is "stop", a STOP event will eventually follow the
27 BLOCK_IO_ERROR event.
29 RESET
30 -----
32 Emitted when the Virtual Machine is reseted.
34 Data: None.
36 Example:
38 { "event": "RESET",
39     "timestamp": { "seconds": 1267041653, "microseconds": 9518 } }
41 RTC_CHANGE
42 ----------
44 Emitted when the RTC time changes.
46 Data:
48 - "offset": delta against the host UTC in seconds (json-number)
50 Example:
52 { "event": "RTC_CHANGE",
53     "data": { "offset": 78 },
54     "timestamp": { "seconds": 1267020223, "microseconds": 435656 } }
56 SHUTDOWN
57 --------
59 Emitted when the Virtual Machine is powered down.
61 Data: None.
63 Example:
65 { "event": "SHUTDOWN",
66     "timestamp": { "seconds": 1267040730, "microseconds": 682951 } }
68 Note: If the command-line option "-no-shutdown" has been specified, a STOP
69 event will eventually follow the SHUTDOWN event.
71 STOP
72 ----
74 Emitted when the Virtual Machine is stopped.
76 Data: None.
78 Example:
80 { "event": "SHUTDOWN",
81     "timestamp": { "seconds": 1267041730, "microseconds": 281295 } }
83 VNC_CONNECTED
84 -------------
86 Emitted when a VNC client establishes a connection.
88 Data:
90 - "server": Server information (json-object)
91   - "host": IP address (json-string)
92   - "service": port number (json-string)
93   - "family": address family (json-string, "ipv4" or "ipv6")
94   - "auth": authentication method (json-string, optional)
95 - "client": Client information (json-object)
96   - "host": IP address (json-string)
97   - "service": port number (json-string)
98   - "family": address family (json-string, "ipv4" or "ipv6")
100 Example:
102 { "event": "VNC_CONNECTED",
103     "data": {
104         "server": { "auth": "sasl", "family": "ipv4",
105                     "service": "5901", "host": "0.0.0.0" },
106         "client": { "family": "ipv4", "service": "58425",
107                     "host": "127.0.0.1" } },
108     "timestamp": { "seconds": 1262976601, "microseconds": 975795 } }
111 Note: This event is emitted before any authentication takes place, thus
112 the authentication ID is not provided.
114 VNC_DISCONNECTED
115 ----------------
117 Emitted when the conection is closed.
119 Data:
121 - "server": Server information (json-object)
122   - "host": IP address (json-string)
123   - "service": port number (json-string)
124   - "family": address family (json-string, "ipv4" or "ipv6")
125   - "auth": authentication method (json-string, optional)
126 - "client": Client information (json-object)
127   - "host": IP address (json-string)
128   - "service": port number (json-string)
129   - "family": address family (json-string, "ipv4" or "ipv6")
130   - "x509_dname": TLS dname (json-string, optional)
131   - "sasl_username": SASL username (json-string, optional)
133 Example:
135 { "event": "VNC_DISCONNECTED",
136     "data": {
137         "server": { "auth": "sasl", "family": "ipv4",
138                     "service": "5901", "host": "0.0.0.0" },
139         "client": { "family": "ipv4", "service": "58425",
140                     "host": "127.0.0.1", "sasl_username": "luiz" } },
141     "timestamp": { "seconds": 1262976601, "microseconds": 975795 } }
143 VNC_INITIALIZED
144 ---------------
146 Emitted after authentication takes place (if any) and the VNC session is
147 made active.
149 Data:
151 - "server": Server information (json-object)
152   - "host": IP address (json-string)
153   - "service": port number (json-string)
154   - "family": address family (json-string, "ipv4" or "ipv6")
155   - "auth": authentication method (json-string, optional)
156 - "client": Client information (json-object)
157   - "host": IP address (json-string)
158   - "service": port number (json-string)
159   - "family": address family (json-string, "ipv4" or "ipv6")
160   - "x509_dname": TLS dname (json-string, optional)
161   - "sasl_username": SASL username (json-string, optional)
163 Example:
165 { "event": "VNC_INITIALIZED",
166     "data": {
167         "server": { "auth": "sasl", "family": "ipv4",
168                     "service": "5901", "host": "0.0.0.0"},
169         "client": { "family": "ipv4", "service": "46089",
170                     "host": "127.0.0.1", "sasl_username": "luiz" } },
171         "timestamp": { "seconds": 1263475302, "microseconds": 150772 } }
173 WATCHDOG
174 --------
176 Emitted when the watchdog device's timer is expired.
178 Data:
180 - "action": Action that has been taken, it's one of the following (json-string):
181             "reset", "shutdown", "poweroff", "pause", "debug", or "none"
183 Example:
185 { "event": "WATCHDOG",
186      "data": { "action": "reset" },
187      "timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
189 Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is
190 followed respectively by the RESET, SHUTDOWN, or STOP events.