6,534
edits
Changes
m
1. == Intro==
2. == Installing XEN itself, Dom0 and XEN tools.==
- === Installing from tarball===
- === Building from sources===
- * build hypervizor xen.gz- * download linux kernel sources 2.6.16 source from kernel.org, patch them with a set of xen patches - * from sources obtained build the vmlinuz-2.6.16.33-xen XenLinux kernel that will be able to boot both in Dom0 and DomU- * build and install xm tool
3. == Installing OpenVZ XenLinux kernel.==
- install === Install from rpm===
Change directory to openvz and download Download rpm package with OpenVZ XenLinux kernel for x86:<pre># cd# cd openvz# wget from http://download.openvz.org/download/kernel/branches/rhel5-2.6.18/028stab034.1/ovzkernel-PAE-2.6.18-8.el5.xen.028stab034.i686.rpm</pre>
- install === Install from sources=== Download OpenVZ kernel source rpm from http://openvz.org/download/kernel/rhel5/.
Download rpm with OpenVZ kernel sources:
<pre>
# wget http://download.openvz.org/kernel/branches/rhel5-2.6.18/028stab034.1/ovzkernel-2.6.18-8.el5.028stab034.1.src.rpm
</pre>
- === install OpenVZ tools:===
- === download OpenVZ guest template===
4. == Preparing guest partition and configuring XEN.==
5. == Starting OpenVZ guest in DomU.==
- === starting===
- === next steps===
6. == RHEL5 based OpenVZ in Dom0. Known problems.==
7. == Appreciates==
Recently released RHEL5 kernel supports compatibility with XEN 3.0. It means that
</pre>
XEN 3.0 1 and XM tool can be installed in 2 ways: either from tarball containing prebuilt binaries or by building from sources.
==== Download/unpack ====Download XEN 3.1 32 bit PAE SMP tarball from [http://bitsxensource.com/download/dl_31tarballs.html xensource.com/ ] and unpack:
<pre>
# cd xen
# wget http://bits.xensource.com/oss-xen/release/3.1.0/bin.tgz/xen-3.1.0-install-x86_32p.tgz
# gunzip tar xvzf xen-3.1.0-install-x86_32p.tgz# tar -xvf xen-3.1.0-install-x86_32p.tar
</pre>
==== Install ====
Run the install.sh script within ./dist folder:
<pre>
</pre>
install.sh checks the presence of the required packages and installs hypervisor xen.gz and XenLinux vmlinuz-2.6.16.33-xen
to /boot and xm tool to /usr/sbin. ==== Configure the bootloader ====Now update /etc/grub.conf by adding the xen entry in the following way:
/etc/grub.conf:
<pre>
title Xen Linux (2.6.16.33-xen)
root (hd0,1)
kernel /boot/xen.gz dom0_mem=1048576-128M module /boot/vmlinuz-2.6.16.33-xen ro root=LABEL=/ console=ttyS0,115200 console=tty silencelevel=8
</pre>
Note the <code>root</code> option and the <code>root=</code> argument -- those should be the same as with your other bootloader entries. ==== Reboot ====Now you can reboot the machine. Choosing the Xen Linux (2.6.16.33-xen) from grub sequence will cause to booting xen hypervisor and Dom0 running Xen Linux (2.6.16.33-xen). In case of success you'll see the usual login prompt. If kernel panic takes place during boot - — reboot the machine into your usual working Linux and check if the xen related /etc/grub.conf entry is correct. If /etc/grub.conf entry is correct and xen kernel is unable to boot,- the reason is prebuild pre-built vmlinuz-2.6.16.33-xen does not contain
some drivers for your hardware, that are needed to be loaded by using initrd. In this case follow instructions below - "Building from sources".
==== Download/unpack ====
Download the package containing sources of Xen-3.1 and unpack it:
<pre>
# wget http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz
# gunzip tar xvzf xen-3.1.0-src.tgz# tar -xvf xen-3.1.0-src.tar
</pre>
==== Build ====
Change directory to ./xen-3.1.0-src:
<pre>
</pre>
Building process will do the following:
==== Install ====
After building is complete run ./install.sh script:
<pre>
# ./install.sh
</pre>
As a result vmlinuz-2.6.16.33-xen, xen.gz will be placed to /boot, xm tool will be placed to /usr/sbin. Now it is time to create initrd for vmlinuz-2.6.16.33-xen. Check that /lib/modules contain recently created directory 2.6.16.3318-xen. If it is, type:
<pre>
# mkinitrd -f -v /boot/initrd-2.6.16.33-xen.img 2.6.16.3318-xen
</pre>
After initrd-2.6.16.3318-xen.img is succesfully created , update corresponding strings in /etc/grub.conf:
<pre>
title Xen Linux (2.6.16.33-xen)
root (hd0,1)
kernel /boot/xen.gz dom0_mem=1048576-128M module /boot/vmlinuz-2.6.16.33-xen ro root=LABEL=/ console=ttyS0,115200 console=tty silencelevel=8 module /boot/initrd-2.6.16.33-xen.img
</pre>
Xen 3.0 doesn't support TLS. To make xen work correct , disable TLS on your machine bu renaming /lib/tls to /lib/tls.disabled:
<pre>
# mv /lib/tls /lib/tls.disabled
</pre>
Check that kernel command line options are correct (after ro ...) and reboot the machine. In grub loader menu select "Xen Linux (2.6.16.33-xen)". In case of success - machine boots into Xen's Dom0 that is running vmlinuz-2.6.16.33-xen XenLinux. Now it is time to prepare OpenVZ XenLinux kernel for DomU.
OpenVZ XenLinux kernel can be installed in 2 ways: either from rpm containing or by
building from sources.
Install downloaded rpm:
<pre>
# rpm -ihv ovzkernel-PAExen-2.6.18-8.el5.xen.028stab033.i686*.rpm
</pre>
If something goes wrong during installation the prebuilt kernel - you can build the OpenVZ XenLinux kernel from sources as described below.
Unpack downloaded rpm package:
<pre>
# rpm2cpio ovzkernel-2.6.18-8.el5.028stab034.1*.src.rpm > ovzkernel-2.6.18-8.el5.028stab034.1.src.cpio# | cpio -i < ovzkernel-2.6.18-8.el5.028stab034.1.src.cpioid
</pre>
Check that ./kernel-ovz.spec contains the following strings:
OpenVZ XenLinux kernel prepared. Now OpenVZ tools are to be installed. In case you faced problem while building the kernel turn to article http://wiki.openvz.org/Kernel_build .
Now download and install latest versions of OpenVZ tools vzctl, vzquota that are necessary for starting/stopping VEs:
More information on installing OpenVZ tools can be found here: http://wiki.openvz.org/Quick_installation.
To make it possible to create VEs download one of the precreated OpenVZ templates and place it to /vz/template/cache:
</pre>
Xen users manual http://www.xensource.com/products/xen/documentation.html describes a set of different ways of creating disk for DomU. Disk can be created using loopback or LVM or physical partition. Consider we have a standalone physical partition /dev/sda7 that will be used for creating DomU disk. Assume /dev/sda7 is empty and it contains ext3 filesystem.
Preparations completed. At this point we have everything that is necessary for cretaing DomU and starting OpenVZ XenLinux within DomU. Reboot into Xen: select Xen Linux (2.6.16.33-xen) item from grub menu. After reboot machine will be running vmlinuz-2.6.16.33-xen (see above) in Dom0 over hypervisor. Follow instructions below.
Start xend daemon to make xm tool work:
It works.
As OpenVZ works in DomU it is the best time for configuring network both in DomU and VEs. This process is described in http://www.xensource.com/products/xen/documentation.html (DomU) and http://wiki.openvz.org/Category:Networking (VEs). After this all of us will feel the full power of virtualization!
OpenVZ XenLinux kernel is able to work also in Dom0. It can be tested just by updating /etc/grub.conf on the hardware node. But in this case it will be impossible to start DomUs. It is a known bug and it is related not to OpenVZ, but to RHEL5 kernel.
Hope it is fixed in next RHEL5 update.
Thanks to Sergey Ya. Korshunoff seyko@ for starting the topic and contribution.