Incorporating Alan's mods.

4 files changed, 373 insertions, 214 deletions

diff --git a/docs/src/user/debian.tex b/docs/src/user/debian.tex
index ba5667c50b..94f3773abd 100644
--- a/docs/src/user/debian.tex
+++ b/docs/src/user/debian.tex
@@ -1,158 +1,173 @@
-\chapter{Installing Xen on Debian}
+\chapter{Installing Xen/XenLinux on Debian}
 
-The Debian project provides a tool called \path{debootstrap} which
-allows a base Debian system to be installed into a filesystem without
-requiring the host system to have any Debian-specific software (such as
-\path{apt}).
+This appendix describes installing Xen 3.0 on Debian Linux.
 
-Here's some info on how to install Debian 3.1 (Sarge) for an
-unprivileged Xen domain:
+Xen can be installed on Debian GNU/Linux using the following methods:
 
-\section{Filesystem Setup}
-\begin{enumerate}
-\item Set up Xen and test that it's working, as described earlier in
-  this manual.
+\begin{itemize}
+\item From a binary tarball
+\item From source 
+\item From debs
+\end{itemize}
 
-\item Create disk images for rootfs and swap. Alternatively, you might
-  create dedicated partitions, LVM logical volumes, etc.\ if that suits
-  your setup.
-\begin{verbatim}
-dd if=/dev/zero of=/path/diskimage bs=1024k count=size_in_mbytes
-dd if=/dev/zero of=/path/swapimage bs=1024k count=size_in_mbytes
-\end{verbatim}
-  If you're going to use this filesystem / disk image only as a
-  `template' for other vm disk images, something like 300 MB should be
-  enough. (of course it depends what kind of packages you are planning
-  to install to the template)
+\section{Installing from a binary tarball}
+This section describes the process of installing Xen on Debian Sarge using the stable binary release tarball.
 
-\item Create the filesystem and initialise the swap image
-\begin{verbatim}
-mkfs.ext3 /path/diskimage
-mkswap /path/swapimage
-\end{verbatim}
+\subsection{Required Packages}
+Install these Debian packages:
 
-\item Mount the disk image for installation
-\begin{verbatim}
-mount -o loop /path/diskimage /mnt/disk
-\end{verbatim}
-\end{enumerate}
-\section{Bootstrapping}
-\begin{enumerate}
-\item Install \path{debootstrap}. Make sure you have debootstrap
-  installed on the host. If you are running Debian Sarge (3.1 / testing)
-  or unstable you can install it by running \path{apt-get install
-    debootstrap}. Otherwise, it can be downloaded from the Debian
-  project website.
-
-\item Install Debian base to the disk image:
-\begin{verbatim}
-debootstrap --arch i386 sarge /mnt/disk  \
-            http://ftp.<countrycode>.debian.org/debian
-\end{verbatim}
-  You may use any Debian mirror that you want.
-\end{enumerate}
+\begin{itemize}
+\item bridge-utils
+\item libcurl3-dev
+\item iproute
+\item zlib1g-dev
+\item python-dev
+\end{itemize}
 
-\section{Configuration}
-\begin{enumerate}
-\item When debootstrap completes successfully, modify settings:
 \begin{verbatim}
-chroot /mnt/disk /bin/bash
+apt-get install bridge-utils   libcurl3-dev iproute  zlib1g-dev python-dev
 \end{verbatim}
 
-  Edit the following files using vi or nano and make any required
-  changes:
-\begin{verbatim}
-/etc/hostname
-/etc/hosts
-/etc/resolv.conf
-/etc/network/interfaces
-/etc/networks
-\end{verbatim}
 
-  Set up access to the services. Edit:
-\begin{verbatim}
-/etc/hosts.deny
-/etc/hosts.allow
-/etc/inetd.conf
-\end{verbatim}
+\subsection{Download the binary tarball}
+Download the Xen 3.0 binary tarball from the XenSource downloads
+page:
 
-  Add Debian mirror to:
+\begin{quote} {\tt http://www.xensource.com/downloads/}
+\end{quote}
+ 
+\subsection{Extract and Install}
 \begin{verbatim}
-/etc/apt/sources.list
+#  tar zxvf 
+xen-2.0.7-install-x86_32.tgz
+# cd xen-2.0.7-install-x86_32.tgz
+# ./install.sh
 \end{verbatim}
 
-  Create fstab like this:
-\begin{verbatim}
-/dev/sda1       /       ext3    errors=remount-ro       0       1
-/dev/sda2       none    swap    sw                      0       0
-proc            /proc   proc    defaults                0       0
-\end{verbatim}
+If everything goes well, you should something like
 
-  Logout
-
-\item Unmount the disk image
 \begin{verbatim}
-umount /mnt/disk
+Installing Xen from 
+'./install' to '/'...
+    All done.
+    Checking to see whether prerequisite tools are installed...
+    All done.
 \end{verbatim}
 
-\item Create Xen 3.0 configuration file for the new domain. You may use
-  the example-configurations provided with Xen as a template.
 
-  Make sure you have the correctly configured:
-\begin{verbatim}
-disk = [ 'file:/path/diskimage,sda1,w', 'file:/path/swapimage,sda2,w' ]
-root = "/dev/sda1 ro"
-\end{verbatim}
-\end{enumerate}
+\subsection{Configure grub}
+Make an entry in your grub configuration like below.
 
-\section{Starting the New Domain}
-\begin{enumerate}
-\item Start the new domain
+{\small
 \begin{verbatim}
-xm create -f domain_config_file
+title          Xen on Debian
+kernel         (hd0,5)/boot/xen.gz dom0_mem=131000
+module         (hd0,5)/boot/vmlinuz-2.6-xen0 root=/dex/hda6 ro console=tty0
 \end{verbatim}
+}
+
+You can now boot into Xen by by choosing the right option from grub menu.
+
+\section{Installing from source}
+\subsection{Required Packages}
+Besides packages mentioned under binary tarball install, you will need:
+
+\begin{itemize}
+\item gcc v3.2.x or v3.3.x
+\item binutils
+\item GNU make
+\end{itemize}
+
+
+\subsection{Download the source tree}
+The Xen source tree is available as either a compressed source tarball
+or as a clone of our master Mercurial repository.
+
+\begin{description}
+\item[Obtaining the Source Tarball]\mbox{} \\
+  Stable versions and daily snapshots of the Xen source tree are
+  available from the Xen download page:
+  \begin{quote} {\tt http://www.xensource.com/downloads/}
+  \end{quote}
+\item[Obtaining the source via Mercurial]\mbox{} \\
+  The source tree may also be obtained via the public Mercurial
+  repository hosted at:
+  \begin{quote}{\tt http://xenbits.xensource.com}.
+  \end{quote} See the instructions and the Getting Started Guide
+  referenced at:
+  \begin{quote}
+    {\tt http://www.xensource.com/downloads/}.
+  \end{quote}
+\end{description}
+
+\subsection{Extract, build and install}
 
-  Check that the new domain is running:
 \begin{verbatim}
-xm list
+# tar zxvf xen-3.0.0-src.tgz
+# cd xen-3.0
+# make dist
+#./install.sh
 \end{verbatim}
 
-\item Attach to the console of the new domain. You should see something
-  like this when starting the new domain:
+\section{Installing from debs}
+This section describes the process of installing Xen on Debian Sarge using debs created by Edward Despard.
 
-\begin{verbatim}
-Started domain testdomain2, console on port 9626
-\end{verbatim}
-        
-  You can see the ID of the console: 26. You can also list the consoles
-  with \path{xm consoles}. ID is the last two digits of the port number.
+\subsection{Edward's announcement to xen-user list}
+"For part of my Google Summer of Code work I've put together debs for xen of 2.0.7 and of unstable. The unstable debs are built off of yesterday's hg tree, but I try to update them fairly regularly when new developments occur." 
 
-  Attach to the console:
+\subsection{Adding apt source}
+Add the following lines to \path{/etc/apt/sources.list}:
 
+\begin{quote}
+{\small
 \begin{verbatim}
-xm console 26
+deb http://tinyurl.com/8tpup
 \end{verbatim}
+}
+\end{quote}
+   
+Note: On Ubuntu, simple replace debian with ubuntu in the above. Replace xen-unstable with with xen-stable for a stable version.
+
+Now run \path{aptitude update} or \path{apt-get update}. Doing \path{apt-cache search xen}, you should see following packages in the output.
+
+\begin{itemize}
+\item kernel-image-2.6.12-xen0 - Xen 2.6 kernel image
+\item kernel-image-2.6.12-xenu - Xen 2.6 kernel image
+\item kernel-patch-xen-2.6.12 - patch to kernel to support xen
+\item libxen3.0 - control libraries for Xen
+\item libxen-dev - development libraries for Xen
+\item xen-doc - documentation for Xen
+\item xen-hypervisor - Xen hypervisor kernel
+\item xen-kernels - Xen kernels
+\item xen - Package to install all of Xen
+\item xen-tools - Tools for managing xen domains
+\end{itemize}
+
+\subsection{Installing Xen}
+You can now install xen using \path{apt-get}, \path{aptitude}, \path{synaptic}, etc. 
+ 
+After doing \path{apt-get install xen}, you will have a working dom0 and should be able boot into it without any problem. By doing \path{apt-cache depends xen}, you will find that the following packages were also installed as a result of dependency.
 
-  or by telnetting to the port 9626 of localhost. The xm console program
-  works better.
-
-\item Log in and run base-config
-
-  By default there is no password set for root.
-
-  Check that everything looks OK, and the system started without errors.
-  Check that the swap is active, and the network settings are correct.
-
-  Run \path{/usr/sbin/base-config} to configure the Debian settings.
+\begin{verbatim}
+#  apt-cache  
+depends  xen
+       xen
+           Depends: xen-doc
+           Depends: xen-kernels
+           Depends: xen-hypervisor
+           Depends: xen-tools
+\end{verbatim}
 
-  Set the password for root using \path{passwd}.
 
-\item Done. You may exit the console by pressing {\path{Ctrl + ]}}
+\subsection{xenkernels.conf}
+To automate grub entry for xen, \path{/etc/xenkernels.conf} is used which is installed when the package in installed. Below is a sample entry
 
-\end{enumerate}
+\begin{verbatim}
+label=Xen(3.0-unstable082205)/Linux(2.6.12)--
+          xen=/boot/xen-3.0-unstable082205.gz
+          kernel=/boot/xen/dom0/vmlinuz-2.6.12-xen0
+          mem=256000
+          root=/dev/hda4
+\end{verbatim}
 
-If you need to create new domains, you can copy the contents of the
-`template'-image to the new disk images, either by mounting the template
-and the new image, and using \path{cp -a} or \path{tar} or by simply
-copying the image file. Once this is done, modify the image-specific
-settings (hostname, network settings, etc).
+You have to run run \path{update-grub-xen} every time \path{xenkernels.conf} is modified. Read \path{man update-grub-xen} for more information.
diff --git a/docs/src/user/fedora.tex b/docs/src/user/fedora.tex
index 5ea79d05d4..c5cbdf2ff4 100644
--- a/docs/src/user/fedora.tex
+++ b/docs/src/user/fedora.tex
@@ -1,66 +1,102 @@
-\chapter{Installing Xen on Red~Hat or Fedora~Core}
-
-\section{Tips}
-Here are a few pointers about using Xen / XenLinux on a Red~Hat or
-Fedora~Core distribution:
-
-\begin{enumerate}
-\item Note that, because domains greater than~0 don't have any
-  privileged access at all, certain commands in the default boot
-  sequence will fail e.g.\ attempts to update the hwclock, change the
-  console font, update the keytable map, start apmd (power management),
-  or gpm (mouse cursor). Either ignore the errors (they should be
-  harmless), or remove them from the startup scripts. Deleting the
-  following links are a good start: {\path{S24pcmcia}},
-  {\path{S09isdn}}, {\path{S17keytable}}, {\path{S26apmd}},
-  {\path{S85gpm}}.
-
-\item If you want to use a single root file system that works cleanly
-  for both domain~0 and unprivileged domains, a useful trick is to use
-  different `init' run levels. For example, use run level 3 for
-  domain~0, and run level 4 for other domains. This enables different
-  startup scripts to be run in depending on the run level number passed
-  on the kernel command line.
-
-\item If using NFS root files systems mounted either from an external
-  server or from domain0 there are a couple of other gotchas. The
-  default {\path{/etc/sysconfig/iptables}} rules block NFS, so part way
-  through the boot sequence things will suddenly go dead.
-
-\item If you're planning on having a separate NFS {\path{/usr}}
-  partition, the RH9 boot scripts don't make life easy - they attempt to
-  mount NFS file systems way to late in the boot process. The easiest
-  way I found to do this was to have a {\path{/linuxrc}} script run
-  ahead of {\path{/sbin/init}} that mounts {\path{/usr}}:
-
-  \begin{quote}
-    \begin{small}\begin{verbatim}
- #!/bin/bash
- /sbin/ipconfig lo 127.0.0.1
- /sbin/portmap
- /bin/mount /usr
- exec /sbin/init "$@" <>/dev/console 2>&1
-\end{verbatim}\end{small}
-  \end{quote}
-
-%% $ XXX SMH: font lock fix :-)
-
-  The one slight complication with the above is that
-  {\path{/sbin/portmap}} is dynamically linked against
-  {\path{/usr/lib/libwrap.so.0}} Since this is in {\path{/usr}}, it
-  won't work. This can be solved by copying the file (and link) below
-  the {\path{/usr}} mount point, and just let the file be `covered' when
-  the mount happens.
-
-\item In some installations, where a shared read-only {\path{/usr}} is
-  being used, it may be desirable to move other large directories over
-  into the read-only {\path{/usr}}. For example, you might replace
-  {\path{/bin}}, {\path{/lib}} and {\path{/sbin}} with links into
-  {\path{/usr/root/bin}}, {\path{/usr/root/lib}} and
-  {\path{/usr/root/sbin}} respectively. This creates other problems for
-  running the {\path{/linuxrc}} script, requiring bash, portmap, mount,
-  ifconfig, and a handful of other shared libraries to be copied below
-  the mount point --- a simple statically-linked C program would solve
-  this problem.
-
-\end{enumerate}
\ No newline at end of file
+\chapter{Installing Xen on Fedora~Core 4}
+
+This section will help you in installing Xen 3 on Fedora Core 4 using various methods.
+
+\section{Installing Xen from Source Package and binary package}
+
+\subsection{Required Packages}
+bridge\_utils
+
+
+\subsection{Installing}
+
+Download the source or binary tarballs available at \begin{quote} {\tt http://www.xensource.com/downloads } \end{quote}.
+
+Extract the archive using following command:
+
+\begin{verbatim}
+tar -zxvf xen-*****-***.tgz
+\end{verbatim}
+
+cd into the xen directory.
+
+To compile and install the source do
+
+\begin{verbatim}
+     make dist
+     make install
+\end{verbatim}
+
+
+To install the binary tarball, all you need to do is run the \path{install.sh} script.
+
+\begin{verbatim}
+     #./install.sh
+\end{verbatim}
+
+\subsection{Installing Xen using yum}
+
+To install xen, type the command
+
+\begin{verbatim}
+#yum install xen
+\end{verbatim}
+
+This will download the following rpms and install them:
+
+\begin{itemize}
+\item xen
+\item bridge-utils
+\item sysfsutils
+\end{itemize}
+
+Next we need to install kernel-xen0 and kernel-xenU. Type the command:
+
+\begin{verbatim}
+ yum install kernel-xen0 kernel-xenU 
+\end{verbatim}
+
+Note: This installs xen0 and xenU kernels and adds an entry in the grub configuration.
+Getting Xen up and running
+
+Once this finishes, you have xen0 and xenU kernels installed in the /boot filesystem. To boot into Dom0, edit the grub configuration file, which is menu.lst
+
+Note: Installation using yum doesn't require the configuration of grub as mentioned below.
+
+An example grub entry would be like:
+
+{\small
+\begin{verbatim}
+title Xen Unstable(From Fedora Core 4)
+          root (hd0,0)
+          kernel /fedora/xen.gz dom0\_mem=230000 console=vga
+          module /fedora/vmlinuz-2.6-xen0 root=/dev/Vol1/LV3 ro console=tty0
+          module /fedora/initrd-2.6.11-1.1369\_FC4smp.img
+\end{verbatim}
+}
+
+Also make sure that \path{/var/run/xenstored} and \path{/var/lib/xenstored} directories have been created. If they are not, manually create them.
+
+Now reboot and select the xen0 option from the GRUB menu.
+
+To check whether you are running the xen0 kernel, type \path{uname -r}
+
+Now start the xend process:
+
+\begin{verbatim}
+xend start
+\end{verbatim}
+
+To check whether xend process is running or not, type the following command which lists the running domains.
+
+\begin{verbatim}
+#xm list
+      Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
+      Domain-0           0      219    0      1   r-----     28.9
+\end{verbatim}
+
+Since you haven't created any guest domains yet, you would see only Domain0.
+
+Further Help and documentations
+
+Besides the usual resources, see the Fedora Quickstart Guide \begin{quote} {\tt http://www.fedoraproject.org/wiki/FedoraXenQuickstart } \end{quote}
diff --git a/docs/src/user/installation.tex b/docs/src/user/installation.tex
index a9f567d5fe..fd9b34b1c0 100644
--- a/docs/src/user/installation.tex
+++ b/docs/src/user/installation.tex
@@ -35,9 +35,10 @@ if you wish to build from source.
 Once you have satisfied these prerequisites, you can now install either
 a binary or source distribution of Xen.
 
+
 \section{Installing from Binary Tarball}
 
-Pre-built tarballs are available for download from the XenSource downloads
+Pre-built tarballs are available for download from the Xen download
 page:
 \begin{quote} {\tt http://www.xensource.com/downloads/}
 \end{quote}
@@ -52,22 +53,7 @@ Once you've downloaded the tarball, simply unpack and install:
 Once you've installed the binaries you need to configure your system as
 described in Section~\ref{s:configure}.
 
-\section{Installing from RPMs}
-Pre-built RPMs are available for download from the XenSource downloads
-page:
-\begin{quote} {\tt http://www.xensource.com/downloads/}
-\end{quote}
 
-Once you've downloaded the RPMs, you typically install them via the RPM commands:
-\begin{verbatim}
-# rpm -ivh \emph{rpmname}
-\end{verbatim}
-
-See the instructions and the Release Notes for each RPM set referenced at:
-  \begin{quote}
-    {\tt http://www.xensource.com/downloads/}.
-  \end{quote}
- 
 \section{Installing from Source}
 
 This section describes how to obtain, build and install Xen from source.
@@ -102,9 +88,9 @@ or as a clone of our master Mercurial repository.
 % \item[\path{tools/}] Xen node controller daemon (Xend), command line
 %   tools, control libraries
 % \item[\path{xen/}] The Xen VMM.
-% \item[\path{buildconfigs/}] Build configuration files
 % \item[\path{linux-*-xen-sparse/}] Xen support for Linux.
-% \item[\path{patches/}] Experimental patches for Linux.
+% \item[\path{linux-*-patches/}] Experimental patches for Linux.
+% \item[\path{netbsd-*-xen-sparse/}] Xen support for NetBSD.
 % \item[\path{docs/}] Various documentation files for users and
 %   developers.
 % \item[\path{extras/}] Bonus extras.
@@ -235,7 +221,7 @@ destinations.
 
 %% Files in \path{install/boot/} include:
 %% \begin{itemize}
-%% \item \path{install/boot/xen-3.0.gz} Link to the Xen 3.0 'kernel'
+%% \item \path{install/boot/xen-2.0.gz} Link to the Xen 'kernel'
 %% \item \path{install/boot/vmlinuz-2.6-xen0} Link to domain 0
 %%   XenLinux kernel
 %% \item \path{install/boot/vmlinuz-2.6-xenU} Link to unprivileged
@@ -301,11 +287,9 @@ When installing a new kernel, it is recommended that you do not delete
 existing menu options from \path{menu.lst}, as you may wish to boot your
 old Linux kernel in future, particularly if you have problems.
 
-%% KMS: Additional configurations as an Appendix?
-
 \subsection{Serial Console (optional)}
 
-%% kernel /boot/xen-3.0.gz dom0_mem=131072 com1=115200,8n1
+%% kernel /boot/xen-2.0.gz dom0_mem=131072 com1=115200,8n1
 %% module /boot/vmlinuz-2.6-xen0 root=/dev/sda4 ro
 
 In order to configure Xen serial console output, it is necessary to add
@@ -327,9 +311,9 @@ necessary to add a line into \path{/etc/inittab}. Add the line:
 \begin{quote} {\small {\tt c:2345:respawn:/sbin/mingetty ttyS0}}
 \end{quote}
 
-run \path{init q} to force init to re-examine \path{/etc/inittab}, and
-you should be able to log in.  Add \path{ttyS0} to \path{/etc/securetty}
-to allow root logins over serial console, if it is not already there.
+and you should be able to log in. To successfully log in as root over
+the serial line will require adding \path{ttyS0} to
+\path{/etc/securetty} if it is not already there.
 
 \subsection{TLS Libraries}
 
diff --git a/docs/src/user/rhel.tex b/docs/src/user/rhel.tex
index bc40a24650..10a90233d2 100644
--- a/docs/src/user/rhel.tex
+++ b/docs/src/user/rhel.tex
@@ -1,3 +1,127 @@
-\chapter{Installing Xen on Red Hat Enterprise Linux (RHEL)}
+\chapter{Installing Xen on Red Hat Enterprise Linux (RHEL) 4.1}
 
-Placeholder.
+RedHat Enterprise Linux is the enterprise-grade, certified version of the Red Hat distribution. This section includes resolving dependencies using yum, installing Xen, and creating an initrd for Xen.
+
+Stable binary release install
+Source install
+\section{Stable binary release install}
+
+\subsection{Setup yum repository}
+
+Setup your yum repository to Dag's Yum Repository or similar. Dag's is recommended.
+
+\subsection{Required Packages}
+
+These packages are required:
+
+\begin{itemize}
+\item bridge-utils
+\item curl
+\item libidn
+\item sysfsutils
+\end{itemize}
+
+Use yum to install these packages.
+
+\begin{verbatim}
+yum install bridge-utils curl libidn sysfsutils
+\end{verbatim}
+
+\subsection{Download Xen}
+
+\subsection{Download the binary tarball}
+Download the Xen 3.0 binary tarball from the XenSource downloads page:
+
+\begin{quote} {\tt http://www.xensource.com/downloads/}
+\end{quote}
+
+\subsection{Extract and Install}
+
+\begin{verbatim}
+tar zxvf xen-unstable-install-x86\_32.tgz
+
+cd xen-unstable-install
+
+./install.sh 
+\end{verbatim}
+
+
+\subsection{Disable TLS}
+
+\begin{verbatim}
+mv /lib/tls /lib/tls.disabled
+\end{verbatim}
+
+\subsection{Creating initrd}
+
+You can use the distro's initrd. The following steps show you how to create one yourself for dom0 and domU. The example uses a Domain0 image, so to adatp it, simply use the appropriate image for DomainU.
+
+\begin{verbatim}
+run depmod 2.x.y-xen0 to re-create modules dependency
+
+mkinitrd  /boot/initrd-2.x.y-xen0.img  2.x.y-xen0 
+\end{verbatim}
+
+If you get an error
+
+\begin{verbatim}
+   "No module xxx found for kernel 2.x.y-xen0, aborting."
+\end{verbatim}
+
+uncheck xxx in \path{/etc/modprobe.conf} if you don't want support for xxx. If you know that its built into kernel (to check \path{grep -i xxx config-2.6.12-xen0}) you can do
+
+\begin{verbatim}
+mkinitrd  --builtin=aic7xxx  ./2.6.12-xen0.img  2.6.12-xen0
+\end{verbatim}
+
+If another yyy module is reported as "not found,"
+
+\begin{verbatim}
+mkinitrd  --builtin=xxx --builtin=yyy ./2.6.12-xen0.img  2.6.12-xen0
+\end{verbatim}
+
+\subsection{Grub Configuration}
+
+As usual, you need to make entry in grub configuration file for Xen. Here's a sample grub entry.
+
+{\small
+\begin{verbatim}
+title  Xen/RHEL 4.1
+       kernel (hd0,5)/boot/xen.gz dom0\_mem=256000
+       module (hd0,5)/boot/vmlinuz-2.6.11.12-xen0 root=/dev/hda6
+       module (hd0,5)/boot/initrd-2.6.11.12-xen0.img
+\end{verbatim}
+}
+
+\section{Source install}
+
+
+\subsection{Download Source Tarball}
+
+\subsection{Download the binary tarball}
+Download the Xen 3.0 binary tarball from the XenSource downloads page:
+
+\begin{quote} {\tt http://www.xensource.com/downloads/}
+\end{quote}
+
+\subsection{Pre-requisites to build from source}
+
+Make sure you have all packages. If you had chosen to install Development tools during the distro installation, you should not need to install any extra packages. If not, install the following:
+
+\begin{itemize}
+\item gcc-3.4.3-22.1
+\item python-devel-2.3.4-14.1
+\item zlib-devel-1.2.1.2-1
+\item curl-devel-7.12.1-5.rhel4
+\end{itemize}
+
+\subsection{Install Xen}
+
+\begin{verbatim}
+tar zxvf xen-unstable-src.tgz
+cd xen-unstable/
+make world
+make install
+\end{verbatim}
+
+The rest of the steps follow as with the binary tarball installation.