Tag: debugging
On Internet Explorer 11 Endpoint Analysis Plugin Fails to Run on NetScaler Gateway Virtual Server and User is prompted to “Download” or “Skip Check”
The Endpoint Analysis (EPA) plugin fails on NetScaler Gateway virtual server, when using Internet Explorer 11 (IE 11) with Microsoft hotfix KB3025390 installed.
After installation of the Microsoft hotfix, you will be directed to a page where you can either “Download” the plugin or “Skip Check” in some builds. The EPA plugin does not run as expected.
Related:
Lifecycle Maintenance Hotfixes – Definitions and Examples
In some instances, hotfixes might be superseded or replaced. This happens only when a subsequent hotfix includes all fixes from the earlier hotfixes, as explained in the following section.
Note: The information in this document applies primarily to the XenApp and the XenDesktop products, but might be extended to other Citrix products as well.
Access to Hotfixes
Hotfixes are available for download from the Citrix Knowledge Center. The access provided to these hotfixes is based on expected customer impact, as mentioned in the following table:
Hotfix Type |
Expected Customer Impact |
Access |
General Release |
Affects a wide customer base |
All customers |
Limited Release |
Affects a smaller number of customers |
Customers with Priority and/or Priority Plus Offering Level, Technical Relationship Manager,CTPs, and Partners |
Hotfix Replacement and Supersedence
Any hotfix that includes all fixes from an earlier hotfix either supersedes or replaces the original hotfix, as mentioned in the following table:
Original Hotfix Type |
Subsequent Hotfix Type |
Status of Original Hotfix |
Rationale |
Limited Release |
General Release |
Superseded hotfix is no longer available |
All customers can access the subsequent hotfix |
Limited Release |
Limited Release |
Superseded hotfix is no longer available |
Customers with access to the original hotfix can also access the subsequent hotfix |
General Release |
General Release |
Superseded hotfix is no longer available |
All customers can access the subsequent hotfix |
General Release |
Limited Release |
Replaced, but remains available for download from the Citrix Knowledge Center |
Original hotfix remains available for customers who cannot access the Limited Release hotfix |
Note: The terms superseded and replaced, as used in this article and on the Citrix Knowledge Center, are used to illustrate the difference between release types. They are not used in the same manner as Microsoft, Windows Installer, however Citrix hotfix readmes use the same terms.
The following table provides an examples of original hotfixes and their status:
Original Hotfix | Subsequent Hotfix | Status | Rationale |
Limited Release Hotfix A is available for download to customers with Subscription Advantage and a My Citrix account | General Release Hotfix B is released. It contains all fixes from Hotfix A, plus new fixes | Hotfix B supersedes Hotfix A | Hotfix A is no longer available for download because Hotfix B is available to all customers |
General Release Hotfix C is available for download from the Knowledge Center to all customers | Limited Release Hotfix D is released. It contains all fixes from Hotfix C, plus new fixes | Hotfix D replaces Hotfix C | Both remain available for download because Hotfix D is available only to customers with Subscription Advantage and a My Citrix account |
Limited Release Hotfix E is available for download to customers with Subscription Advantage and a My Citrix account | Limited Release Hotfix F is released. It contains fixes, but does not contain all fixes from Hotfix E | The status of Hotfix E is unchanged; Hotfix F is offered as a separate, additional hotfix | Both are available for download because Hotfix F does not contain all of the fixes from Hotfix E |
Related:
Hotfix XS81E001 – For Citrix Hypervisor 8.1
Who Should Install This Hotfix?
This is a hotfix for customers running Citrix Hypervisor 8.1.
Note: Ensure that you use XenCenter 8.1.2 or later to install this hotfix. The latest version of XenCenter is available from the Citrix Hypervisor Download site.
Information About this Hotfix
Component | Details |
---|---|
Prerequisite | None |
Post-update tasks* | Restart Host |
Content live patchable** | Yes |
Baselines for Live Patch | Citrix Hypervisor 8.1 |
Revision History |
Published on Feb 13, 2020 |
** Available to Enterprise Customers. |
Issues Resolved In This Hotfix
This hotfix resolves the following issues:
- When running Reclaim Space on a thinly provisioned LUN with more than 2 TB of free space, the operation fails with an ioctl not supported error.
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. Click the following link to download the source code for any modified open source components XS81E001-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.
Installing the Hotfix by using XenCenter
Choose an Installation Mechanism
There are three mechanisms to install a hotfix:
- Automated Updates
- Download update from Citrix
- 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:
- Download the hotfix to a known location on a computer that has XenCenter installed.
- Unzip the hotfix zip file and extract the .iso file
- In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
- Read the information displayed on the Before You Start page and click Next to start the wizard.
- Click Browse to locate the iso file, select XS81E001.iso and then click Open.
- Click Next.
- Select the pool or hosts you wish to apply the hotfix to, and then click Next.
- 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.
- Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
- 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.
- When the update is applied, click Finish to close the wizard.
- If you chose to carry out the post-update tasks, do so now.
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.
Installing the Hotfix by using the xe Command Line Interface
- Download the hotfix file to a known location.
- Extract the .iso file from the zip.
- 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>XS81E001.iso
Citrix Hypervisor assigns the update file a UUID which this command prints. Note the UUID.
04ffe352-3f45-4a2d-bc79-e3f2f13b6d79
- Apply the update to all hosts in the pool, specifying the UUID of the update:
xe update-pool-apply uuid=04ffe352-3f45-4a2d-bc79-e3f2f13b6d79
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=04ffe352-3f45-4a2d-bc79-e3f2f13b6d79
- Verify that the update was applied by using the update-list command.
xe update-list -s <server> -u root -pw <password> name-label=XS81E001
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.
- If the hotfix is applied successfully, restart each host in the pool, starting with the master.
- 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=04ffe352-3f45-4a2d-bc79-e3f2f13b6d79
Files
Hotfix File
Component | Details |
---|---|
Hotfix Filename | XS81E001.iso |
Hotfix File sha256 | 9f1eca3c219c03fd002ebd61ea982e8d826c7e903b07761506f1eac13694188d |
Hotfix Source Filename | XS81E001-sources.iso |
Hotfix Source File sha256 | 70b055290c0009f069a7eb7329fe084da1958e8e1e56d624cf36fbb7f82cfffa |
Hotfix Zip Filename | XS81E001.zip |
Hotfix Zip File sha256 | db7280bd8f791c91d0d2839e1d04f50f2887e2c26f48eb1cbedeb66b930c718f |
Size of the Zip file | 31.51 MB |
Files Updated
kernel-4.19.19-6.0.10.x86_64.rpm |
kernel-livepatch_4.19.19_6.0.9-1-1.x86_64.rpm |
More Information
For more information, see Citrix Hypervisor Documentation.
If you experience any difficulties, contact Citrix Technical Support.
Related:
Hotfix XS80E003 – For Citrix Hypervisor 8.0
Who Should Install This Hotfix?
This is a hotfix for customers running Citrix Hypervisor 8.0.
Information About this Hotfix
Component | Details |
---|---|
Prerequisite | None |
Post-update tasks* | Restart Host |
Content live patchable** | No |
Baselines for Live Patch | N/A |
Revision History |
Published on Jul 24, 2019 |
** Available to Enterprise Customers. |
Issues Resolved In This Hotfix
This hotfix resolves the following issues:
- After live migration, a Windows VM can hang for over a minute.
- If you run your Windows VMs with the viridian_reference_tsc flag enabled, the VM might crash during migration.
This hotfix also allows for the following improvement:
- You can now increase the performance of Windows VMs by enabling the viridian_reference_tsc and viridian_stimer flags.
Any new VMs created after you install this hotfix have these flags enabled by default and benefit from the performance improvement. To get the benefit of the improved performance in your existing VMs, complete the steps in the After installing this hotfix section of this article.
This hotfix also includes the following previously released hotfixes:
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. Click the following link to download the source code for any modified open source components XS80E003-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.
Installing the Hotfix by using XenCenter
Choose an Installation Mechanism
There are three mechanisms to install a hotfix:
- Automated Updates
- Download update from Citrix
- 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:
- Download the hotfix to a known location on a computer that has XenCenter installed.
- Unzip the hotfix zip file and extract the .iso file
- In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
- Read the information displayed on the Before You Start page and click Next to start the wizard.
- Click Browse to locate the iso file, select XS80E003.iso and then click Open.
- Click Next.
- Select the pool or hosts you wish to apply the hotfix to, and then click Next.
- 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.
- Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
- 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.
- When the update is applied, click Finish to close the wizard.
- If you chose to carry out the post-update tasks, do so now.
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.
Installing the Hotfix by using the xe Command Line Interface
- Download the hotfix file to a known location.
- Extract the .iso file from the zip.
- 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>XS80E003.iso
Citrix Hypervisor assigns the update file a UUID which this command prints. Note the UUID.
b99a5e83-e335-431a-a1d1-10e222bc4bfa
- Apply the update to all hosts in the pool, specifying the UUID of the update:
xe update-pool-apply uuid=b99a5e83-e335-431a-a1d1-10e222bc4bfa
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=b99a5e83-e335-431a-a1d1-10e222bc4bfa
- Verify that the update was applied by using the update-list command.
xe update-list -s <server> -u root -pw <password> name-label=XS80E003
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.
- If the hotfix is applied successfully, restart each host in the pool, starting with the master.
- 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=b99a5e83-e335-431a-a1d1-10e222bc4bfa
After installing this hotfix
This hotfix includes updates to VM templates. These updates automatically apply to any VMs you create after applying the hotfix. To apply the updates to your existing Windows VMs and benefit from the performance improvements provided in this hotfix, complete the following steps:
- List all VMs that use viridian:
xe vm-list platform:viridian=true –minimal
- For each of the VMs that you want to update:
- Refer to the viridian flags in the updated template for the VM. For example:
xe template-list name-label=’Windows 7 (64-bit)’ params=platform
- Update the viridian flags in the platform field to match the updated template. For example:
xe vm-param-set uuid=<vm-uuid> platform:viridian=true platform:viridian_time_ref_count=true platform:viridian_reference_tsc=true platform:viridian_apic_assist=true platform:viridian_crash_ctl=true platform:viridian_stimer=true
Note: Only the viridian_reference_tsc and viridian_stimer flags are required to benefit from the performance improvements in this hotfix, but we advise that you set all available viridian flags.
- Shut down the VM.
Do not restart the VM. The restart function does not apply these updates. Ensure that you fully shut down your VM.
If you do not shut down your VM, you can introduce inconsistency in your viridian flags. This inconsistency can prevent you from applying further hotfixes to the Citrix Hypervisor server that hosts this VM or updating the Citrix Hypervisor server that hosts this VM to a later version.
- Start the VM.
- Refer to the viridian flags in the updated template for the VM. For example:
Note: You can update all VMs that use viridian with a single command:
xe vm-list platform:viridian=true –minimal | tr , ‘n’ | xargs -n 1 -I {} xe vm-param-set uuid={} platform:viridian=true platform:viridian_time_ref_count=true platform:viridian_reference_tsc=true platform:viridian_apic_assist=true platform:viridian_crash_ctl=true platform:viridian_stimer=true
Only use this command if you want to update all of your VMs. You must shut down and start the VMs again for the updates to take effect.
This process does not update the snapshots associated with these VMs. Do not attempt to update existing snapshots. Instead create a new snapshot from your updated VM.
If you use your VMs with Citrix Virtual Apps and Desktops Machine Creation Services or Citrix Provisioning, ensure that you update your golden images.
Files
Hotfix File
Component | Details |
---|---|
Hotfix Filename | XS80E003.iso |
Hotfix File sha256 | c0f0454c1b1bfda741d391851d02f28570cbda9498893e0c8767c0e6c4198981 |
Hotfix Source Filename | XS80E003-sources.iso |
Hotfix Source File sha256 | 22a9c553d27ad01acf7efc80266497eae4959d5c99fc80250064516742a1b44a |
Hotfix Zip Filename | XS80E003.zip |
Hotfix Zip File sha256 | d14b96615b96ac7aa7ca42e2fc5b98c953d2cffb150910e88ef27da51af8b48f |
Size of the Zip file | 7.85 MB |
Files Updated
guest-templates-json-1.7.21-1.noarch.rpm |
guest-templates-json-data-linux-1.7.21-1.noarch.rpm |
guest-templates-json-data-other-1.7.21-1.noarch.rpm |
guest-templates-json-data-windows-1.7.21-1.noarch.rpm |
guest-templates-json-data-xenapp-1.7.21-1.noarch.rpm |
microcode_ctl-2.1-26.xs5.x86_64.rpm |
xen-dom0-libs-4.11.1-7.4.x86_64.rpm |
xen-dom0-tools-4.11.1-7.4.x86_64.rpm |
xen-hypervisor-4.11.1-7.4.x86_64.rpm |
xen-libs-4.11.1-7.4.x86_64.rpm |
xen-tools-4.11.1-7.4.x86_64.rpm |
More Information
For more information, see Citrix Hypervisor Documentation.
If you experience any difficulties, contact Citrix Technical Support.
Related:
External logging in SEPM with Failover configuration
My company has two SEPMs and we’re trying to configure External Logging. We have the primary SEPM configured to export logs to a dump file and our SIEM agent is ingesting the logs in the dump files. As long as the SEMP in datacenter a is active it writes logs to the *.tmp files in the dump directory. If the SEPM in datacenter b becomes active, it does not write logs to the *.tmp files in the dump directory. How do we make sure that whichever SEMP is active write *.tmp files in the dump directory(C:Program Files (x86)SymantecSymantec Endpoint Protection Managerdatadump)?
Related:
Hotfix XS71ECU2026 – For Xenserver 7.1 Cumulative Update 2
Who Should Install This Hotfix?
This is a hotfix for customers running XenServer 7.1 Cumulative Update 2.
All customers who are affected by the issues described in CTX266932 – Citrix Hypervisor Multiple Security Updates should install this hotfix.
Note: This hotfix is available only to customers on the Customer Success Services program.
Information About this Hotfix
Component | Details |
---|---|
Prerequisite | None |
Post-update tasks | Restart Host |
Content live patchable** | No |
Baselines for Live Patch | N/A |
Revision History |
Published on Dec 11, 2019 |
** Available to Enterprise Customers. |
Issues Resolved In This Hotfix
This security hotfix addresses the vulnerabilities as described in the Security Bulletin above. In addition, it resolves the following issues:
- On some hardware, UEFI-booted XenServer hosts can crash on reboot.
This hotfix also includes the following previously released hotfixes:
- CTX246443 – Hotfix XS71ECU2002 – For XenServer 7.1 Cumulative Update 2
- CTX250039 – Hotfix XS71ECU2008 – For XenServer 7.1 Cumulative Update 2
- CTX258418 – Hotfix XS71ECU2014 – For XenServer 7.1 Cumulative Update 2
- CTX262553 – Hotfix XS71ECU2021 – For XenServer 7.1 Cumulative Update 2
- CTX263661 – Hotfix XS71ECU2024 – For XenServer 7.1 Cumulative Update 2
Installing the Hotfix
Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. 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. Click the following link to download the source code for any modified open source components XS71ECU2026-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.
Installing the Hotfix by using XenCenter
Choose an Installation Mechanism
There are three mechanisms to install a hotfix:
- Automated Updates
- Download update from Citrix
- Select update or Supplemental pack from disk
The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the XenServer documentation.
For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the XenServer documentation.
The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:
- Download the hotfix to a known location on a computer that has XenCenter installed.
- Unzip the hotfix zip file and extract the .iso file
- In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
- Read the information displayed on the Before You Start page and click Next to start the wizard.
- Click Browse to locate the iso file, select XS71ECU2026.iso and then click Open.
- Click Next.
- Select the pool or hosts you wish to apply the hotfix to, and then click Next.
- 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.
- Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
- 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.
- When the update is applied, click Finish to close the wizard.
- If you chose to carry out the post-update tasks, do so now.
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.
Installing the Hotfix by using the xe Command Line Interface
- Download the hotfix file to a known location.
- Extract the .iso file from the zip.
- 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>XS71ECU2026.iso
XenServer assigns the update file a UUID which this command prints. Note the UUID.
3cc6c3d6-b591-4931-9c1f-d6e4a8c21ae1
- Apply the update to all hosts in the pool, specifying the UUID of the update:
xe update-pool-apply uuid=3cc6c3d6-b591-4931-9c1f-d6e4a8c21ae1
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=3cc6c3d6-b591-4931-9c1f-d6e4a8c21ae1
- Verify that the update was applied by using the update-list command.
xe update-list -s <server> -u root -pw <password> name-label=XS71ECU2026
If 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.
- If the hotfix is applied successfully, restart each host in the pool, starting with the master.
- 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=3cc6c3d6-b591-4931-9c1f-d6e4a8c21ae1
Files
Hotfix File
Component | Details |
---|---|
Hotfix Filename | XS71ECU2026.iso |
Hotfix File sha256 | aafd945cb28b3e271323445643cf6ace4a2c0d74be02e3923731be877cb00386 |
Hotfix Source Filename | XS71ECU2026-sources.iso |
Hotfix Source File sha256 | ea658476cdb0bfcea05fb4f82af60feff603704e34ce0a9cc78eb0a56e4165e8 |
Hotfix Zip Filename | XS71ECU2026.zip |
Hotfix Zip File sha256 | d72f8c0c47a785002cff1521175a91b36ef9fb6e8ca117f744ed9ac3e6b6329c |
Size of the Zip file | 7.08 MB |
Files Updated
microcode_ctl-2.1-26.xs10.x86_64.rpm |
xen-dom0-libs-4.7.6-1.32.x86_64.rpm |
xen-dom0-tools-4.7.6-1.32.x86_64.rpm |
xen-hypervisor-4.7.6-1.32.x86_64.rpm |
xen-libs-4.7.6-1.32.x86_64.rpm |
xen-tools-4.7.6-1.32.x86_64.rpm |
xenserver-status-report-1.1.1.2-313.noarch.rpm |
More Information
For more information, see XenServer Documentation.
If you experience any difficulties, contact Citrix Technical Support.
Related:
Debug invalid_request
Hello fellows,
is there any way how we can debug requests that are denied because of an invalid_request? For example to see if an header is malformed and in what way.
For HTTP connections we can of course capture the whole connection stream, but what about HTTPS connections? Is there a debug log where ProxySG is providing such information?
Related:
Hotfix XS71ECU2017 – For XenServer 7.1 Cumulative Update 2
Who Should Install This Hotfix?
This is a hotfix for customers running XenServer 7.1 Cumulative Update 2.
Note: This hotfix is available only to customers on the Customer Success Services program.
Information About this Hotfix
Component | Details |
---|---|
Prerequisite | None |
Post-update tasks | Restart Host |
Content live patchable** | No |
Baselines for Live Patch | N/A |
Revision History |
Published on Nov 28, 2019 |
** Available to Enterprise Customers. |
Issues Resolved In This Hotfix
This hotfix contains the following improvements:
- Updates to XenServer’s time information to reflect changes to Brazil’s daylight savings time policy in 2019. For more information, see https://www.timeanddate.com/news/time/brazil-scraps-dst.html
- Updates to the PCI ID database to include information about new hardware.
Additionally, this hotfix resolves the following issues:
- Logrotate can fail to run if an unexpected file exists. This unexpected file can be left behind if the logrotate operation was previously interrupted.
- On a Linux guest that has multiple vCPUs, the throughput can be much lower than expected. This issue is caused by interrupts for the VIF queues not being correctly distributed across vCPUs.
Installing the Hotfix
Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. 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. Click the following link to download the source code for any modified open source components XS71ECU2017-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.
Installing the Hotfix by using XenCenter
Choose an Installation Mechanism
There are three mechanisms to install a hotfix:
- Automated Updates
- Download update from Citrix
- Select update or Supplemental pack from disk
The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the XenServer documentation.
For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the XenServer documentation.
The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:
- Download the hotfix to a known location on a computer that has XenCenter installed.
- Unzip the hotfix zip file and extract the .iso file
- In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
- Read the information displayed on the Before You Start page and click Next to start the wizard.
- Click Browse to locate the iso file, select XS71ECU2017.iso and then click Open.
- Click Next.
- Select the pool or hosts you wish to apply the hotfix to, and then click Next.
- 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.
- Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
- 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.
- When the update is applied, click Finish to close the wizard.
- If you chose to carry out the post-update tasks, do so now.
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.
Installing the Hotfix by using the xe Command Line Interface
- Download the hotfix file to a known location.
- Extract the .iso file from the zip.
- 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>XS71ECU2017.iso
XenServer assigns the update file a UUID which this command prints. Note the UUID.
4c159e18-c568-40a0-862f-3e40c2ea225d
- Apply the update to all hosts in the pool, specifying the UUID of the update:
xe update-pool-apply uuid=4c159e18-c568-40a0-862f-3e40c2ea225d
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=4c159e18-c568-40a0-862f-3e40c2ea225d
- Verify that the update was applied by using the update-list command.
xe update-list -s <server> -u root -pw <password> name-label=XS71ECU2017
If 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.
- If the hotfix is applied successfully, restart each host in the pool, starting with the master.
- 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=4c159e18-c568-40a0-862f-3e40c2ea225d
Files
Hotfix File
Component | Details |
---|---|
Hotfix Filename | XS71ECU2017.iso |
Hotfix File sha256 | b58ab0d2e3b18bfba8f6c3412047c13684cc09a59c4920e763facb01fd918607 |
Hotfix Source Filename | XS71ECU2017-sources.iso |
Hotfix Source File sha256 | f2984e0392809532195accdb9cb13e1c5eeada90a7c8f6ec9c16796f8f68a02f |
Hotfix Zip Filename | XS71ECU2017.zip |
Hotfix Zip File sha256 | 4087375c933f725f7bd47a844e41f46fe73248ad232a1910483c504eee431fa3 |
Size of the Zip file | 1.31 MB |
Files Updated
irqbalance-1.0.7-11.el7.x86_64.rpm |
logrotate-3.8.6-17.xs1.0.0.x86_64.rpm |
tzdata-2019b-1.el7.noarch.rpm |
xenserver-hwdata-20190202-1.noarch.rpm |
More Information
For more information, see XenServer Documentation.
If you experience any difficulties, contact Citrix Technical Support.
Related:
Hotfix XS71ECU2020 – For XenServer 7.1 Cumulative Update 2
Who Should Install This Hotfix?
This is a hotfix for customers running XenServer 7.1 Cumulative Update 2.
Note: This hotfix is available only to customers on the Customer Success Services program.
Information About this Hotfix
Component | Details |
---|---|
Prerequisite | None |
Post-update tasks | None |
Content live patchable** | No |
Baselines for Live Patch | N/A |
Revision History |
Published on Nov 20, 2019 |
** Available to Enterprise Customers. |
Issues Resolved In This Hotfix
This hotfix resolves the following issues:
- Sometimes, the storage garbage collection process might run continuously, taking snapshots, coalescing them, deleting the snapshots, and then repeating on an almost permanent basis. This introduces high IOPS load for little benefit.
- When read caching is enabled it is significantly slower to read from the parent snapshot than from the leaf. This is now fixed for sequential reads.
- On HA-enabled pools, when a task is initiated after a XenServer host has failed, VMs on the host can be blocked from restarting for many hours. This issue occurs when an in-progress coalesce process is not explicitly aborted after the failure.
- All VMs on a XenServer host can experience slower read/write performance, during a VM disk copy, and up to 512 seconds after the copy finishes. The degradation of performance is caused by cache memory pressure in dom0 causing all tapdisks to incorrectly enter low memory mode.
Important: This hotfix disables low memory mode. Therefore, VMs might require more memory to be available in dom0. Before applying this hotfix, you can check whether any of your VMs are running in low memory mode by adding the “Tapdisks in Low Memory Mode” graph to the Performance tab in XenCenter. The number of VMs in low memory mode is shown on this graph. We recommended that you increase dom0 memory to make an additional ~1.4MB per VM available in dom0.
This hotfix also includes the following previously released hotfixes:
- CTX256836 – Hotfix XS71ECU2009 – For XenServer 7.1 Cumulative Update 2
- CTX262019 – Hotfix XS71ECU2019 – For XenServer 7.1 Cumulative Update 2
Installing the Hotfix
Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. 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. Click the following link to download the source code for any modified open source components XS71ECU2020-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.
Installing the Hotfix by using XenCenter
Choose an Installation Mechanism
There are three mechanisms to install a hotfix:
- Automated Updates
- Download update from Citrix
- Select update or Supplemental pack from disk
The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the XenServer documentation.
For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the XenServer documentation.
The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:
- Download the hotfix to a known location on a computer that has XenCenter installed.
- Unzip the hotfix zip file and extract the .iso file
- In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
- Read the information displayed on the Before You Start page and click Next to start the wizard.
- Click Browse to locate the iso file, select XS71ECU2020.iso and then click Open.
- Click Next.
- Select the pool or hosts you wish to apply the hotfix to, and then click Next.
- 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.
- Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
- 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.
- When the update is applied, click Finish to close the wizard.
- If you chose to carry out the post-update tasks, do so now.
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.
Installing the Hotfix by using the xe Command Line Interface
- Download the hotfix file to a known location.
- Extract the .iso file from the zip.
- 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>XS71ECU2020.iso
XenServer assigns the update file a UUID which this command prints. Note the UUID.
52a16dea-740a-4a39-8a5e-8b71d617f13d
- Apply the update to all hosts in the pool, specifying the UUID of the update:
xe update-pool-apply uuid=52a16dea-740a-4a39-8a5e-8b71d617f13d
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=52a16dea-740a-4a39-8a5e-8b71d617f13d
- Verify that the update was applied by using the update-list command.
xe update-list -s <server> -u root -pw <password> name-label=XS71ECU2020
If 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.
- 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=52a16dea-740a-4a39-8a5e-8b71d617f13d
Files
Hotfix File
Component | Details |
---|---|
Hotfix Filename | XS71ECU2020.iso |
Hotfix File sha256 | f9d5b0aad2cd089a4ae7340852704b9008cafca30f0c4a5f45efe40e2d06c83f |
Hotfix Source Filename | XS71ECU2020-sources.iso |
Hotfix Source File sha256 | a772d8816e6bb2cb14fba178c36a5df8fef4bb8fbd8a0b914d937ebf16bb042c |
Hotfix Zip Filename | XS71ECU2020.zip |
Hotfix Zip File sha256 | 5fbcd65dd92c6a93164e7b47418b382ce23d9f92483284bc84aa8886645b9cfe |
Size of the Zip file | 1.24 MB |
Files Updated
blktap-3.5.0-xs.2+1.0_71.2.6.x86_64.rpm |
sm-1.17.0-xs.2+1.0_71.2.4.x86_64.rpm |
sm-rawhba-1.17.0-xs.2+1.0_71.2.4.x86_64.rpm |
More Information
For more information, see XenServer Documentation.
If you experience any difficulties, contact Citrix Technical Support.