This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] [PATCH] Console Daemon

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Anthony Liguori" <aliguori@xxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Console Daemon
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 2 Aug 2005 15:45:52 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>, Robert Read <robert@xxxxxxxxxxxxx>
Delivery-date: Tue, 02 Aug 2005 14:44:18 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWXXKh5CuAmSUtuS8u473HhpYIsdgAEzDiQ
Thread-topic: [Xen-devel] [PATCH] Console Daemon
> > This is the first patch to move the console code out of 
> Xend and into 
> > a separate daemon.  In this patch I've included the daemon and a 
> > front-end.  I've also have the console code removed from 
> Xend locally 
> > but I wanted to clarify a few things first before submitting that.
> I checked in consoled. Can you send any further fixes, and 
> code to plumb through xend?
> Is it possible to make it configurable where console i/o goes 
> (e.g., tcp socket as an option instead of tty?).

I guess it would be nice to have tcp sockets as an option (with a
optional restriction to localhost access), but not a huge deal. In any
event, xend needs to know of, or prefereable be in control of, which tty
or port gets allocated.

What I'd really like to see this console deamon do is to implement a
FIFO buffer of the last N megabytes of console output, hence providing
buffering while the tty is disconnected. Regardless of whether the tty
is connected, it would be good to keep the last M megabytes stored on
disk in /var/log/xen-myvmname.


Xen-devel mailing list