[Qemu-devel] Re: [RFC][PATCH v7 00/16] virtagent: host/guest communication agent

[Anthony Liguori]

On 03/07/2011 04:49 PM, Michael Roth wrote:
> It's not really inventing anything. We've always started off with 
> qobject params, which we then pulled apart and stuck into xmlrpc 
> params, which when then turned into xml for transport. Now we just 
> take the qobjects and covert them to json directly. We've only cut out 
> an intermediate library and switched to a different UTF8-based 
> encoding for transport.
>
> With QAPI we'd have the extra step of pulling function parameters into 
> a qobjects. Not any different from what the situation would've been 
> using xmlrpc or any of the other binary encoding that were considered.
>
> It does look more similar to what QMP/QAPI is doing than previously, 
> but it doesn't need to be all or nothing.

I think I have a Clever Idea here but hacking together a prototype.

Basic thinking is to make guest commands part of the QMP namespace such 
that a guest command looks like any other QMP command.  The only role 
QEMU plays in this model is validating the commands inputs and outputs 
and then passing the command to the guest agent.

Stay tuned.

Regards,

Anthony Liguori

> > Regards,
> >
> > Anthony Liguori