Changes between Version 5 and Version 6 of Doc/OS/Xen


Ignore:
Timestamp:
Feb 7, 2008, 1:13:27 PM (18 years ago)
Author:
/C=IE/O=Grid-Ireland/OU=cs.tcd.ie/L=RA-TCD/CN=Stephen O. Childs
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/OS/Xen

    v5 v6  
    5454 * Set up the mapping between the node name and hardware template in the site databases template ({{{site/databases.tpl}}} or {{{pro_site_databases.tpl}}}.
    5555 * Include the template {{{config/xen/guest}}} in the node's template.
     56
     57= Issues =
     58== Hardware issues ==
     59 * On the later Dell PE1950 machines there is an incompatibility between the network card and the Xen network setup. '''This will cause you to lose network connectivity when Xen starts up.''' There is a workaround documented [http://wiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround here].
     60
     61== LVM ==
     62 * For some reason, when the Xen kernel is installed on the host, the initrd that is created does not have the necessary modules for LVM included. If your root filesystem is hosted on LVM, then your machine won't be able to find it at boot time. To ensure that the LVM modules are included in your initrd, do this '''before''' booting into Xen for the first time:
     63{{{
     64mkinitrd --preload dm-mod <initrd file name> <kernel version>
     65}}}
     66 * For example on an sl450-x86_64 machine the command would be as follows:
     67{{{
     68mv /boot/initrd-2.6.18-1.2835.slc4xen.img /boot/initrd-2.6.18-1.2835.slc4xen.img.orig
     69mkinitrd --preload dm-mod /boot/initrd-2.6.18-1.2835.slc4xen.img 2.6.18-1.2835.slc4xen
     70}}}
     71
     72 * Guest VMs shouldn't use LVM for their filesystems as it just adds needless complexity.