Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt

From: Alexander Graf <agraf@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>,
	qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
	Paul Brook <paul@codesourcery.com>,
	Vincent Hanquez <tab@snarc.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt
Date: Thu, 25 Mar 2010 17:30:28 +0100	[thread overview]
Message-ID: <4BAB8FA4.6000803@suse.de> (raw)
In-Reply-To: <4BAB88EA.3020509@codemonkey.ws>

Anthony Liguori wrote:
> On 03/25/2010 10:16 AM, Daniel P. Berrange wrote:
>> On Thu, Mar 25, 2010 at 03:14:24PM +0000, Vincent Hanquez wrote:
>>   
>>> On Thu, Mar 25, 2010 at 03:07:20PM +0000, Daniel P. Berrange wrote:
>>>     
>>>> I agree apps shouldn't use it for RPC, but admins using the
>>>> interactive user
>>>> monitor are just as deserving of stable commands&  args.
>>>>        
>>> I think, once QMP is completely there, admins would be better using
>>> a qemu-cmd
>>> that's just serialise it's command line arguments into a JSON command.
>>>      
>> Then, after a qemu-cmd is introduced, we should mark the user monitor
>> deprecated
>> along with a specific date/release its future for removal.
>>    
>
> I'm not sure.  The human monitor has some features that are not
> appropriate for QMP.  For instance, the ability to deal with formula
> input and some commands meant to add debugging.
>
> I guess you could do that in qemu-cmd but I don't see a compelling
> reason to.

As I mentioned before, I'd love to see the qemu binary (incl. monitor
interface) being implemented as a pure QMP user. Then libvirt and
friends can be 100% that they can achieve everything using QMP because
we don't live in the same address space anymore and can't pull tricks.

Alex