Bug 518703

We'll either have async monitor messages or even Qmonitor protocol. It depends of the later readiness.

Async messages are already implemented in my qmp-unstable repository (although not reviewed), the only missing piece is the timestamp.

So, I don't think it's a big deal from QEMU's side, but I'm concerned with libvirt.

The basic async messages are always emitted like the following example:

{ "event": "SHUTDOWN", "timestamp": "" }

This is simple and can be parsed with fscanf(), another important information is that support for multiple monitors on the command-line has been merged upstream. So, libvirt could open an additional monitor channel only for async messages.

Now, the point is whether this is feasible as it may have concurrency and related problems.

We already have most of the protocol and basic async messages merged upstream (they are in the RHEL6's qemu-kvm branch already too).

The protocol is already functional, but the following is missing for RHEL6:

- Feature negotiation
- Some async messages
- Some more commands conversions

All of those features are going to be handled in different tickets, so either we close this one or we add the others as a dependency.

IBM is signed up to test and provide feedback.

Ok, they can contact me if they need assistance.

On RHEL-6, the KVM userspace package is named "qemu-kvm". Moving bug to the right component.

Luiz, can you please add the dependents you mention in comment 4 and we can just use this as a tracker?

Done for the most important features, I still have to create a ticket to hold all our bugs.

Converting to tracker to track the dependent items.

Removing all flags since this is now a tracker.

------- Comment From ryanh.com 2010-02-25 14:07 EDT-------
QMP is upstream (as of 0.12 qemu release); marking code upstream.

Yes, but fwiw, it's a limited "preview" version. Meaning that it's incomplete and unstable.

It's quite better currently.

------- Comment From mdroth.ibm.com 2010-05-03 19:13 EDT-------
verified on snap1:

[root@arsenal ~]# uname -a
Linux arsenal.linuxperf9025.net 2.6.32-22.el6.x86_64 #1 SMP Tue Apr 20 12:10:42 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@arsenal ~]# rpm -q redhat-release
redhat-release-6-6.0.0.24.el6.x86_64
[root@arsenal ~]# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.39.el6.x86_64

[root@arsenal ~]# /usr/libexec/qemu-kvm -qmp tcp:localhost:4444,server
QEMU waiting for connection on: tcp:::1:4444,server
VNC server running on `::1:5900'

...

[root@arsenal QMP]# telnet localhost 4444
Trying ::1...
Connected to localhost.
Escape character is '^]'.
{"QMP": {"version": {"qemu": "0.12.1", "package": " (qemu-kvm-0.12.1.2)"}, "capabilities": []}}
{ "execute" : "qmp_capabilities" }
{"return": {}}
{ "execute" : "query-block" }
{"return": [{"device": "ide1-cd0", "locked": false, "removable": true, "type": "cdrom"}, {"device": "floppy0", "locked": false, "removable": true, "type": "floppy"}, {"device": "sd0", "locked": false, "removable": true, "type": "floppy"}]}
{ "execute" : "query-balloon" }
{"error": {"class": "DeviceNotActive", "desc": "The balloon device has not been activated by the guest", "data": {"device": "balloon"}}}
{ "execute" : "query-kvm" }
{"return": {"enabled": true, "present": true}}
{ "execute" : "quit" }
Connection closed by foreign host.
[root@arsenal QMP]