Description : ------------ You will find here, full Linux templates released by Alyseo for Citrix XenServer 5.0.0 Build and tested on Version 5.0.0-10918p (hotfix1,2,3 installed). Informations : ------------- This is a clean way to install not supported Linux distro on Citrix XenServer. It work the same way on XenServer or Essentials (does not matter which type of storage you are using : local or shared). But keep in mind, it work fine for us but it is provided as is : use at your own risk. PS: This is of course not supported by Citrix, use the community forum. Install : -------- - Download the .xva file (full template) : .xva : no compression or .xva.7z : compressed with windows 7-zip util (http://www.7-zip.org/) - Verify the md5sum, always a good idea ;-) - Then import the template on your XS installation using : xencenter : Files/Import VM.../Import type: Exported template/Browse and select the uncompressed .xva file previously downloaded. or xenserver cli : xe vm-import option option - In xencenter : Select View/Custom Templates - Now you can deploy new VM using the full template installed. - If you are located in France, then update /etc/apt/sources.list and change all the fr server name. - These templates have been done on and for XS5.0, if you would like to deploy them on XS5.5 and to avoid XenCenter 5.5 warning "Tools out of date (version 5.0 installed)." : Xencenter / Console : select xs-tools.iso as DVD Drive Mount it as root : mount /dev/xvdd /mnt cd /mnt/Linux/ dpkg -i xe-guest-utilities_5.5.0-458_i386.deb or dpkg -i xe-guest-utilities_5.5.0-458_amd64.deb (for the 64bits version) - If you are planning to use the physical DVD feature, then you MUST first do the commands below or you VM will freeze : # cat >> /etc/modules isofs CTRL-D # reboot PS: Thanks to Hillel Seltzer for this bug report, for details see : http://forums.citrix.com/thread.jspa?messageID=1396464� Rem : ---- Boot error/warning : - "Couldnt get a file descriptor referring to the console", is generated by fgconsole and can be ignored. We remove some (console-setup startup script has been disabled) but do not find where the others are coming from (initramfs maybe?). - ACPI error regarding fan.ko and thermal.ko can be ignored : all kernel boot options to disable ACPI/APCI are not working because these modules are now loaded in initramfs : # zcat /boot/initrd.img-2.6.26-2-xen-amd64 |cpio --list |grep acpi 43293 blocks lib/modules/2.6.26-2-xen-amd64/kernel/drivers/acpi lib/modules/2.6.26-2-xen-amd64/kernel/drivers/acpi/fan.ko lib/modules/2.6.26-2-xen-amd64/kernel/drivers/acpi/thermal.ko lib/modules/2.6.26-2-xen-amd64/kernel/drivers/acpi/processor.ko lib/modules/2.6.26-2-xen-amd64/kernel/drivers/acpi/dock.ko We do not want to hack the initramfs so we leave these warning (no impacts). Todo/issues : - Linux UUID : Universal Unique IDentifier will be the same for all your VMs ! We are dealing with OS uuid not XS uuid : https://help.ubuntu.com/community/UsingUUID Is it a potential issue ? Do we need to assign new uuid to each VM... ? - Ubuntu 9.04 templates use a 4GB vdisk for / and 0,5GB for swap, we have also added a firstboot script to change hostname and accounts passwords. - Ubuntu 8.04 templates use a single 8GB vdisk and have no firstboot script, root and alyseo accounts passwords are : Alyseo Maybe we will redesign them like we did for the 9.04 templates, let us know if you think it will be of use ? - Ubuntu 8.04 use the xen distro kernel but it not provided anymore on 9.04, so we used a xen debian kernel for ubuntu 9.04 : http://ftp.de.debian.org/debian/pool/main/l/linux-2.6/ - Will be nice to add network setting... in the /etc/init.d/firstboot script : Anyone would like to contribute ? - No pinning on kernel upgrades : which mean you really need to double check you grub config... after each kernel upgrades or your VM may not boot anymore ! If it happen, please use the xe-edit-bootloader CLI command. But we always recommend you to do a test on a backup VM first (or use snapshots on XS5.5). - Ubuntu and pygrub issues : again always edit /boot/grub/menu.lst after each kernel upgrade. Due to an ubuntu bug, grub config need to be manage by hand. - You can not resize the initial vdisks but you can create new vdisks after VM installation and use them as you would like. If you know any workaround on this point then just let us know ;-) *** UPDATE : see contribs below. - VNC is not setup on all our VMs, and it is not on our todo list : we used to work with ssh ;-) Contribs : --------- 1/ Thanks to Blindheim Christoffer for message below : On ven, 2009-06-19 at 16:02 +0200, Blindheim Christoffer wrote: > You wanted to know how you tune the size of a disk in ubuntu running on xenserver: > swapoff /dev/xvda5 > > fdisk /dev/xvda > remove all partition > recreate new primary, starting point 1 end point to the suggested value subtracted 51 (area for swap space) > create extended and logical on the left space. > Change type on the partition number 5 to type 83 (linux swap) > toggle the boot flag on partition 1 > write and exit fsdisk > > reboot if kernel is still using the old table. > > type following to extend filesystem > resize2fs /dev/xvda1 > > recreate swap area: > mkswap /dev/xvda5 > swapon /dev/xvda5 > record the new UUID of swap area in /etc/fstab > > reboot and your done... fsck is going to complain, but it will fix it all... > > -- > Btw, I'm running version 5.5 of xenserver, and I had to update the location of > CDROM on 8.04 template to /dev/xvdd in /etc/fstab to install the newer xe-tools. > > -- > Christoffer Blindheim > JBV OPM Misc : ----- Contrib made by Alyseo : http://www.alyseo.com/ http://www.coraid.fr/ If you like this contribution, you can contract us or purchase your licenses and Storage goods from us ;-) sales [AT] alyseo.com For support, question... please email to : support [AT] alyseo.com