Hotfix XS61E040 - For XenServer

[cicong]

This hotfix addresses the vulnerabilities as described in the Security Bulletin above. In addition, it resolves the following issues: If a virtual disk image (VDI) is not correctly detached, it can prevent subsequent VDIs from attaching, which prevents starting virtual machines (VMs). XenServer cannot probe Adaptec RAID Controllers. If XAPI restarts when running the command vdi-copy, the Storage Repository Global Catalog fails with the error EXCEPTION util.CommandException, 5. This hotfix also includes the following previously released hotfixes: CTX135410 – Hotfix XS61E001 - For XenServer 6.1.0 CTX137996 – Hotfix XS61E015 - For XenServer 6.1.0 CTX139940 – Hotfix XS61E034 - 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 Download the update to a known location on a computer where XenCenter is also installed. In XenCenter, on the Tools menu, select Install New Update. The Install Update wizard appears. Click Next to start the Wizard. Click Add to upload the update. Browse to the location where you downloaded the hotfix, select it, and then click Open. From the list of updates select XS61E040.xsupdate and then click Next. Select the hosts you wish to apply the hotfix to, and then click Next. Follow the recommendations to resolve any upgrade prechecks and then click Next. Choose how to perform post-update tasks. In the Post update options section, select automatically or manually, and then click Install update. 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 Download the update file to a known location. Extract the xsupdate file from the zip. 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 -u root -pw file-name=<path_to_update_file>\XS61E040.xsupdate XenServer assigns the update file a UUID which this command prints. Note the UUID. dee6cbf8-7c8f-4af2-9c76-5ba9479420e0 Apply the hotfix to all hosts in the pool, specifying the UUID of the hotfix: xe -s -u root -pw patch-pool-apply uuid=dee6cbf8-7c8f-4af2-9c76-5ba9479420e0 Verify that the update was applied by using the patch-list command. xe patch-list -s -u root -pw name-label=XS61E040 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. 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. 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.