From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O6POF-0000jR-HG for qemu-devel@nongnu.org; Mon, 26 Apr 2010 10:34:27 -0400 Received: from [140.186.70.92] (port=36537 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O6POE-0000iR-3b for qemu-devel@nongnu.org; Mon, 26 Apr 2010 10:34:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O6POC-0002n8-Bz for qemu-devel@nongnu.org; Mon, 26 Apr 2010 10:34:25 -0400 Received: from mx1.redhat.com ([209.132.183.28]:61294) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O6POC-0002n0-2t for qemu-devel@nongnu.org; Mon, 26 Apr 2010 10:34:24 -0400 Message-ID: <4BD5A46E.9090808@redhat.com> Date: Mon, 26 Apr 2010 17:34:22 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [libvirt] [Qemu-devel] Re: Libvirt debug API References: <4BBF2E93.3020508@redhat.com> <20100409142717.GA11875@redhat.com> <20100412122013.58894a64@redhat.com> <4BD09A3B.3090001@codemonkey.ws> <4BD1971B.7060907@redhat.com> <4BD1A543.1050004@codemonkey.ws> <4BD1ADA2.2050605@redhat.com> <20100423143656.GG17700@redhat.com> <20100426125424.GC16976@shareable.org> <4BD5A26A.90003@redhat.com> In-Reply-To: <4BD5A26A.90003@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Chris Lalancette Cc: Libvirt , Jiri Denemark , qemu-devel@nongnu.org On 04/26/2010 05:25 PM, Chris Lalancette wrote: > Right, and you are probably one of the users this work targets. But in > general, for those not very familiar with virtualization/qemu, we want > to steer them far clear of this API. That goes doubly true for application > developers; we want them to be able to use a stable, long-term API and > not have to worry about the nitty-gritty details of the monitor. It's that > latter group that we want to make sure doesn't use this API. > With qmp, we have a stable long term API, and the nitty-gritty details are easily hidden behind a stock json parser (unfortunately some rpc details remain). The command line is baroque, but the libvirt xml isn't so pretty either. The problem is a user that starts with libvirt and outgrows its featureset. Do we want them to fall back to qmp? -- error compiling committee.c: too many arguments to function