From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJuE9-000273-I6 for qemu-devel@nongnu.org; Thu, 25 Jun 2009 15:03:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJuE4-00020G-8n for qemu-devel@nongnu.org; Thu, 25 Jun 2009 15:03:16 -0400 Received: from [199.232.76.173] (port=48239 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJuE3-0001zj-DV for qemu-devel@nongnu.org; Thu, 25 Jun 2009 15:03:11 -0400 Received: from mx1.redhat.com ([66.187.233.31]:52049) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJuE2-0000ut-N5 for qemu-devel@nongnu.org; Thu, 25 Jun 2009 15:03:10 -0400 Date: Thu, 25 Jun 2009 20:03:02 +0100 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file Message-ID: <20090625190302.GA11937@redhat.com> References: <4A4252DD.70300@redhat.com> <20090624190539.GR14121@shareable.org> <5b31733c0906241224j50baa7e6lc80b8c79c5d6baa7@mail.gmail.com> <20090624211358.GA14121@shareable.org> <4A43768A.2090604@eu.citrix.com> <4A438FDD.5060206@redhat.com> <4A43935D.6000506@codemonkey.ws> <4A4395B8.4010401@redhat.com> <4A43AE13.4030900@eu.citrix.com> <4A43BD9C.8070304@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A43BD9C.8070304@codemonkey.ws> Reply-To: "Daniel P. Berrange" List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: "ehabkost@redhat.com" , Stefano Stabellini , "jan.kiszka@siemens.com" , "dlaor@redhat.com" , "qemu-devel@nongnu.org" , Luiz Capitulino , Filip Navara , Avi Kivity , Vincent Hanquez On Thu, Jun 25, 2009 at 01:10:36PM -0500, Anthony Liguori wrote: > Stefano Stabellini wrote: > > > >Clearly I agree with Avi. > >I am thinking for example that we could use the RPC protocol directly > >from Xend and I am sure other people will find it useful too. > > > > But you can also use QMP from Xend. In fact, it should be pretty easy > to convert the current code in Xend to use QMP. AFAIK, the current XenD code doesn't talk to the QEMU monitor at all, instead having a add-on to QEMU code which pulls info from XenStored. That doesn't alter your point though, it would be pretty easy to make XenD talk to the proposed QMP monitor if desired. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|