From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NupVM-0001oq-AV for qemu-devel@nongnu.org; Thu, 25 Mar 2010 12:01:58 -0400 Received: from [140.186.70.92] (port=46460 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NupVL-0001nj-2V for qemu-devel@nongnu.org; Thu, 25 Mar 2010 12:01:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NupVJ-0005Et-JK for qemu-devel@nongnu.org; Thu, 25 Mar 2010 12:01:54 -0400 Received: from mail-ew0-f221.google.com ([209.85.219.221]:37710) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NupVJ-0005Eo-B2 for qemu-devel@nongnu.org; Thu, 25 Mar 2010 12:01:53 -0400 Received: by ewy21 with SMTP id 21so1822410ewy.5 for ; Thu, 25 Mar 2010 09:01:52 -0700 (PDT) Message-ID: <4BAB88EA.3020509@codemonkey.ws> Date: Thu, 25 Mar 2010 11:01:46 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt References: <4BAA6CD9.6060001@redhat.com> <20100324171219.4365318b@redhat.com> <4BAA76EA.2060601@codemonkey.ws> <20100324182501.000b69a7@redhat.com> <4BAA86C2.4020701@codemonkey.ws> <4BAB1E21.8080009@snarc.org> <20100325135922.GB10705@redhat.com> <20100325145652.GA25506@snarc.org> <20100325150720.GH10705@redhat.com> <20100325151424.GB25506@snarc.org> <20100325151644.GI10705@redhat.com> In-Reply-To: <20100325151644.GI10705@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: "Daniel P. Berrange" Cc: "libvir-list@redhat.com" , qemu-devel@nongnu.org, Luiz Capitulino , Paul Brook , Vincent Hanquez , Avi Kivity 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. Regards, Anthony Liguori > Daniel >