Who Should Install This Hotfix?
This is a hotfix for customers running XenServer 6.2.0 Service Pack 1.
Issues Resolved In This Hotfix
This hotfix addresses the following issues:
- Initialize new elements added to the vGPU translation array so that they are not mistakenly assumed to contain cached translations. This assumption can cause the GPU to access incorrect pages in the Virtual Machine (VM), possibly leading to memory corruption.
- VMs with memory greater than 4 GB and a GPU assigned to it can have performance issues on host that does not have IOMMU snoop control.
- Starting a VM that has a vGPU assigned to it may cause XenServer to deadlock, triggering the watchdog timer and crashing the host. This happens due to incorrect locking while registering a new device emulator.
- When using a Windows DHCP server, attempts to simultaneously start the VMs can cause the VMs to use DHCP requests meant for other VMs. This can result in multiple VMs using the same IP address.
- Using PCI Pass-through, which includes GPU Pass-through and vGPU, on Intel-based servers can cause a XenServer host crash.
- Under certain circumstances, wrapping of the XenStore rings in hvmloader results in message corruption and can crash the VM. This happens if there are insufficient XenStore communication. This issue occurs only in HVM VMs.
- When migrating VMs by using Storage XenMotion, the virtual disks are not deleted.
- After Virtual Disk Image (VDI) migration, on the destination the VDI base copy is visible in XenCenter. This is especially true for File-based Storage Repositories (SRs), because there is no live leaf coalesce to subsequently hide the problem (as in the block-based SRs). This issue occurs when certain functions do not mark the base copy as hidden.
- When a hotfix backup file is already created on a XenServer host, attempts to reapply the hotfix to the host fails without an error message.
This hotfix also includes the following previously released hotfixes:
- CTX140052 –?? Hotfix XS62E014 - For XenServer 6.2.0
- CTX140051 –?? Hotfix XS62ESP1002 - For XenServer 6.2.0 Service Pack 1
- CTX140417 –?? Hotfix XS62ESP1004 - For XenServer 6.2.0 Service Pack 1
- CTX141036 –?? Hotfix XS62ESP1008 - For XenServer 6.2.0 Service Pack 1
- CTX141472 –?? Hotfix XS62ESP1011 - For XenServer 6.2.0 Service Pack 1
- CTX141480 –?? Hotfix XS62ESP1013 - For XenServer 6.2.0 Service Pack 1
- CTX141717 –?? Hotfix XS62ESP1015 - For XenServer 6.2.0 Service Pack 1
- CTX141779 –?? Hotfix XS62ESP1016 - For XenServer 6.2.0 Service Pack 1
- CTX142146 –?? Hotfix XS62ESP1019 - For XenServer 6.2.0 Service Pack 1
- CTX142272 –?? Hotfix XS62ESP1021 - For XenServer 6.2.0 Service Pack 1
- CTX142481 –?? Hotfix XS62ESP1025 - For XenServer 6.2.0 Service Pack 1
- CTX141952 –?? Hotfix XS62ESP1026 - For XenServer 6.2.0 Service Pack 1
- CTX142536 –?? Hotfix XS62ESP1027- For XenServer 6.2.0 Service Pack 1
- CTX201635 –?? Hotfix XS62ESP1030 - For XenServer 6.2.0 Service Pack 1
Installing the Hotfix
Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to install this update. When the installation is complete, restart the server for the update 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. 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 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 fulfill licensing obligations.
Installing the update by using XenCenter
- Download the update to a known location on a computer that has XenCenter installed.
- In XenCenter, on the?? Tools?? menu, select?? Install Update. The Install Update wizard appears.
- Click?? Next?? to 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?? XS62ESP1031.xsupdate?? and then click?? Next.
- Select the hosts to which you want to apply the hotfix 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.
- Customers who select to?? manually?? perform the post-update tasks, must ensure to do so after installing the hotfix.
- Customers who select to?? automatically?? perform the post-update tasks should note that XenCenter restarts each host sequentially starting with the Pool Master. Where possible, the VMs are migrated to other running hosts to avoid VM downtime. When the Pool Master is restarting, 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?? <hostname>?? -u root -pw?? <password>?? file-name=<path_to_update_file>\XS62ESP1031.xsupdateXenServer assigns the update file a UUID which this command prints. Note the UUID.
- 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=9cc012c5-7e2f-4ac7-b8da-31133c157999
- Verify that the update was applied by using the?? patch-list?? command.
xe patch-list -s?? <hostname>?? -u root -pw?? <password>?? name-label=XS62ESP1031If the update is successful, the?? hosts?? field contains the UUIDs of the hosts to which this patch was successfully applied. This should be a complete list of all hosts in the pool.
- To verify in XenCenter that the update is 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.
- The hotfix is applied to all hosts in the pool, but does not take effect until each host restarts. For each host, migrate the VMs that you wish to keep running, and shut down the remaining VMs before restarting the host.
|Hotfix File md5sum||0cd631ca2ad52073470da07c0a181e69|
|Hotfix Source Filename||XS62ESP1031-src-pkgs.tar.bz2|
|Hotfix Source File md5sum||e98ecec2365cd372e6c0dfb2fdf28e84|
|Hotfix Zip Filename||XS62ESP1031.zip|
|Hotfix Zip File md5sum||0affa96bdf15a273950d0e1c0e0a84da|