From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NuDQr-0004Nf-KT for qemu-devel@nongnu.org; Tue, 23 Mar 2010 19:22:45 -0400 Received: from [140.186.70.92] (port=45806 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NuDQq-0004N6-B7 for qemu-devel@nongnu.org; Tue, 23 Mar 2010 19:22:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NuDQp-0003M6-1O for qemu-devel@nongnu.org; Tue, 23 Mar 2010 19:22:44 -0400 Received: from mail2.shareable.org ([80.68.89.115]:37422) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NuDQo-0003M0-QG for qemu-devel@nongnu.org; Tue, 23 Mar 2010 19:22:43 -0400 Date: Tue, 23 Mar 2010 23:22:30 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt Message-ID: <20100323232230.GD20130@shareable.org> References: <4BA7C40C.2040505@codemonkey.ws> <20100323145105.GV16253@redhat.com> <4BA8D8A9.7090308@codemonkey.ws> <201003231557.19474.paul@codesourcery.com> <4BA8E6FC.9080207@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BA8E6FC.9080207@codemonkey.ws> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: "libvir-list@redhat.com" , Paul Brook , qemu-devel@nongnu.org Anthony Liguori wrote: > On 03/23/2010 10:57 AM, Paul Brook wrote: > >I thought the monitor protocol *was* our API. If not, why not? > > It is. But our API is missing key components like guest enumeration. Is that simply enumerating running qemu instances, and asking each one about things like it's name, VNC port, etc.? Having each qemu publish itself through D-Bus or Avahi (to find the list of running instances), and every info query go through the monitor, would seem a clean solution to that. Are there any other missing key components? -- Jamie