From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FIB69-0000Zi-MZ for qemu-devel@nongnu.org; Sat, 11 Mar 2006 15:54:01 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FIB65-0000Y8-Sq for qemu-devel@nongnu.org; Sat, 11 Mar 2006 15:54:01 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FIB65-0000Y3-NZ for qemu-devel@nongnu.org; Sat, 11 Mar 2006 15:53:57 -0500 Received: from [66.187.233.31] (helo=mx1.redhat.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FIB9f-0006cm-CI for qemu-devel@nongnu.org; Sat, 11 Mar 2006 15:57:39 -0500 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k2BKrtes018448 for ; Sat, 11 Mar 2006 15:53:55 -0500 Received: from devserv.devel.redhat.com (devserv.devel.redhat.com [172.16.58.1]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id k2BKrt127908 for ; Sat, 11 Mar 2006 15:53:55 -0500 Received: from devserv.devel.redhat.com (localhost.localdomain [127.0.0.1]) by devserv.devel.redhat.com (8.12.11/8.12.11) with ESMTP id k2BKrtd9024542 for ; Sat, 11 Mar 2006 15:53:55 -0500 Received: (from veillard@localhost) by devserv.devel.redhat.com (8.12.11/8.12.11/Submit) id k2BKrthY024540 for qemu-devel@nongnu.org; Sat, 11 Mar 2006 15:53:55 -0500 Date: Sat, 11 Mar 2006 15:53:55 -0500 From: Daniel Veillard Subject: Re: [Qemu-devel] [PATCH] Remote console access though socket Message-ID: <20060311205355.GJ346@redhat.com> References: <20060308145211.GG346@redhat.com> <16af12af0603081035h5f61d947y6c24b7a7675eeb14@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Reply-To: veillard@redhat.com, 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 Wed, Mar 08, 2006 at 12:35:13PM -0800, Ed Swierk wrote: > Daniel Veillard wrote: > > enclosed is a first version of a patch to allow remote access and control > > for QEmu instances, I'm not suggesting to apply it as is (though it seems > > to work in my limited testing) but would rather like to get comments back > > for choices I'm facing. > > This sounds pretty nice. A few general comments: > > A few weeks ago I wrote a qemu daemon manager. It's a pretty simple > script that manages multiple qemu processes, launching each one in an > instance of screen. screen does most of the dirty work of keeping > track of running processes, assigning a name to each process, > attaching to a process's console, terminating a process, etc. Of > course screen has many more features that we don't really need, but it > might be worth looking at screen as a model for implementing the > functions you describe. I don't see how this would solve the problems I asked about: - discovery of running instances if not using a filesystem based socket - being able to hook up to qemu instances which are older than the program you're trying to control them from. I know screen, it's good for handling a few number of console, but it's not really what I'm trying to get at, really. [...] > If qemu provides access to its console via a socket, this is just > another resource that a manager can deal with, perhaps passing the > desired port number to qemu via the command line. But for that you need to know the given port a priori, i.e. before lauch which limits a lot the usefulness of the control tool. So far I only see filesystem based discoveey access, I was hoping for something better, maybe there isn't a better way ... Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/