Starting with SLC4.5 Xen domU kernels as well as openafs kernel modules and other supporting packages are included in the standard distribution for i386/x86_64 architectures. If you have installed SLC4.4 Domain U on you systems, please followup the procedure below in order to update yous system to currently supported package versions:

rpm -e yum-xen-conf (not needed anymore on Domain U , all packages are included in base distribution)

yum update

rpm -Uvh http://linuxsoft.cern.ch/cern/slc4X/updates/i386/RPMS/mkinitrd-4.2.1.10-1.1.i386.rpm --oldpackage

rpm -e e2fsprogs-libs --nodeps

rpm -Uvh http://linuxsoft.cern.ch/cern/slc4X/updates/i386/RPMS/e2fsprogs-1.35-12.5.el4.i386.rpm \ http://linuxsoft.cern.ch/cern/slc4X/updates/i386/RPMS/e2fsprogs-devel-1.35-12.5.el4.i386.rpm --oldpackage

Make sure that your guest /etc/fstab refers to ALL partitions by label not physical device name

(in SLC4.4 virtual block devices were called /dev/sdX, in SLC4.5 these become /dev/xvdX)

Make sure that your hypervisor guest config files (/etc/xen/*) also use references to xvdX in stead of sdX

Please note that NOT applying the procedure above WILL result in boot failure of your Domain U system.

Interestingly, the hypervisor will use its own /dev/ directory to get the major/minor numbers for /dev/xvdX (as exported to the domU). So if you get errors such as

DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda'

on the hypervisor/xend, you will need to create the missing /dev/xvda on the hypervisor, via something like

# mknod /dev/xvda b 220 0

.

-- JaroslawPolok - 22 May 2007