ia64/xen-unstable

changeset 928:8dd462437867

bitkeeper revision 1.590 (3fb015den6iTCedknkVEV3Wfg-Ql1Q)

Now contains a fairly complete list of instructions from downloading source codes, compilation to configure, start and stop domains.
author br260@laudney.cl.cam.ac.uk
date Mon Nov 10 22:49:02 2003 +0000 (2003-11-10)
parents 95c8edd31ea0
children 5e91938ceb1b
files docs/Xeno-HOWTO
line diff
     1.1 --- a/docs/Xeno-HOWTO	Mon Nov 10 18:12:44 2003 +0000
     1.2 +++ b/docs/Xeno-HOWTO	Mon Nov 10 22:49:02 2003 +0000
     1.3 @@ -108,19 +108,14 @@ all the tools.
     1.4  
     1.5  Particularly, in order to compile tools under 'control', you
     1.6  must have Apache Ant installed. Latest binary can be found at
     1.7 -'http://ant.apache.org/bindownload.cgi'. Besides, the Java
     1.8 -codes under 'control' are quite broken. You may encounter
     1.9 -compilation errors. For now, it's wise to skip 'control'.
    1.10 +'http://ant.apache.org/bindownload.cgi'.
    1.11 +
    1.12 +Besides, you must have Java J2SDK 1.4 installed. There seemed
    1.13 +to be compilation errors with J2SDK 1.3, but fine with J2SDK 1.4
    1.14  
    1.15  To summarize:
    1.16  
    1.17 -# cd /xeno-1.1.bk/tools/balloon
    1.18 -# make
    1.19 -# make install
    1.20 -# cd /xeno-1.1.bk/tools/internal
    1.21 -# make
    1.22 -# make install
    1.23 -# cd /xeno-1.1.bk/tools/misc
    1.24 +# cd /xeno-1.1.bk/tools
    1.25  # make
    1.26  # make install
    1.27  # cd /install/bin
    1.28 @@ -186,20 +181,109 @@ The following is a list of command line 
    1.29   dom0_mem=xxx     Set the maximum amount of memory for domain0.
    1.30  
    1.31  
    1.32 +Xenctl Configuration
    1.33 +==============================
    1.34 +
    1.35 +# cd /xeno-1.1.bk/tools/control/examples
    1.36 +# cp xenctl.xml xen-mynewdom /etc
    1.37 +
    1.38 +Then, you need to modify /etc/xen-mynewdom:
    1.39 +
    1.40 +# cat /etc/xen-mynewdom
    1.41 +domain new
    1.42 +physical grant -pcdrom_link
    1.43 +domain start
    1.44 +
    1.45 +You should substitue 'cdrom_link' with the
    1.46 +root partition, e.g. '/dev/hda3', '/dev/sda1'.
    1.47 +Therefore, the second looks like:
    1.48 +'physical grant -p/dev/hda3'
    1.49 +
    1.50 +Then, you need to modify /etc/xenctl.xml:
    1.51 +
    1.52 +# cat /etc/xenctl.xml
    1.53 +<?xml version="1.0"?>
    1.54 +<domctl_defaults>
    1.55 +<domain_name>XenoLinux</domain_name>
    1.56 +<domain_size_kb>98304</domain_size_kb>
    1.57 +<domain_image>/boot/xenolinux.gz</domain_image>
    1.58 +<domain_vifs>1</domain_vifs>
    1.59 +<domain_init_rd>/boot/initrd.gz</domain_init_rd>
    1.60 +<root_device>/dev/ram0</root_device>
    1.61 +<root_args>rw</root_args>
    1.62 +<args>init=/linuxrc 4 DOMID=+</args>
    1.63 +<nw_ip>169.254.1.0+</nw_ip>
    1.64 +<nw_gw>169.254.1.0</nw_gw>
    1.65 +<nw_mask>255.255.0.0</nw_mask>
    1.66 +<nw_nfs_server>169.254.1.0</nw_nfs_server>
    1.67 +<max_domain_number>1000</max_domain_number>
    1.68 +<xi_tools_dir>/usr/local/bin/</xi_tools_dir>
    1.69 +</domctl_defaults>
    1.70 +
    1.71 +The meaning of every line is very straightforward
    1.72 +and should be modified according to your configuration.
    1.73 +
    1.74 +Normally you don't need <domain_init_rd>. And you probably want
    1.75 +root_args set to "ro", otherwise fsck will complain. Assuming you've
    1.76 +installed a standard linux installation, you probably don't want to
    1.77 +explicit set the init program, or the run level,
    1.78 +e.g. <args>DOMID=+</args>
    1.79 +
    1.80 +
    1.81  Boot into Domain 0
    1.82  ==============================
    1.83  
    1.84 -Reboot your computer; After selecting the kernel to boot, stand back and watch Xen boot, closely followed by "domain 0" running the XenoLinux kernel.  Depending on which root partition you have assigned to XenoLinux kernel in Grub configuration file, you can use the corresponding username / password
    1.85 -to log in.
    1.86 +Reboot your computer; After selecting the kernel to boot, stand back
    1.87 +and watch Xen boot, closely followed by "domain 0" running the
    1.88 +XenoLinux kernel.  Depending on which root partition you have assigned
    1.89 +to XenoLinux kernel in Grub configuration file, you can use the
    1.90 +corresponding username / password to log in.
    1.91  
    1.92  Once logged in, it should look just like any regular linux box. All
    1.93  the usual tools and commands should work as per usual.
    1.94  
    1.95  
    1.96 -Using the domain control tools
    1.97 +Start New Domains
    1.98  ==============================
    1.99  
   1.100 -The README.CD file contains some examples of how to use 'xenctl' and
   1.101 -the other domain control tools. Invoking the tool without any
   1.102 -arguments prints some usage inforamtion. There's also some
   1.103 -documentation in the the repository under tools/control/doc
   1.104 +You must be 'root' to start new domains.
   1.105 +
   1.106 +Make sure you have successfully configured at least one
   1.107 +physical network interface. Then:
   1.108 +
   1.109 +# xen_nat_enable
   1.110 +# xen_read_console &
   1.111 +
   1.112 +When new  domains are created and  started, they will  send output via
   1.113 +UDP packets to  the local virtual network. Those  packets are received
   1.114 +by xen_read_console running in Domain  0 and output are printed out to
   1.115 +the standard output.
   1.116 +
   1.117 +# xenctl script -f/etc/xen-mynewdom
   1.118 +
   1.119 +This will create and start a new domain based on /etc/xen-mynewdom and
   1.120 +/etc/xenctl.xml
   1.121 +
   1.122 +You should be able to see XenoLinux boot message on standard output
   1.123 +with each line prepended [domain_id].
   1.124 +
   1.125 +
   1.126 +List and Stop Domains
   1.127 +==============================
   1.128 +
   1.129 +You can see a list of existing domains with:
   1.130 +
   1.131 +# xi_list
   1.132 +or
   1.133 +# xenctl domain list
   1.134 +
   1.135 +In order to stop a domain, you use:
   1.136 +
   1.137 +# xi_stop domain_id
   1.138 +or
   1.139 +# xenctl domain stop -ndomain_id
   1.140 +
   1.141 +followed by
   1.142 +# xi_destroy domain_id
   1.143 +or
   1.144 +# xenctl domain destroy -ndomain_id
   1.145 \ No newline at end of file