Cheap VPS & Xen Server


Residential Proxy Network - Hourly & Monthly Packages

Installing Xen On An Ubuntu 7.10 (Gutsy Gibbon) Server From The Ubuntu Repositories


This tutorial provides step-by-step instructions on how to install Xen on an Ubuntu Gutsy Gibbon (Ubuntu 7.10) server system (i386). You can find all the software used here in the Ubuntu repositories, so no external files or compilation are needed.

Xen lets you create guest operating systems (*nix operating systems like Linux and FreeBSD), so called “virtual machines” or domUs, under a host operating system (dom0). Using Xen you can separate your applications into different virtual machines that are totally independent from each other (e.g. a virtual machine for a mail server, a virtual machine for a high-traffic web site, another virtual machine that serves your customers’ web sites, a virtual machine for DNS, etc.), but still use the same hardware. This saves money, and what is even more important, it’s more secure. If the virtual machine of your DNS server gets hacked, it has no effect on your other virtual machines. Plus, you can move virtual machines from one Xen server to the next one.

I will use Ubuntu Gutsy Gibbon (i386) for the host OS (dom0) and Ubuntu Gutsy Gibbon and Ubuntu Feisty Fawn for the guest operating systems (domU). Other Debian-based distributions that can be installed using xen-tools are Debian Etch, Debian Lenny, Debian Sid, and Debian Sarge, as well as Ubuntu Dapper Drake and Ubuntu Edgy Eft.

This howto is meant as a practical guide; it does not cover the theoretical backgrounds. They are treated in a lot of other documents in the web.

This document comes without warranty of any kind! I want to say that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you!

 

1 Install The Ubuntu Gutsy Gibbon Host System (dom0)

You can install the host system (dom0) as shown in the chapters one to nine of this tutorial: http://www.Kreationnext.com/perfect_server_ubuntu7.10 (of course, you don’t have to do this if you already have an Ubuntu 7.10 host system that you want to use).

Make sure that you are logged in as root (type in

sudo su

to become root), because we must run all the steps from this tutorial as root user. Also, if you want to use vi as your text editor (as suggested by this tutorial), you should run

apt-get install vim-full

The vim-full package makes sure that the vi text editor behaves as expected (without vim-full, you might experience some strange behaviour in the vi text editor).

dom0‘s FQDN in this example will be server1.example.com. server1.example.com‘s IP address will be 192.168.0.100 in this tutorial, and the gateway I use is 192.168.0.1, so the virtual machines will have to use that one, too.

 

2 Install Xen

To install Xen and all needed dependencies, all we have to do is run the following command:

apt-get install ubuntu-xen-server

This will also install the xen-tools package which we use later on to create virtual machines.

Now we edit /etc/xen/xend-config.sxp. Comment out the (network-script network-dummy) line and add (network-script network-bridge) right above the (vif-script vif-bridge) line, like this:

vi /etc/xen/xend-config.sxp

[...]
#(network-script network-dummy)

# The script used to control virtual interfaces.  This can be overridden on a
# per-vif basis when creating a domain or a configuring a new vif.  The
# vif-bridge script is designed for use with the network-bridge script, or
# similar configurations.
#
# If you have overridden the bridge name using
# (network-script 'network-bridge bridge=<name>') then you may wish to do the
# same here.  The bridge name can also be set when creating a domain or
# configuring a new vif, but a value specified here would act as a default.
#
# If you are using only one bridge, the vif-bridge script will discover that,
# so there is no need to specify it explicitly.
#
(network-script network-bridge)
(vif-script vif-bridge)
[...]

We also need to add the loop module to the kernel every time we boot our system, so we edit /etc/modules. If you already have a loop line in there, make it look like this, otherwise add it:

vi /etc/modules

[...]
loop max_loop=64
[...]

Now take a look at the /boot directory to see which kernels and ramdisks are installed:

ls -l /boot/

