I personally ran into some issues after my 1st XenClient two installation when I tried to install my existing Ubuntu VM i’ve created with the TechPreview code.

So I thought I’m sharing my experience, so it might save you some time….

Ubuntu and XenClient 2

  • Designed to work with Ubuntu 11.04 32Bit
  • Experimental as for version 2.0
  • XenClient Tools on the XC-Tools CD/ISO contain the following debian packages
    • /xenclient-linuxtools.deb (for actual 2.6.38 Kernel)
    • /ubuntu-drivers/2.6.32/xenclient-linuxtools_i386.deb
    • /ubuntu-drivers/2.6.37/xenclient-linuxtools_i386.deb
  • XenClient Tools for Ubuntu DONT provide a “Switcher Toolbar”
  • XenCleint Tools for Ubunto DONT provide “Secure Application Sharing”

One of the primary functions of the tools for Linux is to allow the hypervisor to control certain power management functions. Most obvious one is to make sure the VM is properly shutting down in case the hypervisor is shut down. Also includes  the functionality to configure what should happen to the VM’s if the user is closing the lid on a Notebook without shutting down.

What’s in the debian package

The XenClient tools for Ubuntu are delivered as source code and because they’re implemented as dynamic kernel modules the installer has a dependency on kernel versions, kernel headers c compiler e.g.

This is a list of dependencies:

  • linux-virtual
  • dkms
  • libc6
  • autoconf
  • gcc
  • libtool
  • zlib1g-dv
  • libx11-dev

The binaries being compiled and installed:

  • libv4v
  • rpc-agent
  • v4v-dkms
  • xblanker
  • xenbus
  • xenmou

The rpc-agent and the xblanker will be controlled with the linux init process and /etc/init.d holds the scripts.

The lsmod lists the kernel modules and unleashes the loaded modules form the XenClient tools.

How NOT to install the tools

First of all don’t expect that a VM with the XenClient tools from the TechPreview will work at all.
If you really want to reuse that VM consider to dpkg –remove the old XenClient tools.

Also DON’T install the XenClient Tools with ipkg or apt

This will be hard to resolve dependencies and by default lead into a failed installation. Additionally if the system is rebooted after the installation filesystem mounts may not work and you end up with ashell.

The way it works is easy!

Took me along time to figure, but just keep it simple 🙂

Do everything without using a CLI – Use Gnome / Nautilus and keep PATIONED.

  • Install Ubuntu from ubuntu-11.04-desktop-i386
  • Login and use the Update Manager to update the OS

  • Reboot the VM
  • Open the CDROM icon on the desktop and double click on the debian package

  • You’ll need to authenticate
  • Observe the progress until you notice the package has been installed
    (In my case it took around 15 Minutes, to resolve dependencies, compile and install the packages)

  • Once your done reboot the VM
  • Switch to the Citrix Receiver for XenClient and verify the tools are installed (Tools CD)
    (Hardware -> Edit)


As usual, excuse typos and my typical glitches in grammar….

IMPORTANT: If you didn’t sign up for Summit / Synergy Barcelona it’s about time!
We offer great sessions and hands on labs for XenClient  check for the Synergy page here.

ENJOY your work with XenClient and please note: We appreciate your feedback, use the XenClient forums or shot me a message walter.hofstetter[at]