ia64/xen-unstable

changeset 1206:b70caff62b81

bitkeeper revision 1.817 (405ef60cUJ4B9bY3LZWu-yP8DBid2w)

Console-HOWTO.txt:
new file
author kaf24@scramble.cl.cam.ac.uk
date Mon Mar 22 14:19:56 2004 +0000 (2004-03-22)
parents 38b05d6c12f5
children 44bf85de60ec
files .rootkeys docs/Console-HOWTO.txt
line diff
     1.1 --- a/.rootkeys	Mon Mar 22 13:45:33 2004 +0000
     1.2 +++ b/.rootkeys	Mon Mar 22 14:19:56 2004 +0000
     1.3 @@ -6,6 +6,7 @@ 3eb788d6Kleck_Cut0ouGneviGzliQ Makefile
     1.4  3f5ef5a24IaQasQE2tyMxrfxskMmvw README
     1.5  3f5ef5a2l4kfBYSQTUaOyyD76WROZQ README.CD
     1.6  3f69d8abYB1vMyD_QVDvzxy5Zscf1A TODO
     1.7 +405ef604hIZH5pGi2uwlrlSvUMrutw docs/Console-HOWTO.txt
     1.8  3f9e7d53iC47UnlfORp9iC1vai6kWw docs/Makefile
     1.9  40083bb4LVQzRqA3ABz0__pPhGNwtA docs/VBD-HOWTO.txt
    1.10  4021053fmeFrEyPHcT8JFiDpLNgtHQ docs/Xeno-HOWTO.txt
     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/docs/Console-HOWTO.txt	Mon Mar 22 14:19:56 2004 +0000
     2.3 @@ -0,0 +1,71 @@
     2.4 +    New console I/O infrastructure in Xen 1.3
     2.5 +    =========================================
     2.6 +
     2.7 +    Keir Fraser, University of Cambridge, 22nd March 2004
     2.8 +
     2.9 + I thought I'd write a quick note about using the new console I/O
    2.10 + infrastructure in Xen 1.3. Significant new features compared with 1.2,
    2.11 + and with older revisions of 1.3, include:
    2.12 +  - bi-directional console access
    2.13 +  - log in to a Xenolinux guest OS via its virtual console
    2.14 +  - a new terminal client (replaces the use of telnet in character mode)
    2.15 +  - proper handling of terminal emulation
    2.16 +
    2.17 +Domain 0 virtual console
    2.18 +------------------------
    2.19 + The virtual console for domain 0 is shared with Xen's console. For
    2.20 + example, if you specify 'console=com1' as a boot parameter to Xen,
    2.21 + then domain 0 will have bi-directional access to the primary serial
    2.22 + line. Boot-time messages can be directed to the virtual console by
    2.23 + specifying 'console=xencons0' as a boot parameter to Xenolinux.
    2.24 +
    2.25 +Connecting to the virtual console
    2.26 +---------------------------------
    2.27 + Domain 0 console may be accessed using the supplied 'miniterm' program
    2.28 + if raw serial access is desired. If the Xen machine is connected to a
    2.29 + serial-port server, then the supplied 'xencons' program may be used to
    2.30 + connect to the appropriate TCP port on the server:
    2.31 +  # xencons <server host> <server port>
    2.32 +
    2.33 +Logging in via virtual console
    2.34 +------------------------------
    2.35 + It is possible to log in to a guest OS via its virtual console if a
    2.36 + 'getty' is running. To achieve this, a suitable device node must be
    2.37 + created, and a new line added to inittab:
    2.38 +  # mkdir -p /dev/xen
    2.39 +  # mknod /dev/xen/cons c 4 123
    2.40 +  # echo "c:2345:respawn:/sbin/mingetty --noclear xen/cons" >>/etc/inittab
    2.41 +
    2.42 + [NOTE to users in the lab -- existing Xen installations may be running
    2.43 + mingetty on /dev/console. This is incorrect behaviour! Please modify
    2.44 + such setups to run mingetty on /dev/xen/cons.]
    2.45 +
    2.46 + Additionally, if you wish to allow root logins via the virtual
    2.47 + console, then 'xen/cons' must be added to the trusted tty list in
    2.48 + /etc/securettys.
    2.49 +
    2.50 +Virtual console for other domains
    2.51 +---------------------------------
    2.52 + Every guest OS has a virtual console that is accessible via
    2.53 + 'console=xencons0' at boot time, or mingetty running on
    2.54 + /dev/xen/cons. However, domains other than domain 0 do not have access
    2.55 + to the physical serial line. Instead, their console data is sent to
    2.56 + and from a control daemon running in domain 0. When properly
    2.57 + installed, this daemon can be started from the init scripts (e.g.,
    2.58 + rc.local):
    2.59 +  # /usr/sbin/xend start
    2.60 +
    2.61 + Note that, when a domain is created using xc_dom_create.py, xend MUST
    2.62 + be running. If everything is set up correctly then xc_dom_create will
    2.63 + print the local TCP port to which you should connect to perform
    2.64 + console I/O. A suitable console client is provided by the Python
    2.65 + module xenctl.console_client: running this module from the command
    2.66 + line with <host> and <port> parameters will start a terminal
    2.67 + session. This module is also installed as /usr/bin/xencons, from a
    2.68 + copy in tools/misc/xencons. For example:
    2.69 +  # xencons localhost 9600
    2.70 +
    2.71 + An alternative to manually running a terminal client is to specify
    2.72 + '-c' to xc_dom_create.py, or add 'auto_console=True' to the defaults
    2.73 + file. This will cause xc_dom_create.py to automatically become the
    2.74 + console terminal after starting the domain.