aboutsummaryrefslogtreecommitdiff
path: root/QMP
diff options
context:
space:
mode:
authorLuiz Capitulino <lcapitulino@redhat.com>2010-04-27 20:35:59 -0300
committerAnthony Liguori <aliguori@us.ibm.com>2010-05-03 12:39:12 -0500
commit6ed2c484f261fd8bd217f855b9e5e5f981e63f0a (patch)
treee95efe58f55934530619e1ff4a7941d54fa3981a /QMP
parent3d54abc7b7f234685ea48bdd1743ed631cf02ba0 (diff)
downloadqemu-6ed2c484f261fd8bd217f855b9e5e5f981e63f0a.zip
qemu-6ed2c484f261fd8bd217f855b9e5e5f981e63f0a.tar.gz
qemu-6ed2c484f261fd8bd217f855b9e5e5f981e63f0a.tar.bz2
QMP: Introduce RESUME event
It's emitted when the Virtual Machine resumes execution. We currently have the STOP event but don't have the matching RESUME one, this means that clients are notified when the VM is stopped but don't get anything when it resumes. Let's fix that as it's already causing some trouble to libvirt. Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'QMP')
-rw-r--r--QMP/qmp-events.txt12
1 files changed, 12 insertions, 0 deletions
diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt
index c084a47..01ec85f 100644
--- a/QMP/qmp-events.txt
+++ b/QMP/qmp-events.txt
@@ -38,6 +38,18 @@ Example:
{ "event": "RESET",
"timestamp": { "seconds": 1267041653, "microseconds": 9518 } }
+RESUME
+------
+
+Emitted when the Virtual Machine resumes execution.
+
+Data: None.
+
+Example:
+
+{ "event": "RESUME",
+ "timestamp": { "seconds": 1271770767, "microseconds": 582542 } }
+
RTC_CHANGE
----------