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: RE: [Xen-devel] [PATCH] xen-2.0: privileged port connections

To: "Kurt Garloff" <kurt@xxxxxxxxxx>
Subject: RE: RE: [Xen-devel] [PATCH] xen-2.0: privileged port connections
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 23 Mar 2005 22:16:57 -0000
Cc: "Xen development list" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, "Anthony Liguori" <aliguori@xxxxxxxxxx>, <ian.pratt@xxxxxxxxxxxx>
Delivery-date: Wed, 23 Mar 2005 22:19:47 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcUv8OlXIQgyDNV1T1edmSNjtZhKMgABCznQ
Thread-topic: RE: [Xen-devel] [PATCH] xen-2.0: privileged port connections
> > Perhaps a better way to handle consoles would be to use 
> 'screend', and
> > then have incoming ssh connections dispatched to particular screen
> > sessions.
> screen is what is commonly used to handle many (mostly 
> serial) consoles
> these days, so hooking into that is certainly something most sysadmins
> would consider a natural choice.

I think we've got resounding agreement on using screen.
> > > > 5) you still have to deal with xfrd
> > > 
> > > It seems to listen on *:8002 ... 
> > > Is there no authentication either? Sigh.
> > > 
> > > And we probably need to look into the event channel 
> (8001) as well.
> > 
> > Xfrd needs an option to listen only on localhost. (It's 
> still needed for
> > save/restore even if you don't use migrate).
> We could just pass it an option during startup.

Yep, though it should be configurable from the xend config.

> > The event channel only ever needs to be localhost (and 
> could probably be
> > turned into a unix domain socket quite easily).
> Sounds good. Let's do it.

Keep those patches coming! :-)


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_idh83&alloc_id149&op=click
Xen-devel mailing list