root@server1:~# ls -l /boot/
total 32948
-rw-r–r– 1 root root  424317 2007-10-15 03:42 abi-2.6.22-14-server
-rw-r–r– 1 root root   75416 2007-10-15 03:42 config-2.6.22-14-server
-rw-r–r– 1 root root   76107 2007-10-15 03:49 config-2.6.22-14-xen
drwxr-xr-x 2 root root    4096 2007-10-30 13:02 grub
-rw-r–r– 1 root root 7080785 2007-10-18 12:57 initrd.img-2.6.22-14-server
-rw-r–r– 1 root root 6794412 2007-10-18 12:50 initrd.img-2.6.22-14-server.bak
-rw-r–r– 1 root root 6871299 2007-10-30 13:02 initrd.img-2.6.22-14-xen
-rw-r–r– 1 root root 6871266 2007-10-30 13:01 initrd.img-2.6.22-14-xen.bak
-rw-r–r– 1 root root  103204 2007-09-28 12:06 memtest86+.bin
-rw-r–r– 1 root root  828819 2007-10-15 03:42 System.map-2.6.22-14-server
-rw-r–r– 1 root root  806408 2007-10-15 03:49 System.map-2.6.22-14-xen
-rw-r–r– 1 root root 1787224 2007-10-15 03:42 vmlinuz-2.6.22-14-server
-rw-r–r– 1 root root 1596690 2007-10-15 03:49 vmlinuz-2.6.22-14-xen
-rw-r–r– 1 root root  308810 2007-10-12 17:10 xen-3.1.gz
root@server1:~#

The /boot/vmlinuz-2.6.22-14-xen kernel is the Xen kernel that got installed together with the ubuntu-xen-server package, and /boot/initrd.img-2.6.22-14-xen is its ramdisk. We will need these soon.

You can now also take a look at the /usr/lib/xen-tools directory because it reveals which distributions can be installed in a virtual machine with xen-tools:

ls -l /usr/lib/xen-tools

root@server1:~# ls -l /usr/lib/xen-tools
total 32
drwxr-xr-x 2 root root 4096 2007-10-30 13:00 centos4.d
-rwxr-xr-x 1 root root 4306 2007-09-17 01:13 common.sh
drwxr-xr-x 2 root root 4096 2007-10-30 13:00 dapper.d
drwxr-xr-x 2 root root 4096 2007-10-30 13:00 debian.d
drwxr-xr-x 2 root root 4096 2007-10-30 13:00 edgy.d
lrwxrwxrwx 1 root root    8 2007-10-30 13:00 etch.d -> debian.d
drwxr-xr-x 2 root root 4096 2007-10-30 13:00 fedora.d
lrwxrwxrwx 1 root root    6 2007-10-30 13:00 feisty.d -> edgy.d
drwxr-xr-x 2 root root 4096 2007-10-30 13:00 gentoo.d
lrwxrwxrwx 1 root root    6 2007-10-30 13:00 gutsy.d -> edgy.d
lrwxrwxrwx 1 root root    8 2007-10-30 13:00 lenny.d -> debian.d
lrwxrwxrwx 1 root root    8 2007-10-30 13:00 sarge.d -> debian.d
lrwxrwxrwx 1 root root    8 2007-10-30 13:00 sid.d -> debian.d
lrwxrwxrwx 1 root root    8 2007-10-30 13:00 stentz.d -> fedora.d
root@server1:~#

As you see we can install the following distributions:

  • Debian: Etch, Lenny (testing), Sid (unstable), Sarge
  • Ubuntu: Dapper Drake, Edgy Eft, Feisty Fawn, Gutsy Gibbon
  • CentOS 4
  • Fedora Core 4 (Stentz)
  • Gentoo

(I haven’t tried to install CentOS, Fedora, and Gentoo with xen-tools yet, so I can’t say how good it works.)

I want to store my virtual machines in the /home/xen directory, therefore I create it now:

mkdir /home/xen

We will use xen-tools to create virtual machines. xen-tools make it very easy to create virtual machines – please read this tutorial to learn more: http://www.Kreationnext.com/xen_tools_xen_shell_argo. As mentioned before, the xen-tools package got installed together with the ubuntu-xen-server package.

Now we edit /etc/xen-tools/xen-tools.conf. This file contains the default values that are used by the xen-create-image script unless you specify other values on the command line. I changed the following values and left the rest untouched:

vi /etc/xen-tools/xen-tools.conf

[...]
dir = /home/xen
[...]
dist   = gutsy     # Default distribution to install.
[...]
gateway   = 192.168.0.1
netmask   = 255.255.255.0
broadcast = 192.168.0.255
[...]
passwd = 1
[...]
mirror = http://de.archive.ubuntu.com/ubuntu/
[...]

The dist line holds the default distribution that you want to install in a virtual machine. The contents of the /usr/lib/xen-tools directory reveals which distributions are available (see above).

The kernel line must contain our Xen kernel, and the initrd line its ramdisk. The default /etc/xen-tools/xen-tools.conf file has the values kernel = /boot/vmlinuz-`uname -r` and initrd = /boot/initrd.img-`uname -r` which automatically translate to the correct kernel and ramdisk, so we don’t have to modify these lines.

