ia64/xen-unstable

changeset 7798:4f247dc79d0a

Further changes to xm.1 man page.

Signed-off-by: Sean Dague <sean@dague.net>
author emellor@leeni.uk.xensource.com
date Sat Nov 12 18:52:16 2005 +0100 (2005-11-12)
parents 5ee1f7f3fc9b
children bffbe58801d0
files docs/man/xm.pod.1
line diff
     1.1 --- a/docs/man/xm.pod.1	Sat Nov 12 18:41:37 2005 +0100
     1.2 +++ b/docs/man/xm.pod.1	Sat Nov 12 18:52:16 2005 +0100
     1.3 @@ -36,6 +36,13 @@ Most B<xm> commands require root privled
     1.4  communications channels used to talk to the hypervisor.  Running as
     1.5  non root will return an error.
     1.6  
     1.7 +Most B<xm> commands act asynchronously, so just because the B<xm>
     1.8 +command returned, doesn't mean the action is complete.  This is
     1.9 +important, as many operations on domains, like create and shutdown,
    1.10 +can take considerable time (30 seconds or more) to bring the machine
    1.11 +into a fully compliant state.  If you want to know when one of these
    1.12 +actions has finished you must poll through xm list periodically.
    1.13 +
    1.14  =head1 DOMAIN SUBCOMMANDS
    1.15  
    1.16  The following sub commands manipulate domains directly, as stated
    1.17 @@ -86,19 +93,19 @@ B<EXAMPLES>
    1.18  
    1.19  =over 4
    1.20  
    1.21 -=item Config file in /etc/xen
    1.22 +=item I<with config file>
    1.23  
    1.24 -xm create Fedora4
    1.25 +  xm create Fedora4
    1.26  
    1.27  This creates a domain with the file /etc/xen/Fedora4, and returns as
    1.28  soon as it is run.
    1.29  
    1.30 -=item Creating a domain without ConfigFile
    1.31 -
    1.32 - xm create /dev/null ramdisk=initrd.img \
    1.33 -    kernel=/boot/vmlinuz-2.6.12.6-xenU \
    1.34 -    name=ramdisk nics=0 vcpus=1 \
    1.35 -    memory=64 root=/dev/ram0
    1.36 +=item I<without config file>
    1.37 + 
    1.38 +  xm create /dev/null ramdisk=initrd.img \
    1.39 +     kernel=/boot/vmlinuz-2.6.12.6-xenU \
    1.40 +     name=ramdisk nics=0 vcpus=1 \
    1.41 +     memory=64 root=/dev/ram0
    1.42  
    1.43  This creates the domain without using a config file (more specifically
    1.44  using /dev/null as an empty config file), kernel and ramdisk as
    1.45 @@ -131,7 +138,8 @@ grouped by function.
    1.46  
    1.47  =item I<list> [--long] [DomId, ...]
    1.48  
    1.49 -Prints information about running domains.
    1.50 +Prints information about one or more domains.  If no domains are
    1.51 +specified it prints out information about all domains.
    1.52  
    1.53  An example format for the list is as follows:
    1.54  
    1.55 @@ -148,44 +156,154 @@ size of the memory allocated to the doma
    1.56  VCPUS allocated to domain.  State is the run state (see below).  Time
    1.57  is the total run time of the domain as accounted for by Xen.
    1.58  
    1.59 +B<STATES>
    1.60 +
    1.61 +=over 4
    1.62 +
    1.63  The State field lists 6 states for a Xen Domain, and which ones the
    1.64  current Domain is in.
    1.65  
    1.66 +=item I<r - running>
    1.67 +
    1.68 +The domain is currently running on a CPU
    1.69 +
    1.70 +=item I<b - blocked>
    1.71 +
    1.72 +The domain is blocked, and not running or runable.  This can be caused
    1.73 +because the domain is waiting on IO (a traditional wait state) or has
    1.74 +gone to sleep because there was nothing else for it to do.
    1.75 +
    1.76 +=item I<p - paused>
    1.77 +
    1.78 +The domain has been paused, usually occurring through the administrator
    1.79 +running B<xm pause>.  When in a paused state the domain will still
    1.80 +consume allocated resources like memory, but will not be eligible for
    1.81 +scheduling by the Xen hypervisor.
    1.82 +
    1.83 +=item I<s - shutdown>
    1.84 +
    1.85 +FIXME: Why would you ever see this state?
    1.86 +
    1.87 +=item I<c - crashed>
    1.88 +
    1.89 +The domain has crashed, which is always a violent ending.  Usually
    1.90 +this state can only occur if the domain has been configured not to
    1.91 +restart on crash.  See L<xmdomain.cfg> for more info.
    1.92 +
    1.93 +=item I<d - dying>
    1.94 +
    1.95 +The domain is in process of dying, but hasn't completely shutdown or
    1.96 +crashed.
    1.97 +
    1.98 +FIXME: Is this right?
    1.99 +
   1.100 +=back
   1.101 +
   1.102 +B<LONG OUTPUT>
   1.103 +
   1.104 +=over 4
   1.105 +
   1.106 +If I<--long> is specified, the output for xm list is not the table
   1.107 +view shown above, but instead is an S-Expression representing all
   1.108 +information known about all domains asked for.  This is mostly only
   1.109 +useful for external programs to parse the data.
   1.110 +
   1.111 +B<Note:> there is no stable guarantees on the format of this data.
   1.112 +Use at your own risk.
   1.113 +
   1.114 +=back
   1.115 +
   1.116 +B<NOTES>
   1.117 +
   1.118 +=over 4
   1.119 +
   1.120 +The Time column is deceptive.  Virtual IO (network and block devices)
   1.121 +used by Domains requires coordination by Domain0, which means that
   1.122 +Domain0 is actually charged for much of the time that a DomainU is
   1.123 +doing IO.  Use of this time value to determine relative utilizations
   1.124 +by domains is thus very suspect, as a high IO workload may show as
   1.125 +less utilized than a high CPU workload.  Consider yourself warned.
   1.126 +
   1.127 +=back
   1.128 +
   1.129  =item I<mem-max> <DomId> <Mem>
   1.130  
   1.131 -Set domain maximum memory limit to Mem. Mem is in Megabytes. This is the upper memory mark for how much memory a domain can have.
   1.132 +Specify the maximum amount of memory the Domain is able to use.  Mem
   1.133 +is specified in megabytes. 
   1.134 +
   1.135 +The mem-max value may not correspond to the actual memory used in the
   1.136 +Domain, as it may balloon down it's memory to give more back to the OS.
   1.137  
   1.138  =item I<mem-set> <DomId> <Mem>
   1.139  
   1.140 -Set domain's memory, in Megabytes. Mem must be less than or equal to the maximum memory for the domain.
   1.141 +Set the domain's used memory using the balloon driver.  Because this
   1.142 +operation requires cooperation from the domain operating system, there
   1.143 +is no guarantee that it will succeed.
   1.144 +
   1.145 +B<Warning:> there is no good way to know in advance how small of a
   1.146 +mem-set will make a domain unstable and cause it to crash.  Be very
   1.147 +careful when using this command on running domains.
   1.148  
   1.149  =item I<migrate> <DomId> <Host> [Options]
   1.150  
   1.151 -Migrate a domain to another Host machine. B<Xend> must be running on other host machine and there must be sufficient resources as well.
   1.152 +Migrate a domain to another Host machine. B<Xend> must be running on
   1.153 +other host machine, it must be running the same version of xen, it
   1.154 +must have the migration tcp port open and accepting connections from
   1.155 +the source host, and there must be sufficient resources for the domain
   1.156 +to run (memory, disk, etc).
   1.157 +
   1.158 +Migration is pretty complicated, and has many security implications,
   1.159 +please read the Xen Users Guide to ensure you understand the
   1.160 +ramifications and limitations on migration before attempting it in
   1.161 +production.
   1.162 +
   1.163 +B<OPTIONS>
   1.164  
   1.165  =over 4
   1.166  
   1.167 -Additional Options:
   1.168 +=item I<-l, --live>
   1.169 +
   1.170 +Use live migration.  This will migrate the domain between hosts
   1.171 +without shutting down the domain.  See the Xen Users Guide for more
   1.172 +information.
   1.173  
   1.174 -    -l, --live                    Use live migration.
   1.175 -    -r, --resource <Mbit value>   Set resource level.
   1.176 +=item I<-r, --resource> Mbs
   1.177 +
   1.178 +Set maximum Mbs allowed for migrating the domain.  This ensures that
   1.179 +the network link is not saturated with migration traffic while
   1.180 +attempting to do other useful work.
   1.181  
   1.182  =back
   1.183  
   1.184  =item I<pause> <DomId>
   1.185  
   1.186 -Pause a domain's execution.
   1.187 +Pause a domain.  When in a paused state the domain will still consume
   1.188 +allocated resources like memory, but will not be eligible for
   1.189 +scheduling by the Xen hypervisor.
   1.190  
   1.191  =item I<reboot> [Options] <DomId>
   1.192  
   1.193 -Reboot a domain.
   1.194 +Reboot a domain.  This acts just as if the domain had the B<reboot>
   1.195 +command run from the console.  The command returns as soon as it has
   1.196 +executed the reboot action, which may be significantly before the
   1.197 +domain actually reboots.
   1.198 +
   1.199 +The behavior of what happens to a domain when it reboots is set by the
   1.200 +B<on_reboot> parameter of the xmdomain.cfg file when the domain was
   1.201 +created.
   1.202 +
   1.203 +B<OPTIONS>
   1.204  
   1.205  =over 4
   1.206  
   1.207 -Additional Options:
   1.208 +=item I<-a, --all>
   1.209 +
   1.210 +Reboot all domains
   1.211  
   1.212 -    -a, --all        reboot all domains.
   1.213 -    -w, --wait       Wait for shutdown to complete.
   1.214 +=item I<-w, --wait>
   1.215 +
   1.216 +Wait for reboot to complete before returning.  This may take a while,
   1.217 +as all services in the domain will have to be shut down cleanly.
   1.218  
   1.219  =back
   1.220