Differences

This shows you the differences between two versions of the page.

--- xen:installation_of_dom0 [2011/02/04 17:41]
Luc Nieland
+++ xen:installation_of_dom0 [2011/03/27 20:38] (current)
Luc Nieland [Debian 6.0 (Squeeze)]
@@ Line 1: / Line 1: @@
 ======Building a Dom0======
+Various distributions deliver the base to create a Xen domain-zero (Dom0). Below a few step-by-step CLI guides on getting from bare metal to a Dom0 for PV or HVM.
-=====Debian 6.0 (Squeeze)=====
+=====Suse=====
+====OpenSuse 11.4====
+Install a minimal OpenSuse system, choose "other" graphical system, and choose text based server).
+Now the system will come up with a graphical-screen (ROTFL). With ctrl-alt-F1 change to text-mode and log in with the created non-root user during install. Use:
+  sudo su - root
+  passwd root
+to go to a more comfortable area.
+Use yast:
+  * system ->  System Services (expert): to the default runlevel to 3
+  * security -> firewall: to disable the firewall
+  * system -> System Services: to enable sshd in runlevel 3 (and optionally 4 and 5)
+  * network -> to change the hostname and make the IP static
+Update the repository cache and install generic usefull stuff:
+  zypper up
+  zypper install  mc iputils man bind-util vim-enhanced tcpdump rsync wget iftop
+De-install conflicting patterns-openSUSE-minimal_base because it conflicts with python-base (which is a requirement for xen-tools). As a replacment for the package, some other packages need to be installed:
+  zypper remove  patterns-openSUSE-minimal_base
+  zypper install  python-base
+Install the Xen hypervisor and a Xen-enabled Linux dom0 kernel:
+  zypper install  libvirt  xen-libs    xen  kernel-xen  xen-tools
+Extra stuff:
+  zypper install  libvirt-python  vm-install  xen-tools-ioemu
+The required linux-bridging stuff has come as dependency.
+Change the default boot-option to the Xen hypervisor in /boot/grub/menu.lst
+  default 0
+As an alternative for cmdline zypper; use Yast: Virtualization -> Install Hypervisor and Tools -> Xen to install the Xen hypervisor and dom0 patched kernel. Resolve the python dependency also.
+===bridged networking===
+Configure in /etc/xen/xend-config.sxp the following network-script line (and comment out all other network-script lines):
+  (network-script hannibal-xen-network-script)
+Leave the line as is:
+  (vif-script vif-bridge)
+And create a file (chmod +x) /etc/xen/scripts/hannibal-xen-network-script (an example for a machine with four physical NIC's:
+  #!/bin/sh
+  BASEPATH=/etc/xen/scripts
+  ${BASEPATH}/network-bridge "$@" vifnum=0 netdev=eth0 bridge=xenbr0
+  ${BASEPATH}/network-bridge "$@" vifnum=1 netdev=eth1 bridge=xenbr1
+  ${BASEPATH}/network-bridge "$@" vifnum=2 netdev=eth2 bridge=xenbr2
+  ${BASEPATH}/network-bridge "$@" vifnum=3 netdev=eth3 bridge=xenbr3
+===References===
+Further reading:
+  * [[http://www.scribd.com/doc/43734889/Xen3-Zero-to-Xen-From-the-CLI-in-OpenSuSE-10-3]]
+  *
+=====Debian=====
+====Debian 6.0 (Squeeze)====
 Install a minimal Debian-6 (Squeeze) system in 64 bit. Preferrably configured with a static IP-configuration in /etc/network/interfaces (ie. DHCP-client not tested).
@@ Line 16: / Line 88: @@
-====grub2 corrections and tuning====
+===grub2 corrections and tuning===
 IMPORTANT! Make the Xen-hypervisor the first boot entry in grub:
   mv /etc/grub.d/20_linux_xen /etc/grub.d/08_linux_xen
@@ Line 33: / Line 105: @@
-====bridged networking====
+===bridged networking===
 When the physical machine (ie the dom0) has more than 1 physical NIC, configure in /etc/xen/xend-config.sxp the following network-script line (and comment out all other network-script lines):
   (network-script hannibal-xen-network-script)
@@ Line 44: / Line 116: @@
   #!/bin/sh
   BASEPATH=/etc/xen/scripts
-  ${BASEPATH}/network-bridge "$@" vifnum=0 netdev=eth0 bridge=xenbr0
+  ${BASEPATH}/network-bridge "$@" vifnum=0 bridge=xenbr0 netdev=eth0
-  ${BASEPATH}/network-bridge "$@" vifnum=1 netdev=eth1 bridge=xenbr1
+  ${BASEPATH}/network-bridge "$@" vifnum=1 bridge=xenbr1 netdev=eth1
-  ${BASEPATH}/network-bridge "$@" vifnum=2 netdev=eth2 bridge=xenbr2
+  ${BASEPATH}/network-bridge "$@" vifnum=2 bridge=xenbr2 netdev=eth2
-  ${BASEPATH}/network-bridge "$@" vifnum=3 netdev=eth3 bridge=xenbr3
+  ${BASEPATH}/network-bridge "$@" vifnum=3 bridge=xenbr3 netdev=eth3
@@ Line 54: / Line 126: @@
-In /etc/rc.local the following has to be added to make the bridges which have no IP-number working for the domU's:
-  /sbin/ifconfig xenbr0 up
+Now there is a working setup, with multiple bridges. However, only the bridge which is configured with an IP-adress with a working gateway is activated fast. It takes a few minutes for the other bridges to come up. This is a bug in /etc/xen/scripts/network-bridge (squeeze/jan 2011)
-  /sbin/ifconfig xenbr1 up
-  /sbin/ifconfig xenbr2 up
+The fix is to subsititute the line 118 with lines 119-121:
-  /sbin/ifconfig xenbr3 up
+         #[ -n "$gateway" ] && ip route add default via ${gateway}
+         if [ -n "$gateway" ]; then
+             ip route add default via ${gateway}
+         fi
-===udev===
+See also: [[http://lists.xensource.com/archives/html/xen-users/2010-06/msg00420.html]]
-If you have troubles with udev creating firewire network devices that mess up your intended network configuration, rename them to a higher ethX number in:
-  /etc/udev/rules.d/70-persistent-net.rules
+==network devices==
+If your hardware has a firewire device, udev will automatically create network devices (i.e. ethN) for them. Great, is'n it :-)  If you do not want this, edit  /etc/udev/rules.d/70-persistent-net.rules  and give them a proper name like firewN or completely disable them.
+Add contrib and non-free to /etc/apt/sources and install the Realtec binary-firmware, and update your initrd image:
+  apt-get install firmware-realtek
+  apt-get install firmware-linux-nonfree
+  update-initramfs -u
-====Refs====
+===Refs===
 See also:
   * [[http://wiki.debian.org/Xen]]
@@ Line 78: / Line 158: @@
-=====Debian 5.0 (Lenny)=====
+====Debian 5.0 (Lenny)====
 See Debian 4.0
-=====Debian 4.0 (Etch)=====
+====Debian 4.0 (Etch)====
-====Core OS and hypervisor====
+===Core OS and hypervisor===
-===create a bootable system===
+==create a bootable system==
 With the availability of 64-bit hardware in mind, we only use the AMD64 port of Debian Etch in order to create Xen enabled servers. There are several reasons for this decision, one of them is to avoid the TLS-issue's with the 32-bit Xen hypervisor on x86 CPU's.
@@ Line 122: / Line 202: @@
 A reboot will complete the installation.
-===Xen config===
+==Xen config==
 In /etc/default/xendomains, the following option can be changed to:
   XENDOMAINS_SAVE=""
@@ Line 197: / Line 277: @@
-=====Debian 3.0 (Sarge)=====
+====Debian 3.0 (Sarge)====
-====Core operating system and hypervisor====
+===Core operating system and hypervisor===
-===create a bootable system===
+==create a bootable system==
 Start with the install of a minimal working Debian-sarge on your bare metal. Download a debian-31r2-i386-netinst.iso for this. At the end of the install procedure, answer no to the options task-select and dselect. As the result of this, you end up wit a minimal system. Use apt-get softwarepackagename to install stuff you need. For example ssh could be useful.
@@ Line 278: / Line 358: @@
+=====Redhat=====
-======Debian Dom0 additions======
+====Redhat 6.x ====
-====Volume manager====
+RHEL-6 does not ship Xen hypervisor or tools and does not ship Xen dom0 capable kernel.
+It can be build, see: http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial
+=====Dom0 additions=====
+====Debian====
+===Volume manager===
 We prefer to run our Xen guests from logical volumes instead of running them from loop mounted files. By default we choose to format the file systems of the Xen guests to xfs.
 Install the necessary LVM and XFS packages:
@@ Line 310: / Line 401: @@
 ====Power====
 For APC equipment, there is software ready in the Debian repository. Good reason to buy this if you need uninterrupted power. After connecting the equipment (power and USB-cabling), install the ups-daemon software:
   apt-get install  apcupsd apcupsd-doc apcupsd-cgi
 Edit the configfile /etc/apcupsd/apcupsd.conf
 <code>
+## apcupsd.conf v1.1 ##
+#
+#  for apcupsd release 3.14.8 (16 January 2010) - debian
+#
+# "apcupsd" POSIX config file
 UPSNAME ups01
 UPSCABLE usb

HannibalWiki

User Tools

Site Tools

Differences

Page Tools