The passwd = 1 line makes that you can specify a root password when you create a new guest domain. In the mirror line specify an Ubuntu mirror close to you.

Make sure you specify a gateway and netmask. If you don’t, and you don’t specify a gateway and netmask on the command line when using xen-create-image, your guest domains won’t have networking even if you specified an IP address!

Now reboot the system:

shutdown -r now

If your system reboots without problems, then everything is fine!

Run

uname -r

and your new Xen kernel should show up:

root@server1:~# uname -r
2.6.22-14-xen
root@server1:~#

3 Creating Virtual Machines (domU)

Now let’s create our first guest domain, xen1.example.com, running Gutsy Gibbon (gutsy) with the IP address 192.168.0.101:

xen-create-image –hostname=xen1.example.com –size=2Gb –swap=256Mb –ide \
–ip=192.168.0.101 –netmask=255.255.255.0 –gateway=192.168.0.1 –force \
–dir=/home/xen –memory=64Mb –arch=i386 –kernel=/boot/vmlinuz-2.6.22-14-xen \
–initrd=/boot/initrd.img-2.6.22-14-xen –debootstrap –dist=gutsy \
–mirror=http://de.archive.ubuntu.com/ubuntu/ –passwd

A lot of switches are unnecessary here because we specified the same details in /etc/xen-tools/xen-tools.conf but it shows that you can specify the desired settings either on the command line or in /etc/xen-tools/xen-tools.conf. Please make sure that you specify –ide, otherwise your virtual machine might not boot!

(To learn more about the available options, take a look at the xen-create-image man page:

man xen-create-image

)

The xen-create-image command will now create the xen1.example.com virtual machine for us. This can take a few minutes. The output should be similar to this one:

root@server1:~# xen-create-image –hostname=xen1.example.com –size=2Gb –swap=256Mb –ide \
–dir=/home/xen –memory=64Mb –arch=i386 –kernel=/boot/vmlinuz-2.6.22-14-xen \
–initrd=/boot/initrd.img-2.6.22-14-xen –debootstrap –dist=gutsy \
–mirror=http://de.archive.ubuntu.com/ubuntu/ –passwd> –ip=192.168.0.101 –netmask=255.255.255.0 –gateway=192.168.0.1 –force \
> –dir=/home/xen –memory=64Mb –arch=i386 –kernel=/boot/vmlinuz-2.6.22-14-xen \
> –initrd=/boot/initrd.img-2.6.22-14-xen –debootstrap –dist=gutsy \
> –mirror=http://de.archive.ubuntu.com/ubuntu/ –passwd
Unknown option: debootstrap

General Information
——————–
Hostname       :  xen1.example.com
Distribution   :  gutsy
Fileystem Type :  ext3

Size Information
—————-
Image size     :  2Gb
Swap size      :  256Mb
Image type     :  sparse
Memory size    :  64Mb
Kernel path    :  /boot/vmlinuz-2.6.22-14-xen
Initrd path    :  /boot/initrd.img-2.6.22-14-xen

Networking Information
———————-
IP Address 1   : 192.168.0.101
Netmask        : 255.255.255.0
Broadcast      : 192.168.0.255
Gateway        : 192.168.0.1

Creating swap image: /home/xen/domains/xen1.example.com/swap.img
Done

Creating disk image: /home/xen/domains/xen1.example.com/disk.img
Done

Creating ext3 filesystem on /home/xen/domains/xen1.example.com/disk.img
Done
Installation method: debootstrap
Done

Running hooks
Done

No role script specified.  Skipping

Creating Xen configuration file
Done
Setting up root password
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
All done

Logfile produced at:
/var/log/xen-tools/xen1.example.com.log
root@server1:~#

There should now be a xen1.example.com configuration file – /etc/xen/xen1.example.com.cfg. Take a look at it to become familiar with virtual machine configuration files:

cat /etc/xen/xen1.example.com.cfg

#
# Configuration file for the Xen instance xen1.example.com, created
# by xen-tools 3.5 on Tue Oct 30 14:55:46 2007.
#
#
#  Kernel + memory size
#
kernel      = '/boot/vmlinuz-2.6.22-14-xen'
ramdisk     = '/boot/initrd.img-2.6.22-14-xen'
memory      = '64'
#
#  Disk device(s).
#
root        = '/dev/hda1 ro'
disk        = [ 'file:/home/xen/domains/xen1.example.com/disk.img,hda1,w', 'file:/home/xen/domains/xen1.example.com/swap.img,hda2,w' ]
#
#  Hostname
#
name        = 'xen1.example.com'
#
#  Networking
#
vif         = [ 'ip=192.168.0.101' ]
#
#  Behaviour
#
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

