From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJoay-0003YC-Fh for qemu-devel@nongnu.org; Thu, 25 Jun 2009 09:02:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJoas-0003XK-Gy for qemu-devel@nongnu.org; Thu, 25 Jun 2009 09:02:26 -0400 Received: from [199.232.76.173] (port=48053 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJoas-0003XH-AP for qemu-devel@nongnu.org; Thu, 25 Jun 2009 09:02:22 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:11706) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJoar-0000o0-Ta for qemu-devel@nongnu.org; Thu, 25 Jun 2009 09:02:22 -0400 Message-ID: <4A43768A.2090604@eu.citrix.com> Date: Thu, 25 Jun 2009 14:07:22 +0100 From: Stefano Stabellini MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file References: <4A412339.5000109@redhat.com> <4A412659.1080803@us.ibm.com> <20090623220204.GA5612@snarc.org> <4A415C30.7030301@us.ibm.com> <20090624010108.GA6537@snarc.org> <4A42200C.6060600@codemonkey.ws> <5b31733c0906240857g546316e0pd92fee9afe6115fa@mail.gmail.com> <4A4252DD.70300@redhat.com> <20090624190539.GR14121@shareable.org> <5b31733c0906241224j50baa7e6lc80b8c79c5d6baa7@mail.gmail.com> <20090624211358.GA14121@shareable.org> In-Reply-To: <20090624211358.GA14121@shareable.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: "ehabkost@redhat.com" , "jan.kiszka@siemens.com" , "dlaor@redhat.com" , "qemu-devel@nongnu.org" , Luiz Capitulino , Filip Navara , Avi Kivity , Vincent Hanquez Jamie Lokier wrote: > Aren't most QEMU management programs (other than libvirt) scripts? Probably because we didn't provide an rpc interface before. Chichen and egg problem here... > Looks to me like "works with libvirt and other management programs" > implies that you can use it from scripts, because many management > programs are, in fact, scripts. Having the possibility of using it from scripts would be nice but I wouldn't make it a requirement. With an rpc interface and the right scripting language you can still use the rpc interface from a very very short script.