TableOfContents

Overview

Updating a debian etch (v4.1) system to lenny (v5.0) also involves an upgrade of xen from v3.0 to v3.2. This can create quite some hassle for specific setups.

The documentation below describes some of the issues, that we ran into, when we upgraded the https://systemausfall.org server.

Problematic details

Update the kernel

To ease the maintenance of the domU kernel during upgrades, we use symlinks in /boot:

thorax:~# ls -l /boot
lrwxrwxrwx 1 root root       35 2008-12-28 05:20 domU-initrd -> /boot/initrd.img-2.6.18-6-xen-amd64
lrwxrwxrwx 1 root root       32 2008-12-28 05:20 domU-kernel -> /boot/vmlinuz-2.6.18-6-xen-amd64
 -- snipped some more details --

Update these links to the new domU kernel:

lrwxrwxrwx 1 root root       35 2008-12-28 05:20 domU-initrd -> /boot/initrd.img-2.6.26-1-xen-amd64
lrwxrwxrwx 1 root root       32 2008-12-28 05:20 domU-kernel -> /boot/vmlinuz-2.6.26-1-xen-amd64

Make sure, that all xen host configuration files (e.g. in /etc/xen/ or /etc/xen/vm/) contain the following lines:

kernel  = '/boot/domU-kernel'
ramdisk = '/boot/domU-initrd'

Update the configuration file of xen-tools (/etc/xen-tools/xen-tools.conf) to use these kernel symlinks by default for new xen hosts:

kernel = /boot/domU-kernel
initrd = /boot/domU-initrd
#kernel      = /boot/vmlinuz-`uname -r`
#initrd      = /boot/initrd.img-`uname -r`

Update the new module directory in all domU

Plain copying

Using a shared read-only blockdevice for all domU

Here we use a separate partition for /lib/modules that is shared among all domU hosts.


Creative Commons Lizenzvertrag
This page is licensed under a Creative Commons Attribution-ShareAlike 2.5 License.