Citrix has released hotfix number 11 for XenServer 6.0.2.
This hotfix resolves the following issues:
- Attempts to read the metadata volume of an attached Storage Repository (SR) after the reboot of a multipath-enabled XenServer host, can cause an error and display the Error in Metadata volume Operation on SR error message.
- Storage may take several minutes to become available when using the Dell™ PowerVault™ MD32xxi Storage Arrays with LVMoiSCSI.
- XenServer may not discover all available LUNs when using wildcard IQN on storage arrays which do not support IQNs across multiple target portals. This occurs when using iSCSI storage arrays with multiple controllers, each managing their own LUNs.
- When booting a XenServer host, or re-attaching an iSCSI SR that contains a failed iSCSI path, the SR may fail to connect.
In addition, this hotfix also includes fixes released in CTX132823 – Hotfix XS602E001 – For XenServer 6.0.2, CTX133166 – Hotfix XS602E003 – For XenServer 6.0.2, CTX133812 – Hotfix XS602E005 – For XenServer 6.0.2 and CTX134479 – Hotfix XS602E007 – For XenServer 6.0.2. This means that you will not have to install these hotfixes before you can implement this hotfix. Only reason I see this is usefull is in a clean install of XenServer 6.0.2. In an existing environment I dare to hope you have already implemented these hotfixes by now…
Important: This hotfix updates the control domain (dom0) kernel version. The driver disks produced for Hotfix XS602E007 are compatible with this hotfix. For a list of the drivers and their updates, see CTX134481 – Driver Disks for XenServer 6.0.2 with Hotfix XS602E007.
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 XS602E011.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.
Installing the update using the off-host CLI
- Download the update to a known location on a computer that has the XenServer CLI or XenCenter installed.
- Extract the xsupdate file from the zip.
- If using Windows, start a Command Prompt and navigate to the XenCenter directory, for example:
cd C:Program filesCitrixXenCenter
- Upload the xsupdate file to the Pool Master by entering the following commands: (Where hostnameis the Pool Master’s IP address or DNS name.)
xe patch-upload -s
<hostname>
-u root -pw<password>
file-name=<path_to_update_file>
XS602E011.xsupdateXenServer assigns the update file a UUID which this command prints. Note the UUID.
843804e2-d698-4a57-93d7-ede337a92a33
- Apply the hotfix to all hosts in the pool, specifying the UUID of the hotfix:
xe patch-pool-apply uuid=
<843804e2-d698-4a57-93d7-ede337a92a33>
- Verify that the update was applied by using the patch-listcommand.
xe patch-list -s
<hostname>
-u root -pw<password>
name-label=XS602E011If the update has been successful, the hostsfield will contain the UUIDs of the hosts this patch was successfully applied to. This should be a complete list of all hosts in the pool.
- 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 shutdown the remaining VMs before rebooting the host.
- 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 Fully applied.
You can download the hotfix here from the Citrix Knowledge Center.