Who Should Install This Hotfix?

This is a hotfix for customers running Citrix Hypervisor 8.2.

Information About this Hotfix

Improvements Included In This Hotfix

This hotfix includes the following improvements:

• VDI copy is now prevented on VDIs that have reset-on-boot enabled. This restriction prevents the VDI from being wiped.
• Improved checking and notifications for VMs whose vGPU configuration does not support VM suspend or migrate.
• Improvements to the HA timeout behavior to make it more resilient in cases of network congestion.

Issues Resolved In This Hotfix

This hotfix resolves the following issues:

• After upgrading to Citrix Hypervisor 8.2, you cannot revert a VM to a snapshot that was taken on the earlier version of Citrix Hypervisor.
• If, during the shutdown of a VM, you trigger a forced reboot, this can cause the VM to get into a bad power state.
• When allocating more than one VDI to an SR, the performance metrics might show incorrect latency values.
• After a VM migration fails, sometimes the VM cannot be shutdown.
• Hotplugging a VIF or VBD can intermittently fail.
• In the Citrix Hypervisor 8.2 Java SDK, a Types.InternalError exception is thrown by the Message.getSince() method when it is given valid input. This is a change in behavior from previous versions of the SDK.
• When installing a certificate on your Citrix Hypervisor server, its private key might be incorrectly rejected. This behavior is caused by overly strict cryptographic checking.
• Alerts about certificate validity might sometimes be deleted and replaced by an almost identical alert that has a different UUID.
• In some cases, the certificate checking process can send daily email notifications to the system administrator from pool member servers with the message: "Not checking certificate expiration for alerts, this is not a master host".

This hotfix also includes the following previously released hotfixes:

• CTX285938 - Hotfix XS82E002 - For Citrix Hypervisor 8.2
• CTX286800 - Hotfix XS82E013 - For Citrix Hypervisor 8.2

Installing the Hotfix

Customers should use either XenCenter or the Citrix Hypervisor Command Line Interface (CLI) to apply this hotfix. As with any software update, back up your data before applying this update. 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 are upgraded and some are 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 the hotfix update package only. Log in to your Citrix account and click the following link to download the source code for any modified open source components XS82E020-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations. You must be logged in to access this link.

Installing the Hotfix by using XenCenter

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

1. Automated Updates
2. Download update from Citrix
3. Select update or Supplemental pack from disk

The Automated Updates feature is available for Citrix Hypervisor Premium Edition customers, or to those who have access to XenServer through their Citrix Virtual Apps and Desktops entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the Citrix Hypervisor documentation.

For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the Citrix Hypervisor documentation.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

1. Download the hotfix to a known location on a computer that has XenCenter installed.
2. Unzip the hotfix zip file and extract the .iso file
3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
4. Read the information displayed on the Before You Start page and click Next to start the wizard.
5. Click Browse to locate the iso file, select XS82E020.iso and then click Open.
6. Click Next.
7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
9. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
10. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
11. When the update is applied, click Finish to close the wizard.
12. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

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

   xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>\XS82E020.iso

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

   0f965483-3171-4a8b-b669-b8d76868c39e

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

   xe update-pool-apply uuid=0f965483-3171-4a8b-b669-b8d76868c39e

   Alternatively, if you need to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

   xe update-apply host=<host> uuid=0f965483-3171-4a8b-b669-b8d76868c39e

    

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

   xe update-list -s <server> -u root -pw <password> name-label=XS82E020

   If the update is successful, the hosts field contains the UUIDs of the hosts to which this update was successfully applied. This should be a complete list of all hosts in the pool.
6. The hotfix is applied to all hosts in the pool, but it will not take effect until the XAPI service is restarted on all hosts. On the console of each host in the pool beginning with the master, enter the following command to restart the XAPI service:

   xe-toolstack-restart

   Note: When this command is run on the Pool Master, XenCenter loses connection to the pool. Wait for 30 seconds after losing connection, and then reconnect manually.
7. Use the update-pool-clean command to remove the update files from all hosts in the pool. This command frees up space on shared storage and does not uninstall the update.

   xe update-pool-clean uuid=0f965483-3171-4a8b-b669-b8d76868c39e

Files

Hotfix File

Files Updated

More Information

For more information, see Citrix Hypervisor Documentation.

If you experience any difficulties, contact Citrix Technical Support.