From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJqLT-0000UV-5t for qemu-devel@nongnu.org; Thu, 25 Jun 2009 10:54:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJqLO-0000Pm-UD for qemu-devel@nongnu.org; Thu, 25 Jun 2009 10:54:34 -0400 Received: from [199.232.76.173] (port=60682 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJqLO-0000Pf-RH for qemu-devel@nongnu.org; Thu, 25 Jun 2009 10:54:30 -0400 Received: from mx2.redhat.com ([66.187.237.31]:36364) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJqLO-0003F1-9y for qemu-devel@nongnu.org; Thu, 25 Jun 2009 10:54:30 -0400 Message-ID: <4A438FDD.5060206@redhat.com> Date: Thu, 25 Jun 2009 17:55:25 +0300 From: Avi Kivity 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> <4A43768A.2090604@eu.citrix.com> In-Reply-To: <4A43768A.2090604@eu.citrix.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefano Stabellini Cc: "ehabkost@redhat.com" , "jan.kiszka@siemens.com" , "dlaor@redhat.com" , "qemu-devel@nongnu.org" , Luiz Capitulino , Filip Navara , Vincent Hanquez On 06/25/2009 04:07 PM, Stefano Stabellini wrote: >> 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. > I'd go further and make shell script support a non-goal. Maybe the majority of qemu control programs are scripts, but only a tiny minority of VMs are controlled by shell scripts. It is nearly impossible to write a correct nontrivial program in bash; and scripts will be slow due to the need to constantly fork/exec/connect. Serious management programs will be written in real languages, and that's what we should optimize for. -- error compiling committee.c: too many arguments to function