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] xen-2.0: privileged port connections

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xen-2.0: privileged port connections
From: Christian Limpach <christian.limpach@xxxxxxxxx>
Date: Wed, 23 Mar 2005 21:37:49 +0000
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Kurt Garloff <garloff@xxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, ian.pratt@xxxxxxxxxxxx
Delivery-date: Wed, 23 Mar 2005 21:38:40 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=tlcsPeGkNik+bObRGcZQ6NVG24hPXqcJvUIXRQmZoYTGBLB9Otio2twjs/99ILv/oDVnKfz2m0i2M33zknYB3tg5Rw9ffQS1kUNXph00Xx8HKLZiSQEk9Z8NztrE6E0ExUrpIWbgEkXKPFhJYOkTYAJdvJ+xg97woL3dQCyi25s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4241C314.4030902@xxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3822@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <4241C314.4030902@xxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
On Wed, 23 Mar 2005 13:27:16 -0600, Anthony Liguori <aliguori@xxxxxxxxxx> wrote:
> Perhaps we could export the console via a pty and then create a screen
> session by executing the equivalent of "screen vm-console domid".
> Clients can then connect to it by executing screen -x (instead of
> connecting directly to the pty) and our client could translate C-] to
> C-a C-d to detach from the screen.  Any reconnects will perserve the
> screen of the previous session.

Yes, I think this is what we want.  Although I thought we could
probably change screen's keyboard mapping such that C-] is the escape
character and at the same time finally get support for sending C-] to
the domain -- I keep getting stuck in nested xencons clients...
You can have screen -x as a login shell or run it from command= in a
.ssh/authorized_keys file.

> This way, we can still have minimalistic toolchains that provide serial
> style consoles.

I think it should be an option in the domain configuration file
whether the domain creating tool should also setup a screen session
backing the console.  I think this needs to be somehow linked to the
domain creation tool because otherwise you won't capture the entire
If we support multiple consoles for a single domain, it would also be
nice to have them all connected to the same screen session, allowing
you to switch between the consoles using C-] 1, C-] 2, ...


This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
Xen-devel mailing list