Hotfix XS61E069 - For XenServer 6.1.0

Who Should Install This Hotfix?

This is a hotfix for customers running Citrix XenServer 6.1.0. All customers who are affected by the issues described in??CTX209443: Citrix XenServer Multiple Security Updates??should install this hotfix.

IMPORTANT:

• Any issued driver disk and the Driver Development Kit (DDK) for XenServer 6.1.0, must be updated to be compatible with this hotfix. See??CTX204201 - Driver Disks for XenServer 6.1.0 with XS61E064??for a list of the affected driver disks that must be updated. See??CTX204205??for DDK information.
• After applying the hotfix to all hosts in a pool, customers should update the required driver disks??before??rebooting the XenServer hosts.

Issues Resolved in This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above. In addition, it resolves the following issues:

• After installing the hotfix XS61E060, certain security programs or debuggers can cause Windows VMs to reboot on Intel hardware.
• After installing the hotfix XS61E065, in scenarios where a XenServer host handles numerous concurrent connections and requests from XenAPI clients (including XenCenter and other hosts in the pool), the service that handles the incoming connections can crash. This causes the XenAPI clients to lose connection to the XenServer host. Perform the following steps to recover the connection, prior to installing this hotfix:
  1. Connect to the control domain (dom0). You can use either SSH, or serial console, or use the physical keyboard-and-monitor.
  2. Run the command??xe-toolstack-restart.

This hotfix also includes the following previously released hotfixes:

• CTX135596 - Hotfix XS61E003 - For XenServer 6.1.0
• CTX135469 - Hotfix XS61E004 - For XenServer 6.1.0
• CTX135709 - Hotfix XS61E006 - For XenServer 6.1.0
• CTX136252 - Hotfix XS61E009 - For XenServer 6.1.0
• CTX136674 - Hotfix XS61E012 - For XenServer 6.1.0
• CTX136482 - Hotfix XS61E013 - For XenServer 6.1.0
• CTX136483 - Hotfix XS61E014 - For XenServer 6.1.0
• CTX137168 - Hotfix XS61E017 - For XenServer 6.1.0
• CTX137645 - Hotfix XS61E018 - For XenServer 6.1.0
• CTX137487 - Hotfix XS61E019 - For XenServer 6.1.0
• CTX137843 - Hotfix XS61E020 - For XenServer 6.1.0
• CTX137675 - Hotfix XS61E022 - For XenServer 6.1.0
• CTX138038 - Hotfix XS61E024 - For XenServer 6.1.0
• CTX138348 - Hotfix XS61E026 - For XenServer 6.1.0
• CTX138749 - Hotfix XS61E027 - For XenServer 6.1.0
• CTX138610 - Hotfix XS61E028 - For XenServer 6.1.0
• CTX138731 - Hotfix XS61E030 - For XenServer 6.1.0
• CTX139353 - Hotfix XS61E032 - For XenServer 6.1.0
• CTX139307 - Hotfix XS61E033 - For XenServer 6.1.0
• CTX140242 - Hotfix XS61E035 - For XenServer 6.1.0
• CTX140053 - Hotfix XS61E036 - For XenServer 6.1.0
• CTX140724 - Hotfix XS61E037 - For XenServer 6.1.0
• CTX140774 - Hotfix XS61E039 - For XenServer 6.1.0
• CTX141038 - Hotfix XS61E041 - For XenServer 6.1.0
• CTX141479 - Hotfix XS61E043 - For XenServer 6.1.0
• CTX141718 - Hotfix XS61E045 - For XenServer 6.1.0
• CTX141778 - Hotfix XS61E046 - For XenServer 6.1.0
• CTX142145 - Hotfix XS61E050 - For XenServer 6.1.0
• CTX142271 - Hotfix XS61E051 - For XenServer 6.1.0
• CTX142480 - Hotfix XS61E052 - For XenServer 6.1.0
• CTX142535 - Hotfix XS61E054 - For XenServer 6.1.0
• CTX202162 - Hotfix XS61E055 - For XenServer 6.1.0
• CTX201575 - Hotfix XS61E056 - For XenServer 6.1.0
• CTX201634 - Hotfix XS61E057 - For XenServer 6.1.0
• CTX201738 - Hotfix XS61E058 - For XenServer 6.1.0
• CTX202436 - Hotfix XS61E059 - For XenServer 6.1.0
• CTX202615 - Hotfix XS61E060 - For XenServer 6.1.0
• CTX203491 - Hotfix XS61E061 - For XenServer 6.1.0
• CTX204045 - Hotfix XS61E063 - For XenServer 6.1.0
• CTX204051 - Hotfix XS61E064 - For XenServer 6.1.0
• CTX205226 - Hotfix XS61E065 - For XenServer 6.1.0
• CTX205353 - Hotfix XS61E066 - For XenServer 6.1.0
• CTX206527 - Hotfix XS61E067 - For XenServer 6.1.0
• CTX208511 - Hotfix XS61E068 - For XenServer 6.1.0

