|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file |
Date: | Fri, 26 Jun 2009 12:00:54 +0300 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Thunderbird/3.0b2 |
On 06/25/2009 10:03 PM, Daniel P. Berrange wrote:
On Thu, Jun 25, 2009 at 01:10:36PM -0500, Anthony Liguori wrote:Stefano Stabellini wrote:Clearly I agree with Avi. I am thinking for example that we could use the RPC protocol directly>from Xend and I am sure other people will find it useful too.But you can also use QMP from Xend. In fact, it should be pretty easy to convert the current code in Xend to use QMP.AFAIK, the current XenD code doesn't talk to the QEMU monitor at all, instead having a add-on to QEMU code which pulls info from XenStored. That doesn't alter your point though, it would be pretty easy to make XenD talk to the proposed QMP monitor if desired.
All it takes is implementing QMP, and an emitter/parser for each qemu command. On the other hand, things like xml-rpc require around one line of code in Python per command.
Let's turn this around. IIRC libvirt uses an RPC interface for its clients. How would you estimate the effort to port this interface to QMP, and adapt all its clients?
-- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.
[Prev in Thread] | Current Thread | [Next in Thread] |