summaryrefslogtreecommitdiff
path: root/monitor.c
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
commit6cec8dcc022ae3fcdea2546c631c5354c7c58900 (patch)
treee95efe58f55934530619e1ff4a7941d54fa3981a /monitor.c
parent1dd45fa2d0512e4eb155dc8377de95a8bc88b784 (diff)
downloadqemu-6cec8dcc022ae3fcdea2546c631c5354c7c58900.tar.gz
qemu-6cec8dcc022ae3fcdea2546c631c5354c7c58900.tar.bz2
qemu-6cec8dcc022ae3fcdea2546c631c5354c7c58900.zip
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 'monitor.c')
-rw-r--r--monitor.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/monitor.c b/monitor.c
index 754bcc5cc0..bb87479f58 100644
--- a/monitor.c
+++ b/monitor.c
@@ -423,6 +423,9 @@ void monitor_protocol_event(MonitorEvent event, QObject *data)
case QEVENT_STOP:
event_name = "STOP";
break;
+ case QEVENT_RESUME:
+ event_name = "RESUME";
+ break;
case QEVENT_VNC_CONNECTED:
event_name = "VNC_CONNECTED";
break;