Issues Resolved In This Hotfix
This hotfix resolves the following issues:
- When creating a Storage Repository (SR) or a Virtual Disk (VDI), predefined XML entities (for example &, <, >, “, ‘) entered into the Name and Description fields, are written directly into the SR metadata. Any subsequent actions such as creating an SR or a VDI will fail with an error message, as the XML parser fails to parse metadata if it contains predefined XML entities.
- If there is a failure or a change in the number of paths to storage, attempts to create or destroy a VDI on an LVM-based SR may fail and will display the following error message: Error in Metadata Volume Operation on SR. The VDI will be created, but will lack a Name or Description.
- If multipath is active, on some storage arrays an error may occur when reading the Metadata Volume during an SR attach and display the following error message: Error in Metadata Volume Operation on SR.
- Storage may take several minutes to become available when using Dell PowerVault MD32xxi Storage Arrays with LVMoiSCSI
- Xapi frequently hangs pool slaves due to exceeding the number of sessions on the Pool Master.
- An SR may fail to connect when the XenServer host is booted with one failed iSCSI path when using Hitachi or Compellent storage arrays.
- XenServer may not discover all of the available LUNS when using the wildcard IQN. This occurs when using Compellent storage arrays via iSCSI.
- Improvements to the XenCenter Update functionality; customers are correctly notified in XenCenter when new XenServer Tools are available.
In addition, this hotfix includes the following previously released hotfixes.
NOTE: Customers MUST install Hotfix XS60E001 – For XenServer 6.0 before attempting to apply this hotfix.
Installing the Hotfix
Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to install this update. Once the update has installed, the server must be restarted for it to take effect. As with any software update, please back up your data before applying this hotfix. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts have been upgraded 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.
Important: This hotfix updates the control domain (dom0) kernel version. The driver disks produced for Hotfix XS60E016 are compatible with this hotfix. For a list of the drivers and their updates, see CTX133960 – Driver Disks for XenServer Hotfix XS60E016.
Installing the update using XenCenter
- Download the update to a known location on a computer that has XenCenter installed.
- In XenCenter, on the Tools menu, select Install New Update. This displays the Install Update wizard.
- Click Nextto start the Wizard.
- Click Add…to upload a new update.
- Browse to the location where you downloaded the hotfix, select it, and then click Open.
- From the list of updates select XS60E017.update 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.
- Click Install to start the installation.
Note: The XenCenter controlled upgrade process reboots each host sequentially starting with the Pool Master, where possible VMs will be migrated to other running hosts to avoid VM downtime. When the Pool Master is being rebooted, XenCenter will be unable to monitor the pool.
You can download the fix here.