Installing the Hotfix

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to install this update. Once the update is installed, the server must be restarted for the changes to take effect. As with any software update, back up your data before applying this hotfix. Citrix recommends updating all hosts within a pool sequentially. Updating of hosts should be scheduled to minimize the amount of time the pool runs in a "mixed state" where some hosts are updated and some have not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

NOTE:??The attachment to this article is a zip file. It contains both the hotfix update package and the source code for any modified open source components. The source code is not necessary for hotfix installation: it is provided to fulfil licensing obligations.

Installing the update using XenCenter

1. Download the update to a known location on a computer where XenCenter is also installed.
2. In XenCenter, on the??Tools??menu, select??Install New Update. The Install Update wizard appears.
3. Click??Next??to start the Wizard.
4. Click??Add??to upload the update.
5. Browse to the location where you downloaded the hotfix, select it, and then click??Open.
6. From the list of updates select??XS61E069.xsupdate??and then click??Next.
7. Select the hosts you wish to apply the hotfix to, and then click??Next.
8. Follow the recommendations to resolve any upgrade prechecks and then click??Next.
9. Choose how to perform post-update tasks. In the??Post update options??section, select??automatically??or??manually, and then click??Install update.
10. When the installation process is complete, click??Finish??to exit the wizard.

NOTES:

• If you select??manually??to perform the post-update tasks, you must ensure to do so after installing the hotfix.
• If you select??automatically??to perform the post-update tasks, the XenCenter controlled upgrade process restarts each host sequentially starting with the Pool Master, where possible VMs are migrated to other running hosts to avoid VM downtime. When restarting the Pool Master, XenCenter cannot monitor the pool.

Installing the update by using the xe Command Line Interface

1. Download the update file to a known location.
2. Extract the xsupdate file from the zip.
3. Upload the xsupdate file to the Pool Master by entering the following commands:??
   (Where??hostname??is the Pool Master's IP address or DNS name.)
   

   xe patch-upload -s??<hostname>??-u root -pw??<password>??file-name=<path_to_update_file>\XS61E069.xsupdate

   XenServer assigns the update file a UUID which this command prints. Note the UUID.

   9c068089-3049-46a9-b1be-f9533118267c

4. Apply the hotfix to all hosts in the pool, specifying the UUID of the hotfix:

   xe -s??<hostname>??-u root -pw??<password>??patch-pool-apply uuid=9c068089-3049-46a9-b1be-f9533118267c

5. Verify that the update was applied by using the??patch-list??command.

   xe patch-list -s??<hostname>??-u root -pw??<password>??name-label=XS61E069

   If the update is successful, the??hosts??field contains the UUIDs of the hosts this patch was successfully applied to. This should be a complete list of all hosts in the pool.
6. To verify in XenCenter that the update has been applied correctly, select the Pool, and then click the??General??tab. This displays the Pool properties. In the??Updates??section, ensure that the update is listed as??Applied.
7. The hotfix is applied to all hosts in the pool, but it will not take effect until each host has been rebooted. For each host, migrate the VMs that you wish to keep running, and shut down the remaining VMs before rebooting the host.

Files

Hotfix File

Files Updated