WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [RFC] [PATCH] Plumb bootloader I/O through xenconsole.

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [RFC] [PATCH] Plumb bootloader I/O through xenconsole.
From: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
Date: Mon, 15 Jan 2007 16:20:14 +0000
Delivery-date: Mon, 15 Jan 2007 08:19:47 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
User-agent: Mutt/1.5.13 (2006-08-11)
The attached patches change the way the bootloader is called when
creating a PV domain.  Currently, in order to provide an interactive
environment for the bootloader, the bootloader is run by xm create,
using the tty of xm create's caller.  This is a problem when a domain is
rebooted, as there is no equivalent of xm create with a useful tty.

With these patches, Xend always calls the bootloader, and its
interactive I/O is passed through the same pty channel that the domain's
console will use when it is created.

All comments appreciated!

Details:

Patch 1 (ptsname) is a wrapper around the ptsname(3) POSIX library
function, which doesn't appear to be available in python otherwise.

Patch 2 (bootloader-console) makes the following changes:
  - the xenconsole client can handle the domain's console pty changing.
  - xend forwards console traffic between the running bootloader and a pty
    which it writes to the store so the xenconsole client can see it.
  - xend runs the bootloader interactively unless the config file 
    tells it explicitly not to.
  - xm create no longer runs the bootloader.

Yet to come: making "xm console" and "xm create -c" attach early enough
in domain building to see the bootloader (at the moment you need to run
xenconsole by hand for that).

Cheers,

Tim.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel