Set up and Run Linux Xen Dom0 and DomU VMs
Posted on In Linux, VirtualizationThe Xen solutions including installing and configuring Dom0 and DomU are summarized here.
LVM volumes as backing for DomU’s file system is an appealing solution to Xen VBD. LVM volumes can dynamically grow/shrink and snapshot. These features make it simple and fast to duplicate DomU and adding storage to DomU. LVM backed DomU is recommended.
Table of Contents
Dom0 installation and configuration
Installing Xen (Domain-0) on Fedora 17
Setting up Stable Xen Dom0 with Fedora: Xen 3.4.3 with Xenified Linux Kernel 2.6.32.13 in Fedora 12
DomU installation and configuration
Installing Fedora 17 Domain-U on Xen with PXE Booting.
LVM backed Xen DomU is quite stable with high performance that uses unmodified Fedora pv_ops kernel:
Setting Up LVM Backed Xen DomU
Setting Up Ubuntu DomU on Xen: Use Ubuntu 10.10 on Fedora Xen Dom0
Dom0 management
Dom0’s CPU and memory configuration advises:
Managing Xen Dom0′s CPU and Memory
DomU management
Duplicating LVM Backed Xen DomU
Duplicating and Backing Up LVM Backed Xen DomU from a Remote Server
Create and manage virtual machines on Xen
How to Duplicate Xen DomU Virtual Machines
Automatically backing up Xen File-backed DomU
Unified Xen DomU configuration file
LVM with Xen
A summary of tutorials related to Xen and LVM:[[xen-with-lvm|
]]
Problems
Some problems that may happen and their solution:
Hello I am a M.E student and I want to optimize live migration of virtual machine using xen. So how can I achieve it. orelse how can I do tcp analysis in xen durin live migration.
Any help will be great Sir.
Thanx.
Hi,
You may want to take a look at this: http://wiki.xen.org/wiki/Migration
For TCP analysis, other tools, such as tcpdump, may help you.
hi i’m also m.e doing my project in xen ..i ‘ve a problem in installation of xen from source code.
Cloning into ‘seabios-dir-remote.tmp’…
fatal: unable to connect to xenbits.xen.org:
xenbits.xen.org[0: 50.57.170.242]: errno=Connection timed out
make[4]: *** [seabios-dir] Error 128
make[4]: Leaving directory `/root/xen-4.2.1/tools/firmware’
As the output shows, you are building Xen-4.2.1 which possibly require a different method from the one introduced here.
From your output, the error is:
“Connection timed out”
–> check your network.
after rectifying that error i’m getting a new error like this
policydb.c: In function ‘policydb_read’:
policydb.c:1779: error: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘size_t’
make[7]: *** [policydb.o] Error 1
make[7]: Leaving directory `/root/xen-4.2.1/xen/xsm/flask/ss’
make[6]: *** [ss/built_in.o] Error 2
make[6]: Leaving directory `/root/xen-4.2.1/xen/xsm/flask’
make[5]: *** [flask/built_in.o] Error 2
make[5]: Leaving directory `/root/xen-4.2.1/xen/xsm’
make[4]: *** [/root/xen-4.2.1/xen/xsm/built_in.o] Error 2
make[4]: Leaving directory `/root/xen-4.2.1/xen/arch/x86′
make[3]: *** [/root/xen-4.2.1/xen/xen] Error 2
make[3]: Leaving directory `/root/xen-4.2.1/xen’
make[2]: *** [install] Error 2
make[2]: Leaving directory `/root/xen-4.2.1/xen’
make[1]: *** [install-xen] Error 2
make[1]: Leaving directory `/root/xen-4.2.1′
make: *** [world] Error 2
policydb.c: In function ‘policydb_read’:
policydb.c:1779: error: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘size_t’
make[7]: *** [policydb.o] Error 1
make[7]: Leaving directory `/root/xen-4.2.1/xen/xsm/flask/ss’
make[6]: *** [ss/built_in.o] Error 2
make[6]: Leaving directory `/root/xen-4.2.1/xen/xsm/flask’
make[5]: *** [flask/built_in.o] Error 2
make[5]: Leaving directory `/root/xen-4.2.1/xen/xsm’
make[4]: *** [/root/xen-4.2.1/xen/xsm/built_in.o] Error 2
make[4]: Leaving directory `/root/xen-4.2.1/xen/arch/x86′
make[3]: *** [/root/xen-4.2.1/xen/xen] Error 2
make[3]: Leaving directory `/root/xen-4.2.1/xen’
make[2]: *** [install] Error 2
make[2]: Leaving directory `/root/xen-4.2.1/xen’
make[1]: *** [install-xen] Error 2
make[1]: Leaving directory `/root/xen-4.2.1′
make: *** [world] Error 2
Hello I am student in technologies, I am working on a project to monitor virtual networks with Lattice Framework, does anyone know how to add the libraries from the Framework to use the Xen Hypervisor?