ia64/xen-unstable

changeset 2871:a881f5bde9d3

bitkeeper revision 1.1159.1.361 (4189cc99kcfAjah5PwXTNmK_0GONgA)

Tweak migration instructions + update ttylinux instructions (we now
mirror Tim's modified ttylinux on SF).
author mwilli2@equilibrium.research
date Thu Nov 04 06:30:49 2004 +0000 (2004-11-04)
parents 94ac39a10a8d
children 88412d1771bd
files docs/src/user.tex
line diff
     1.1 --- a/docs/src/user.tex	Thu Nov 04 03:05:32 2004 +0000
     1.2 +++ b/docs/src/user.tex	Thu Nov 04 06:30:49 2004 +0000
     1.3 @@ -602,7 +602,9 @@ full-featured distribution once they hav
     1.4  basics.
     1.5  
     1.6  \begin{enumerate}
     1.7 -\item Download the ttylinux disk image from XXX where from?
     1.8 +\item Download and extract the ttylinux disk image from the Files
     1.9 +section of the project's SourceForge site (see {\tt
    1.10 +http://sf.net/projects/xen/}).
    1.11  \item Create a configuration file like the following:
    1.12  \begin{verbatim}
    1.13  kernel = "/boot/vmlinuz-2.6.9-xenU"
    1.14 @@ -611,7 +613,7 @@ name = "ttylinux"
    1.15  cpu = -1 # leave to Xen to pick
    1.16  nics = 1
    1.17  ip = "1.2.3.4"
    1.18 -disk = ['file:/path/to/ttylinux-disk,sda1,w']
    1.19 +disk = ['file:/path/to/ttylinux/rootfs,sda1,w']
    1.20  root = "/dev/sda1 ro"
    1.21  \end{verbatim}
    1.22  \item Now start the domain and connect to its console:
    1.23 @@ -758,12 +760,17 @@ To perform a live migration, both hosts 
    1.24  the destination host must have sufficient resources (e.g. memory
    1.25  capacity) to accommodate the domain after the move.
    1.26  
    1.27 +Currently, there is no support for providing access to disk
    1.28 +filesystems when a domain is migrated.  Administrators should choose
    1.29 +an appropriate storage solution (i.e. SAN, NAS, etc.) to ensure that
    1.30 +domain filesystems are also available on their destination node.
    1.31 +
    1.32  A domain may be migrated using the {\tt xm migrate} command.  To
    1.33 -migrate the example ttylinux domain to another machine, we would use
    1.34 +live migrate a domain to another machine, we would use
    1.35  the command:
    1.36  
    1.37  \begin{verbatim}
    1.38 -# xm migrate --live ttylinux destination.ournetwork.com
    1.39 +# xm migrate --live mydomain destination.ournetwork.com
    1.40  \end{verbatim}
    1.41  
    1.42  There will be a delay whilst the domain is moved to the destination
    1.43 @@ -780,11 +787,6 @@ the new machine using the {\tt xm consol
    1.44  domain has any open network connections then they will be preserved,
    1.45  so SSH connections do not have this limitation.
    1.46  
    1.47 -Currently, there is no support for providing access to disk
    1.48 -filesystems when a domain is migrated.  Administrators should choose
    1.49 -an appropriate storage solution (i.e. SAN, NAS, etc.) to ensure that
    1.50 -domain filesystems are also available on their destination node.
    1.51 -
    1.52  \section{Managing domain memory (ballooning and memory limits)}
    1.53  
    1.54  XenLinux domains have the ability to relinquish / reclaim machine