XenTools Fix for Windows VSIs Deployed from Custom Image Template

If you are having issues with the XenTools not being installed, or are having issues with your newly provisioned Windows VSI from a custom template, you may want to look into reinstalling them per the instuctions below.

When this condition occurs, the XenTools library is ignored, with the instance defaulting to using default drivers. The default drivers are functional but lack the extended support for recognizing additional disks and performing optimized IO. SoftLayer Engineers are currently working on a patch that will insure instances provisioned from templates will have access to the optimized library and full function and performance benefit.

While the permanent fix is being tested, clients who are experiencing the issue may address the issue via a reinstall of XenTools using the procedures documented below:

The below steps should be run from the virtual KVM interface, due to the disruption in the network connectivity which will occur during the process.

  1. Download the latest XenTools libraries from: http://downloads.service.softlayer.com/citrix/xen/xentools_6.2.328.zip
  2. Run the installwizard.msi 

The previous steps should result in an updated library and access to full function. In the event an error occurs during the install, the following steps can be executed to remove the invalid libraries and introduce the new levels:

The below steps should be run from the virtual KVM interface, due to the disruption in the network connectivity which will occur during the process.

1.   Log into the VSI and go to Control Panel ‐> Add/Remove Features (Programs), and uninstall these in the following order:

1.  First - Citrix XenServer Windows Guest Agent

2.  Second - Citrix XenServer VSS Provider

3.  Third - Citrix Xen Windows x64 PV Drivers

4.  Lastly - Citrix XenServer Tools Installer

2. Go back to control panel and open up Add/Remove Programs again... uh oh Citrix XenServer Tools Installer is back! No worries, this happens 99% of the time. What will need to happen now is an entry from the registry will need to be removed. Open regedit and do a search for "Xen", press F3 to find the 2nd entry which should look similar to the image below. It should also contain this entry, "Citrix XenServer Tools Installer". Delete the folder for this entry, once deleted it is time to reboot the VSI.

3.   You will need to give the VSI time to boot back up, and you may need to re-open the KVM once it has completed rebooting (this is a process that will need to be completed several times throughout this process more than likely).

4.   Go back to Control Panel -> Add/Remove Features (Programs) once more and verify the 4 entries are completely removed and no longer showing here. If anything is still here STOP! Verify everything was done correctly.

2008 / 2008 R2 - Final Steps

Now that the VSI has rebooted, you will need to run a repair on .NET Framework 4.x. This can be done from the Add/Remove Features (Programs) found in Control Panel. Simply select the installed program from the list as if you were to uninstall it and click the "Repair" option instead. Once the repair has completed you will be prompted to reboot again, go ahead with the reboot.

Now you can move on to installing XenTools, from the installer that you downloaded earlier. Please be patient this process can take up to 20 minutes to complete, so just let it do its thing (Please note the KVM access will come and go at this point, and is normal). Once it has completed, you will log in and see a notification that it has successfully completed installing.

2012 / 2012 R2 - Final Steps

Now that the VSI has rebooted, you can move on to installing XenTools, from the installer that you downloaded earlier. Please be patient this process can take up to 20 minutes to complete, so just let it do its thing. Once it has completed, you will log in and see that networking is not working. You will need to go in and reconfigure the networking, including default gateways and backend network (10.0.0.0/8) gateways.  The Network Cards should show they are Citrix PV drivers, not Realtek drivers.