From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G4guj-00009l-Tl for qemu-devel@nongnu.org; Sun, 23 Jul 2006 12:34:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G4guj-00009Z-Cx for qemu-devel@nongnu.org; Sun, 23 Jul 2006 12:34:45 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G4guj-00009V-5p for qemu-devel@nongnu.org; Sun, 23 Jul 2006 12:34:45 -0400 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1G4gvc-0005tp-NU for qemu-devel@nongnu.org; Sun, 23 Jul 2006 12:35:40 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1G4guh-00067O-2C for qemu-devel@nongnu.org; Sun, 23 Jul 2006 18:34:43 +0200 Received: from cpe-70-116-9-243.austin.res.rr.com ([70.116.9.243]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 23 Jul 2006 18:34:43 +0200 Received: from anthony by cpe-70-116-9-243.austin.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 23 Jul 2006 18:34:43 +0200 From: Anthony Liguori Date: Sun, 23 Jul 2006 11:34:34 -0500 Message-ID: References: <44C11ED6.3090006@opensourcedemo.com> <20060723113929.GB4412@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Sender: news Subject: [Qemu-devel] Re: Re: QEMU GUI-Frontend based on Libvert API Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Sun, 23 Jul 2006 12:39:29 +0100, Daniel P. Berrange wrote: >> I have toyed around with the idea of writing an XML-RPC front-end to >> QEMU (with the idea of bridging the gap for libvirt). DV also had a >> patch floating around to add a socket management interface to QEMU >> (although now there is a TCP character device so I presume his patch is >> unnecessary). > > If there was a way to enumerate all running QEMU instances on a machine in > a reasonably fast manner (ie, not reading every single /proc/PID entry), > the existing QEMU monitor interface exposes enough functionality to > support most of libvirt API. The approach I took was to have all qemu spawning be done through a single daemon that could keep track of running instances. In the general case, I don't think there's a way to do it. Plus, you want to make sure that each instance has the monitor on some reconnectable interface. Regards, Anthony Liguori > So the main questions are how to enumerate > QEMU instances & how to connect to the monitor - UNIX, TCP, or XML-RPC are > all possible options with plus/minuses. UNIX is nice because you can > manage security with simple file permissions on the socket. TCP/XML-RPC is > nice because you can manage VMs remotely - but you'd need to do some kind > of sensible auth scheme in remote case - unlike Xen which allows anyone to > connect :-( > > Regards, > Dan,