(Please note: if you have a dual-core CPU and want the virtual machine to use both CPU cores, please add the line vcpus = ‘2’ to the configuration file, like this:

vi /etc/xen/xen1.example.com.cfg

#
# Configuration file for the Xen instance xen1.example.com, created
# by xen-tools 3.5 on Tue Oct 30 14:55:46 2007.
#
#
#  Kernel + memory size
#
kernel      = '/boot/vmlinuz-2.6.22-14-xen'
ramdisk     = '/boot/initrd.img-2.6.22-14-xen'
memory      = '64'
vcpus       = '2'
#
#  Disk device(s).
#
root        = '/dev/hda1 ro'
disk        = [ 'file:/home/xen/domains/xen1.example.com/disk.img,hda1,w', 'file:/home/xen/domains/xen1.example.com/swap.img,hda2,w' ]
#
#  Hostname
#
name        = 'xen1.example.com'
#
#  Networking
#
vif         = [ 'ip=192.168.0.101' ]
#
#  Behaviour
#
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

Afterwards, in the virtual machine, you can run the command

cat /proc/cpuinfo

to check that both CPU cores are being used by the virtual machine. The output could look like this if your vm is using both cores:

xen1:~# cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 75
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping        : 2
cpu MHz         : 2210.054
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu tsc msr pae mce cx8 apic mca cmov pat pse36 clflush mmx fxsr
sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni
cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc
bogomips        : 5526.81

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 75
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping        : 2
cpu MHz         : 2210.054
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu tsc msr pae mce cx8 apic mca cmov pat pse36 clflush mmx fxsr
sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up pni
cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc
bogomips        : 5526.81

xen1:~#

)

To start the virtual machine, run

xm create /etc/xen/xen1.example.com.cfg

Run

xm console xen1.example.com

to log in on that virtual machine (type CTRL+] if you are at the console, or CTRL+5 if you’re using PuTTY to go back to dom0), or use an SSH client to connect to it (192.168.0.101).

To get a list of running virtual machines, type

xm list

The output should look like this:

root@server1:~# xm list
Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0      327     1 r—–    687.7
xen1.example.com                           1       64     1 -b—-     22.4
root@server1:~#

To shut down xen1.example.com, do this:

xm shutdown xen1.example.com

If you want vm01 to start automatically at the next boot of the system, then do this:

ln -s /etc/xen/xen1.example.com.cfg /etc/xen/auto

Here are the most important Xen commands:

xm create -c /path/to/config – Start a virtual machine.
xm shutdown <name> – Stop a virtual machine.
xm destroy <name> – Stop a virtual machine immediately without shutting it down. It’s as if you switch off the power button.
xm list – List all running systems.
xm console <name> – Log in on a virtual machine.
xm help – List of all commands.

Let’s create a second vm, xen2.example.com with the IP address 192.168.0.102 and Feisty Fawn (feisty) as the operating system:

xen-create-image –hostname=xen2.example.com –size=2Gb –swap=256Mb –ide \
–ip=192.168.0.102 –netmask=255.255.255.0 –gateway=192.168.0.1 –force \
–dir=/home/xen –memory=64Mb –arch=i386 –kernel=/boot/vmlinuz-2.6.22-14-xen \
–initrd=/boot/initrd.img-2.6.22-14-xen –debootstrap –dist=feisty \
–mirror=http://de.archive.ubuntu.com/ubuntu/ –passwd

Afterwards, you can start xen2.example.com like this:

xm create /etc/xen/xen2.example.com.cfg

… and shut it down like this:

xm shutdown xen2.example.com

A list of all virtual machines that were created with the xen-create-image command is available under

xen-list-images

root@server1:~# xen-list-images
Name: xen1.example.com
Memory: 64
IP: 192.168.0.101

Name: xen2.example.com
Memory: 64
IP: 192.168.0.102
root@server1:~#

To learn more about what you can do with xen-tools, take a look at this tutorial: http://www.Kreationnext.com/xen_tools_xen_shell_argo

 

  • Xen: http://www.xensource.com/xen/
  • xen-tools: http://xen-tools.org/software/xen-tools
  • Ubuntu: http://www.ubuntu.com/

Comments

comments