Recommended Hotfixes for XenServer 7.x

Citrix Hypervisor, formerly XenServer, is powered by the Xen Project hypervisor.

This article contains the complete set of recommended updates/hotfixes for XenServer 7.x .

For List of XenServer Tools/Management Agent/Windows Driver Updates refer toCTX235403-Updates to Management Agent – For XenServer 7.0 and later​

For XenServer 6.x hotfixes, refer to CTX138115 – Recommended Hotfixes for XenServer 6.x

XenServer 7.6 XenServer 7.5 XenServer 7.4 XenServer 7.1 CU2 XenServer 7.1 CU1 XenServer 7.0

For more information, refer to the following Knowledge Center articles

Note: Citrix recommends updating the XenServer Console before updating any new hotfixes. All XenServer hotfixes can be applied at the same time and the hotfixes in the article are not relevant to the installation order

Hotfix XS76E002 –

For XenServer 7.6
All customers who are affected by the issues described in CTX239432 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable** No
Hotfix XS75E003 –

For XenServer 7.5
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable** No
Hotfix XS75E005 –

For XenServer 7.5
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable** No
Hotfix XS75E007 –

For XenServer 7.5
All customers who are affected by the issues described in CTX239432 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS74E005 –

For XenServer 7.4
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable** No
Hotfix XS74E006 –

For XenServer 7.4
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix..

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS74E007 –

For XenServer 7.4
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable** No
XenCenter 7.1.3

This release of XenCenter is for customers who use XenCenter as the management console for XenServer 7.1 LTSR. XenCenter 7.1 CU2 is released as part of XenServer 7.1 Cumulative Update 2 and is available only to customers on the Customer Success Services program.

We recommend that you install this version of XenCenter before using XenCenter to update XenServer 7.1 CU1 hosts to XenServer 7.1 CU2.

XS71ECU2

XenServer 7.1 Cumulative Update 2 (XS71ECU2) must be installed by customers running XenServer 7.1 LTSR CU1. It includes all previously released XenServer 7.1 CU1 hotfixes. Installation of XS71ECU2 is required for all future functional hotfixes for XenServer 7.1 LTSR.

XenServer 7.1 Cumulative Update 2 and its subsequent hotfixes are available only to customers on the Customer Success Services program.

Citrix will continue to provide security updates to the base XenServer 7.1 CU1 product for a period of three months from the release date of the XenServer 7.1 Cumulative Update 2 (until March 12, 2019). After this three month period elapses, any new hotfixes released will only support XenServer 7.1 with CU2 applied.

For more information about XenServer 7.1 CU2, see the Citrix XenServer 7.1 Cumulative Update 2 Release Notes.

Content live patchable** No

XenServer 7.1 Cumulative Update 1 (XS71ECU1) should be installed by customers running XenServer 7.1. It includes all previously released XenServer 7.1 hotfixes. Installation of XS71ECU1 is required for all future functional hotfixes for XenServer 7.1 LTSR. XenServer 7.1 Cumulative Update 1 and its subsequent hotfixes are available only to customers on the Customer Success Services program.

Citrix will continue to provide security updates to the base XenServer 7.1 product for a period of three months from the release date of the XenServer 7.1 Cumulative Update 1 (until December 11, 2017). After this three month period elapses, any new hotfixes released will only support XenServer 7.1 with CU1 applied.

XenCenter 7.1.2

This release of XenCenter is for customers who use XenCenter as the management console for XenServer 7.1.

XenCenter 7.1.2 is available on the Citrix downloads site as a restricted download. You must sign in to the site and have active membership of the Customer Success Services (CSS) program to access these downloads.

Hotfix XS71ECU1006-

For XenServer 7.1CU1
This is a hotfix for customers running XenServer 7.1 Cumulative Update 1. All customers who are affected by the issues described in CTX230138 – Citrix XenServer Multiple Security Updates should install this hotfix.

Content live patchable* No
Hotfix XS71ECU1013-

For XenServer 7.1CU1
This is a hotfix for customers running XenServer 7.1 Cumulative Update 1. All customers who are affected by the issues described in CTX232655 – Citrix XenServer Multiple Security Updates should install this hotfix.

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above. In addition, it resolves the following issue:

  • If SNMP configuration is modified to request interface statistics Object Identifiers (OIDs) and when SNMP service happens to start before Openvswitch service, all further statistics requests to SNMP returns incorrect data.
Content live patchable* No
Hotfix XS71ECU1015-

For XenServer 7.1CU1

This hotfix addresses following issues:

Customers using Active Directory (AD) with XenCenter are unable to log on to XenCenter, or get disconnected intermittently. In some cases, XenCenter displays incorrect AD group membership details. This hotfix resolves this issue.

Content live patchable* No
Hotfix XS71ECU1019-

For XenServer 7.1CU1

This hotfix resolves the following issues:

  • A race condition in XenBus can cause pauses in Windows VM operation, which lead to Timeout Detection and Recovery (TDR) events. The TDR can cause the VM to crash.
  • Under low resource situations, Xennet can consume all of the RAM on a Windows VM. This causes the VM to crash.
  • XenVBD can consume 100% of a vCPU and can block other processes from using that vCPU.
Content live patchable* No

This hotfix also includes the following previously released hotfixes:

Hotfix XS71ECU1026-

For XenServer 7.1CU1
All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS71ECU1029-

For XenServer 7.1CU1

This hotfix resolves the following issues:

  • After rebooting, a XenServer host can fail to connect to iSCSI targets on Compellent arrays.
  • When you attempt to migrate a VM between resource pools, the migration can fail with the following error: Storage_interface.Internal_error(“Jsonrpc.Parse_error(_)”). This migration failure can cause some versions of XenCenter to fail.
  • If you cancel an ongoing Storage XenMotion, the next attempt to migrate the VM using Storage XenMotion fails with the VDI Mirroring Cannot be performed error. However, any subsequent attempts to migrate the VM will succeed.
  • After taking a disk-only snapshot for a VM running in the pool, users randomly fail to access the Virtual Hard Disk (VHD) when trying to unpause the VM, and the VM stops responding. This is caused by time racing in Linux Logical Volume Manager (LVM).
  • In addition, this hotfix includes minor performance improvements when performing a large number of VM I/O operations.

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS71ECU1030-

For XenServer 7.1CU1

This hotfix resolves the following issues:

  • An incorrect setting in the I/O scheduler for all blktap devices can cause poor I/O performance in certain scenarios, depending on the server hardware, server configuration, VM configuration, and workload. This hotfix includes the correct setting.
  • Due to incorrect maximum sector size used by Dom0 kernel, users failed to copy VDIs to/from SR targets on certain iSCSI disks.
  • For XenServer pools that use certain storage targets, a race condition in the iSCSI module can cause hosts in the pool to crash.
  • It is not possible to attach storage provided by iSCSI target Server on Windows Server 2016 VMs.

This hotfix also includes the following previously released hotfixes:

Content live patchable** Yes
Hotfix XS71ECU1032-

For XenServer 7.1CU1
All customers who are affected by the issues described in CTX239432 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Content live patchable** No
Hotfix XS71ECU1033-

For XenServer 7.1CU1

This hotfix resolves the following issues:

  • If customers upgrade a host with legacy disk partition from XenServer 6.x to XenServer 7.1 CU1, and then attempt to apply a subsequent Cumulative Update as an update, they may receive an insufficient space error. This hotfix includes a fix to reduce the calculated space required to apply the update. You must apply this hotfix to XenServer 7.1 CU1 before attempting to update to a subsequent Cumulative Update. This hotfix should not be necessary on hosts that have the new host disk partition layout introduced in XenServer 7.0.
  • When customers are attempting to use Jumbo Frames, a VM without PV drivers installed would cause the MTU to drop to 1500 as the MTU was only being set for the paravirtualised VIF device and not for the fully emulated TAP device.

This hotfix also includes the following previously released hotfixes:

Content live patchable** No

Apply the following hotfixes for XenServer 7.0 and restart XenServer when the hotfix installation is complete.

Hotfix XS70E001 –

For XenServer 7.0
This is a XenCenter update (a .exe file) and not a host side Hotfix. This package needs to be installed

on the Windows Machine Running XenCenter
Hotfix XS70E002 – For XenServer 7.0 All customers who are affected by the CVE-2016-2107 issue described in

CTX212736: Citrix XenServer Multiple Security Updates should install this hotfix.
Hotfix XS70E004 – For XenServer 7.0 Important: This is a critical hotfix for customers running XenServer 7.0. All XenServer 7.0

customers must apply this hotfix.
Hotfix XS70E009 – For XenServer 7.0

This hotfix resolves the following issue:

  • In rare circumstances when a XenServer host is enabling HA, or during a host reboot with HA enabled, the host can fail to establish HA communication with the other hosts. This is due to another process on the host using the listening port required by the HA software.
Update XS70EU001 – Management Agent for XenServer 7.0 The Management Agent update resolves the following issues:

  • Installation of Management Agent can fail after installing newer I/O drivers through Windows Update.
  • Failure to reboot a Windows VM after installing XenServer Tools can result in excessive log entries being written to xensource.log and xenstored-access.log until the VM is rebooted. If customers do not reboot the VM, or delay the reboot, excess logs can fill up the XenServer host log partition.
  • The Management Agent can crash and respawn on systems without a terminal services Windows Management Instrumentation (WMI) object causing high CPU usage and excessive logging in /var/log/daemon.
  • If the Management Agent auto update is enabled after installing XenServer Tools, and a new update is available, the initial auto-update can fail due to a race condition that can cause multiple update attempts to occur simultaneously.
Update XS70EU002 – Management Agent for XenServer 7.0 New versions of the I/O drivers, compatible with Microsoft Windows Server 2016 have been released.
Update XS70EU003 – Management Agent for XenServer 7.0
  • The default behavior of the Management Agent has been improved to enable customers to configure whether any I/O driver updates included in the Management Agent should be applied automatically. For more information, see section 4.3.1 Installing XenServer Tools in the XenServer 7.0 Virtual Machine User’s Guide.
  • This version (v7.1.844) of the Management Agent includes new versions of the I/O drivers that are compatible with Microsoft Windows Server 2016. These drivers have been released previously through the Microsoft Windows Server Update Service. For more information, see Update XS70EU002 – Windows I/O Drivers for XenServer 7.0.
Hotfix XS70E018 – For XenServer 7.0 This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX220112: Citrix XenServer Multiple Security Updates should install this hotfix.
  • This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX219378: Citrix XenServer Multiple Security Updates should install this hotfix.
  • This hotfix supports the improvements to XenServer’s Direct Inspect APIs.
Hotfix XS70E024 – For XenServer 7.0
  • When booting a vGPU provisioned Virtual Machine (VM) from network, an interaction between VGA BIOS and VGA emulation code in the vGPU device model can result in the corruption of the VM console in XenCenter.
Hotfix XS70E027 – For XenServer 7.0
  • When Installing XenServer or upgrading XenServer to a newer version, PBIS services get enabled (even when Role-based access control (RBAC) is not used) and display a lot of error messages. Also, this issue consumes a lot of control domain (dom0) resources.
Hotfix XS70E028 – For XenServer 7.0 This hotfix supports the following new guest operating systems.

  • Oracle Linux 6.8
  • Red Hat Enterprise Linux 6.8
  • CentOS 6.8
  • NeoKylin Linux Advanced Server 6.5 ( only 64 bit )
  • NeoKylin Linux Advanced Server 7.2 ( Only 64 bit )
  • SUSE Linux Enterprise Server 11 SP4
Hotfix XS70E037 – For XenServer 7.0

This hotfix addresses the following issue:

  • When attempting to use XenServer Conversion Manager (XCM) Console to connect to an XCM Virtual Appliance that runs on a slave host, the connection fails and the following message is displayed by the console: “There was a failure communicating with the plugin.” This hotfix ensures that the XCM Console can connect to a XCM Virtual Appliance that runs on any XenServer host.
Hotfix XS70E041 – For XenServer 7.0

This hotfix resolves the following issue:

  • When using SSH to connect to XenServer, a user might experience a memory leak in systemd on XenServer.
Hotfix XS70E042 – For XenServer 7.0

This hotfix resolves the following issues:

  • Excessive input/output from a process could trigger a SCSI target reset while the process is still ongoing. This leads to tapdisk logs reporting invalid request type and/or invalid number of segments, and filling up the Dom0 log partition. This issue occurs due to a race condition that leads to an incorrect reference count.
  • When running XenDesktop on XenServer, if you have logged on to the console session using terminal services, then, multiple XenDpriv.exe processes are seen running. This issue occurs when VMs treat all logins as if they were console logins.
  • When installing windows PV tools on Windows 10 and Windows Server 2016, users are not notified to reboot the VM in order to continue with the driver installation.
  • If the clipboard buffer on a VM contains the “%s” format specifier, the VM can bug check with error SYSTEM_SERVICE_EXCEPTION 0x3B (c0000005).
  • When a Virtual Network Interface (VIF) receives malformed packets, the virtual CPU (vCPU) can cause Windows VMs to rise to 100% CPU usage and become unresponsive at the console.

This hotfix also includes the following previously released hotfix:

Hotfix XS70E043 – For XenServer 7.0

This hotfix resolves the following issue:

  • Under certain workloads on Skylake and Kaby Lake processors with Hyper-Threading enabled, applications can crash or incorrect program behavior can be observed. Microcode update fixes this issue.
Hotfix XS70E048 – For XenServer 7.0 This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX230138 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Hotfix XS70E052 – For XenServer 7.0 This is a hotfix for customers running XenServer 7.0. All customers who are affected by the issues described in CTX232655 – Citrix XenServer Multiple Security Updates should install this hotfix.This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.
Hotfix XS70E061 – For XenServer 7.0

This is a hotfix for customers running XenServer 7.0.

All customers who are affected by the issues described in CTX236548 – Citrix XenServer Multiple Security Updates should install this hotfix.

Hotfix XS70E062 – For XenServer 7.0

This hotfix resolves the following issues:

  • Virtual machines (VMs) configured with in-guest software RAID may fail to cleanly shut down or restart.
  • After taking a disk-only snapshot for a VM running in the pool, users randomly fail to access the Virtual Hard Disk (VHD) when trying to unpause the VM, and the VM stops responding. This is caused by time racing in Linux Logical Volume Manager (LVM).
  • After rebooting, a XenServer host can fail to connect to iSCSI targets on Compellent arrays.
  • When Intellicache mirroring fails due to ENOSPC on shared storage, the VBD image list gets truncated to point to itself. This causes an infinite loop and can lead to the I/O datapath stopping and subsequently VMs freezing.
  • When a pool master node executes multi-step plugins on the pool member nodes after important events such as coalesce, the plugin continues to execute through all its steps even if one of the previous ones have failed. This can lead to complications such that the other VDI operations are permanently blocked with OTHER_OPERATION_IN_PROGRESS.
  • After deleting a snapshot on a pool member that is not the pool master, a coalesce operation may not succeed. In such cases, the coalesce process can constantly retry to complete the operation, resulting in the creation of multiple RefCounts that can consume a lot of space on the pool member.
  • The storage cleanup process initiated after a VDI destroy can conflict with ongoing VDI copy processes (including Storage XenMotion), causing subsequent operations on the SR to fail.

This hotfix also includes the following previously released hotfixes:

Hotfix XS70E063 – For XenServer 7.0

This hotfix resolves the following issues:

  • High Availability (HA) enabled VMs can take longer to restart after a HA failover.
  • In rare cases, when a XenServer host in a pool is restarted, it may not be able to rejoin the pool.
  • In rare cases, attempts to shut down a XenServer host in a pool may not succeed.
  • On HA-enabled pools, when a task is initiated after a XenServer host has failed, VMs running on the host can take longer (about 10 minutes) to restart. This issue occurs when a task is assigned to the host after it has failed, but before XAPI is aware of the host failure. In such cases, the task doesn’t get cancelled even when XAPI is notified about the failure, causing delays in restarting the VMs.
  • When migrating VMs that have Dynamic Memory Control (DMC) enabled, the VMs shutdown operation can unexpectedly fail. This is caused by reducing memory allocation before shutdown and this operation taking longer than expected.
  • On Nutanix hosts, the host’s memory-overhead is miscalculated after first boot. This is because XAPI calculates the available host RAM on startup assuming no domains other than the XenServer Control Domain are running. On first boot this is true but on subsequent boots, the Nutanix Controller VM (CVM) is started before XAPI.

This hotfix also includes the following previously released hotfixes:

Hotfix XS70E064 – For XenServer 7.0 All customers who are affected by the issues described in CTX239432 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix also includes the following previously released hotfixes:

Related:

  • No Related Posts

XenServer 7.1 Cumulative Update 1

Who Should Install This Cumulative Update?

XenServer 7.1 Cumulative Update 1 (XS71ECU1) should be installed by customers running XenServer 7.1. It includes all previously released XenServer 7.1 hotfixes. Installation of XS71ECU1 is required for all future functional hotfixes for XenServer 7.1 LTSR.

XenServer 7.1 Cumulative Update 1 and its subsequent hotfixes are available only to customers on the Customer Success Services program.

Citrix will continue to provide security updates to the base XenServer 7.1 product for a period of three months from the release date of the XenServer 7.1 Cumulative Update 1 (until December 11, 2017). After this three month period elapses, any new hotfixes released will only support XenServer 7.1 with CU1 applied.

For more information about XenServer 7.1 CU1, see the Citrix XenServer 7.1 Cumulative Update 1 Release Notes.

Information About this Cumulative Update

Component Details
Prerequisite
  • XenServer 7.1

  • Licensed customer with Customer Success Service

Post-update tasks Restart Host
Content live patchable* No
Revision History Published on September 11, 2017
* Available to Enterprise Customers.

Included in this Cumulative Update

This cumulative update includes the following previously released hotfixes.

  1. CTX222368 – Hotfix XS71E001 – For XenServer 7.1
  2. CTX224279 – Hotfix XS71E002 – For XenServer 7.1
  3. CTX223285 – Hotfix XS71E003 – For XenServer 7.1
  4. CTX222843 – Hotfix XS71E004 – For XenServer 7.1
  5. CTX221590 – Hotfix XS71E005 – For XenServer 7.1
  6. CTX222424 – Hotfix XS71E006 – For XenServer 7.1
  7. CTX223290 – Hotfix XS71E007 – For XenServer 7.1
  8. CTX223858 – Hotfix XS71E008 – For XenServer 7.1
  9. CTX225676 – Hotfix XS71E009 – For XenServer 7.1
  10. CTX224899 – Hotfix XS71E010 – For XenServer 7.1
  11. CTX224691 – Hotfix XS71E011 – For XenServer 7.1
  12. CTX224697 – Hotfix XS71E012 – For XenServer 7.1
  13. CTX226298 – Hotfix XS71E013 – For XenServer 7.1
  14. CTX226299 – Hotfix XS71E014 – For XenServer 7.1

This cumulative update also includes additional fixes. For a list of the issues resolved by XenServer 7.1 CU1, see the Citrix XenServer 7.1 Cumulative Update 1 Release Notes.

Installing the Cumulative Update

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this cumulative update. When the installation is complete, see the Post-update tasks in the table Information About this Cumulative Update 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 cumulative update update package only. Click the following link to download the source code for any modified open source components XS71ECU1-sources.iso. The source code is not necessary for cumulative update installation: it is provided to fulfill licensing obligations.

Installing the Cumulative Update by using XenCenter

Before installing this cumulative update, we recommend that you update your version of XenCenter to the latest available version for XenServer 7.1 CU 1.

Choose an Installation Mechanism

There are three mechanisms to install a cumulative update:

  1. Automated Updates
  2. Download update from Citrix
  3. 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 cumulative update using the Automated Updates feature, see the section Applying Automated Updates in the XenServer 7.1 Cumulative Update 1 Installation Guide.

For information about installing a cumulative update using the Download update from Citrix option, see the section Applying an Update to a Pool in the XenServer 7.1 Cumulative Update 1 Installation Guide.

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

  1. Download the cumulative update to a known location on a computer that has XenCenter installed.
  2. Unzip the cumulative update 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 XS71ECU1.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the cumulative update 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. In addition, the Install Update wizard checks whether a live patch (this is an Enterprise Edition feature) is available for the cumulative update and if the live patch can be successfully applied to the hosts. For more information, see Live Patching in XenServer in XenServer 7.1 Installation Guide.

    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.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode. If the update contains a live patch that can be successfully applied to the hosts, it displays No action required on the Tasks to be performed screen.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. 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.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Cumulative Update by using the xe Command Line Interface

  1. Download the cumulative update 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>XS71ECU1.iso

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

    5eea06f3-4990-497d-af7a-d0bba6f9f96a

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

    xe update-pool-apply uuid=<UUID_of_file>

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

    xe upload-apply host-uuid=<UUID_of_host> uuid=<UUID_of_file>

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

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

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this cumulative update was successfully applied. This should be a complete list of all hosts in the pool.

  6. If the cumulative update is applied successfully, carry out any specified post-update task on each host, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS71ECU1.iso
Hotfix File sha256 66a75cbddde0d6fb5712fa726c3e8e4505a9bde4a660618c247425aaddfa634b
Hotfix Source Filename XS71ECU1-sources.iso
Hotfix Source File sha256 6af223f7811cbea27c496c017bbf8940e022f98e5ea29125df40b2613b33eec0
Hotfix Zip Filename XS71ECU1.zip
Hotfix Zip File sha256 03c6765b1454176339a17373b35a682e191d2d103b0e5b14d9d94c9d069a6b90
Size of the Zip file 253 MB

Files Updated

blktap-3.5.0-xs.1+1.0_71.1.0.x86_64.rpm
control-XS71ECU1-1.0-1.noarch.rpm
device-mapper-1.02.107-5.xs+1.2.x86_64.rpm
device-mapper-event-1.02.107-5.xs+1.2.x86_64.rpm
device-mapper-event-libs-1.02.107-5.xs+1.2.x86_64.rpm
device-mapper-libs-1.02.107-5.xs+1.2.x86_64.rpm
forkexecd-1.1.2-1.el7.centos.x86_64.rpm
gpumon-0.4.0-2.el7.centos.x86_64.rpm
grub-2.02-1.xs18.x86_64.rpm
grub-efi-2.02-1.xs18.x86_64.rpm
grub-tools-2.02-1.xs18.x86_64.rpm
host-upgrade-plugin-1.1.3-1.x86_64.rpm
kernel-4.4.27-600.1.6.x86_64.rpm
lvm2-2.02.130-5.xs+1.2.x86_64.rpm
lvm2-libs-2.02.130-5.xs+1.2.x86_64.rpm
message-switch-1.4.1-1.el7.centos.x86_64.rpm
microcode_ctl-2.1-14.2.x86_64.rpm
ocaml-xenops-tools-1.0.1-4.el7.centos.x86_64.rpm
openssl-1.0.1e-51.el7_2.5.x86_64.rpm
openssl-libs-1.0.1e-51.el7_2.5.i686.rpm
openssl-libs-1.0.1e-51.el7_2.5.x86_64.rpm
openssl-perl-1.0.1e-51.el7_2.5.x86_64.rpm
openvswitch-2.3.2-24.1.2.0.x86_64.rpm
pbis-open-8.2.2-1.7.1.x86_64.rpm
pbis-open-upgrade-8.2.2-3.x86_64.rpm
rrd2csv-1.0.2-2.el7.centos.x86_64.rpm
rrdd-plugins-1.0.4-1.el7.centos.x86_64.rpm
sm-1.17.0-xs.2+1.0_71.1.1.x86_64.rpm
sm-cli-0.9.8-1.el7.centos.x86_64.rpm
squeezed-0.13.0-3.el7.centos.x86_64.rpm
systemd-219-19.el7_2.7.xs7.2.x86_64.rpm
systemd-libs-219-19.el7_2.7.xs7.2.x86_64.rpm
systemd-sysv-219-19.el7_2.7.xs7.2.x86_64.rpm
update-XS71ECU1-1.0-1.noarch.rpm
v6d-citrix-10.0.5-1.el7.centos.x86_64.rpm
vhd-tool-0.11.0-1.el7.centos.x86_64.rpm
wsproxy-1.1.0-1.el7.centos.x86_64.rpm
xapi-core-1.14.35-1.x86_64.rpm
xapi-storage-0.9.0-2.el7.centos.x86_64.rpm
xapi-storage-script-0.13.0-1.el7.centos.x86_64.rpm
xapi-tests-1.14.35-1.x86_64.rpm
xapi-xe-1.14.35-1.x86_64.rpm
xcp-networkd-0.13.4-1.el7.centos.x86_64.rpm
xcp-python-libs-2.0.2-1.noarch.rpm
xcp-rrdd-1.2.0-3.el7.centos.x86_64.rpm
xencenter-7.1.2.5459-1.noarch.rpm
xen-device-model-0.10.2.xs-1.2.x86_64.rpm
xen-dom0-libs-4.7.1-1.9.x86_64.rpm
xen-dom0-tools-4.7.1-1.9.x86_64.rpm
xengt-2.0.4-1.x86_64.rpm
xengt-userspace-2.0.4-1.x86_64.rpm
xen-hypervisor-4.7.1-1.9.x86_64.rpm
xen-libs-4.7.1-1.9.x86_64.rpm
xenops-cli-1.0.2-2.el7.centos.x86_64.rpm
xenopsd-0.17.10-1.el7.centos.x86_64.rpm
xenopsd-xc-0.17.10-1.el7.centos.x86_64.rpm
xenopsd-xenlight-0.17.10-1.el7.centos.x86_64.rpm
xenserver-docs-7.1.0-16.noarch.rpm
xenserver-pv-tools-7.1.54-1.noarch.rpm
xenserver-release-7.1.1-4.x86_64.rpm
xenserver-release-config-7.1.1-4.x86_64.rpm
xenserver-transfer-vm-7.1.2-2.noarch.rpm
xen-tools-4.7.1-1.9.x86_64.rpm

More Information

For more information see, the XenServer 7.1 Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

7023547: How to run GDB to debug a process in SMG

Step 2: Shutdown the module to be tested

This step is crucial to save the headache of dealing with modules trying to automatically reload.

If possible, shut down the program either with the modules UI page, or by sending a kill command to the module from a terminal window. If the kill command is used, it MUST NOT be used with the -9 switch, as this will not allow the module to stay down.

If shutting down the module is not possible, typically due to a crash/restart loop, disable the server setting for ‘Module auto-recovery’ under the Manage Servers UI page. With this setting disabled, the program will not come back up by itself. It is important to remember to re-enable this option when the back trace has been obtained.

Step 3: Ensure gdb is installed

To get the debug information, gdb is required, but it not installed by default.

Type ‘gdb –help’ at the terminal prompt to check that it is installed.

If the help page is not displayed, install gdb by typing ‘apt install gdb’.

Step 4: Run the module in debug mode

Using the startup command determined in step 1, we can now prepare to start the application. Using the examples from step 1, and assuming the module we are investigating is gwvsmtp, enter the following commands, noting the additional switch that has been added to the end of the line:

cd /opt/gwava/assets/bin/linux/x64

gdb --args /opt/gwava/assets/bin/linux/x64/gwvsmtp "/root=/opt/gwava/" /ServerId=1 /ModuleId=1 /ConsoleLog

After typing these commands you should be placed into the gdb program at a (gdb) prompt which is ready to run the application. Type ‘r’ to start the program.

Step 5: Watch and wait

Now that the program is running, it is simply a matter of waiting for the crash to occur. The /ConsoleLog switch that was included on the command line will be echoing to the terminal display. This is the same log information that is stored in the application logs. By emitting it during the debug session, we are able to capture the end of the log along with the debug information which saves on the effort of matching log files to the information we are after.

Leave the program running until it stops. This will be evident when the log stops scrolling and you are given a prompt to type at.

Step 6: Obtain the backtrace

Once the program fails, type ‘bt’ at the prompt. This will provide a set of lines that include the information that’s useful to engineering.

Scroll back up through the information to where the logging information ends. Copy the text from approximately one screenful of logging information down to the end of the backtrace information. Pay attention to what’s in the log information and if it seems that more may be useful, copy as much as seems necessary. It is better to capture more information than less if you are unsure of what you are reading. Using the time on the log can also be a useful way to determine what might be necessary. If there are four pages of log data within the same second, chances are that’s all going to be related.

The information should look something like this:

Step 7: Clean up

To exit gdb, enter ‘q’. This will return you to the terminal prompt.

If Module auto-recovery was disabled, re-enable it on the Manage Servers page.

Restart the programs using the appropriate method for the system you are working on.

Step 8: Provide the information to engineering

Self explanatory. Add the information to the bug ticket, or via email to the engineer that requested the information.

Related:

  • No Related Posts

Hotfix XS71ECU1033 – For XenServer 7.1 CU1

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.1 Cumulative Update 1 with a legacy disk partition scheme.

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 the XAPI Toolstack
Content live patchable** No
Baselines for Live Patch N/A
Revision History

Published on November 30, 2018

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This hotfix resolves the following issues:

  • If customers upgrade a host with legacy disk partition from XenServer 6.x to XenServer 7.1 CU1, and then attempt to apply a subsequent Cumulative Update as an update, they may receive an insufficient space error. This hotfix includes a fix to reduce the calculated space required to apply the update. You must apply this hotfix to XenServer 7.1 CU1 before attempting to update to a subsequent Cumulative Update. This hotfix should not be necessary on hosts that have the new host disk partition layout introduced in XenServer 7.0.
  • When customers are attempting to use Jumbo Frames, a VM without PV drivers installed would cause the MTU to drop to 1500 as the MTU was only being set for the paravirtualised VIF device and not for the fully emulated TAP device.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the XenServer 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 XS71ECU1033-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:

  1. Automated Updates
  2. Download update from Citrix
  3. 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:

  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 XS71ECU1033.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. 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.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. 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.
  13. When the update is applied, click Finish to close the wizard.
  14. 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>XS71ECU1033.iso

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

    4058e644-e819-11e8-842a-b36f8ca04d81

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

    xe update-pool-apply uuid=4058e644-e819-11e8-842a-b36f8ca04d81

    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=4058e644-e819-11e8-842a-b36f8ca04d81

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

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

    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.

Files

Hotfix File

Component Details
Hotfix Filename XS71ECU1033.iso
Hotfix File sha256 b97c6d527df01ddac8d37746cb4c9d1a80d238b75cb82baf2cba433dcd22413a
Hotfix Source Filename XS71ECU1033-sources.iso
Hotfix Source File sha256 b33ecea9f4577f674fc725a0f47bb281aa3dbe7e7c6487ae3ff1c881572dd2f7
Hotfix Zip Filename XS71ECU1033.zip
Hotfix Zip File sha256 c8fc91a8e4e589e98879e05853bf5f03bdc5165fbbbad3dfcf62e830cb35c893
Size of the Zip file 48.9 MB

Files Updated

squeezed-0.13.2-1.el7.centos.x86_64.rpm
v6d-citrix-10.0.7-1.el7.centos.x86_64.rpm
vhd-tool-0.11.3-1.el7.centos.x86_64.rpm
xapi-core-1.14.39.1-1.x86_64.rpm
xapi-tests-1.14.39.1-1.x86_64.rpm
xapi-xe-1.14.39.1-1.x86_64.rpm
xcp-networkd-0.13.6-1.el7.centos.x86_64.rpm
xenopsd-0.17.12-1.el7.centos.x86_64.rpm
xenopsd-xc-0.17.12-1.el7.centos.x86_64.rpm
xenopsd-xenlight-0.17.12-1.el7.centos.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

Hotfix XS71ECU1032 – For XenServer 7.1 Cumulative Update 1

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.1 Cumulative Update 1.

All customers who are affected by the issues described in CTX239432 – Citrix XenServer 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 November 20, 2018

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the XenServer 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 XS71ECU1032-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:

  1. Automated Updates
  2. Download update from Citrix
  3. 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:

  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 XS71ECU1032.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. 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.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. 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.
  13. When the update is applied, click Finish to close the wizard.
  14. 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>XS71ECU1032.iso

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

    28f4de5b-9165-479e-88d2-5aafe500f507

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

    xe update-pool-apply uuid=28f4de5b-9165-479e-88d2-5aafe500f507

    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=28f4de5b-9165-479e-88d2-5aafe500f507

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

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

    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.

  6. If the hotfix is applied successfully, restart each host in the pool, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS71ECU1032.iso
Hotfix File sha256 a1954439ed27737add17bd3c78e3c4fe1d4cf2c9a3231d499a5af572663401fc
Hotfix Source Filename XS71ECU1032-sources.iso
Hotfix Source File sha256 969ede718dec52f5291b786eda1d3e9995ccbddb23a70154f8cd95118d3bf952
Hotfix Zip Filename XS71ECU1032.zip
Hotfix Zip File sha256 55e917d7c24fe88ef7a1ce0ace25cb84b0e30ae2b2168707d237d7199dee0263
Size of the Zip file 31.83 MB

Files Updated

dracut-033-360.el7.centos.xs13.x86_64.rpm
dracut-network-033-360.el7.centos.xs13.x86_64.rpm
kexec-tools-2.0.4-31.x86_64.rpm
linux-firmware-20170622-3.2.noarch.rpm
microcode_ctl-2.1-26.xs1.x86_64.rpm
xen-dom0-libs-4.7.5-1.23.x86_64.rpm
xen-dom0-tools-4.7.5-1.23.x86_64.rpm
xen-hypervisor-4.7.5-1.23.x86_64.rpm
xen-libs-4.7.5-1.23.x86_64.rpm
xen-tools-4.7.5-1.23.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

Hotfix XS75E007 – For XenServer 7.5

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.5.

All customers who are affected by the issues described in CTX239432 – Citrix XenServer 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 November 20, 2018

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the XenServer 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 XS75E007-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:

  1. Automated Updates
  2. Download update from Citrix
  3. 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:

  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 XS75E007.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. 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.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. 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.
  13. When the update is applied, click Finish to close the wizard.
  14. 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>XS75E007.iso

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

    72655461-6cb2-4c66-a347-23bf6a7ba0b7

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

    xe update-pool-apply uuid=72655461-6cb2-4c66-a347-23bf6a7ba0b7

    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=72655461-6cb2-4c66-a347-23bf6a7ba0b7

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

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

    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.

  6. If the hotfix is applied successfully, restart each host in the pool, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS75E007.iso
Hotfix File sha256 3fb4e6e85910e2ce53e3a4d6b5e8d522eb5f8a6645d4af4852e4b7c2a0e8b653
Hotfix Source Filename XS75E007-sources.iso
Hotfix Source File sha256 60c678e59d7007033427e1340c076f927aa368409ea1d910a5aa7e380a760934
Hotfix Zip Filename XS75E007.zip
Hotfix Zip File sha256 719e04100a24ccfbec8290739675b7858c4a9f668f379ba58acf969c6c6c219c
Size of the Zip file 31.4 MB

Files Updated

linux-firmware-20170622-3.2.noarch.rpm
microcode_ctl-2.1-26.xs1.x86_64.rpm
xen-dom0-libs-4.7.5-5.7.x86_64.rpm
xen-dom0-tools-4.7.5-5.7.x86_64.rpm
xen-hypervisor-4.7.5-5.7.x86_64.rpm
xen-libs-4.7.5-5.7.x86_64.rpm
xen-tools-4.7.5-5.7.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

Hotfix XS76E002 – For XenServer 7.6

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.6.

All customers who are affected by the issues described in CTX239432 – Citrix XenServer Multiple Security Updates should install this hotfix.

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 November 20, 2018

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

This hotfix also includes the following previously released hotfix:

Installing the Hotfix

Customers should use either XenCenter or the XenServer 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 XS76E002-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:

  1. Automated Updates
  2. Download update from Citrix
  3. 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 Citrix Virtual Apps and Desktops 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:

  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 XS76E002.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. 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.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. 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.
  13. When the update is applied, click Finish to close the wizard.
  14. 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>XS76E002.iso

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

    c38a0f28-62d7-4eae-8f54-0b75cdb3ea14

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

    xe update-pool-apply uuid=c38a0f28-62d7-4eae-8f54-0b75cdb3ea14

    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=c38a0f28-62d7-4eae-8f54-0b75cdb3ea14

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

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

    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.

  6. If the hotfix is applied successfully, restart each host in the pool, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS76E002.iso
Hotfix File sha256 e13d6d93ebc9019aa41c5c70e364a09272f23d1bc4a1da1f38eb4d059adf7811
Hotfix Source Filename XS76E002-sources.iso
Hotfix Source File sha256 4b13fab66b57f612bffffc6ae9fbaa5d0c3f8e60e300d9d8ef8995f900c3a901
Hotfix Zip Filename XS76E002.zip
Hotfix Zip File sha256 9f0a7c274cb0ed30a4f6c9fe3184861ce8584948c7571c3ab03cd50080ae67a7
Size of the Zip file 2.58 MB

Files Updated

xen-hypervisor-4.7.6-6.3.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

Hotfix XS71ECU1030 – For XenServer 7.1 Cumulative Update 1

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.1 Cumulative Update 1.

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** Yes
Baselines for Live Patch XS71ECU1027
Revision History

Published on November 8, 2018

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This hotfix resolves the following issues:

  • An incorrect setting in the I/O scheduler for all blktap devices can cause poor I/O performance in certain scenarios, depending on the server hardware, server configuration, VM configuration, and workload. This hotfix includes the correct setting.
  • Due to incorrect maximum sector size used by Dom0 kernel, users failed to copy VDIs to/from SR targets on certain iSCSI disks.
  • For XenServer pools that use certain storage targets, a race condition in the iSCSI module can cause hosts in the pool to crash.
  • It is not possible to attach storage provided by iSCSI target Server on Windows Server 2016 VMs.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the XenServer 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 XS71ECU1030-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:

  1. Automated Updates
  2. Download update from Citrix
  3. 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:

  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 XS71ECU1030.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. 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.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. 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.
  13. When the update is applied, click Finish to close the wizard.
  14. 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>XS71ECU1030.iso

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

    b9cf20be-45b1-48e9-a0cd-e495960a42a2

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

    xe update-pool-apply uuid=b9cf20be-45b1-48e9-a0cd-e495960a42a2

    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=b9cf20be-45b1-48e9-a0cd-e495960a42a2

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

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

    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.

  6. If the hotfix is applied successfully, restart each host in the pool, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS71ECU1030.iso
Hotfix File sha256 ae88638d308a81caea696273496fc4453002f776979b5baa4ebabd240cbc04a8
Hotfix Source Filename XS71ECU1030-sources.iso
Hotfix Source File sha256 763fa96dda5881fe609386aae5a60e7aaee00cd3e623324ec83004fc5230a1a0
Hotfix Zip Filename XS71ECU1030.zip
Hotfix Zip File sha256 13539a290b18217f25f19df80ba975eadaac803fa008dbcec2bdf281a4e7a1c9
Size of the Zip file 21.04 MB

Files Updated

kernel-4.4.27-600.1.10.x86_64.rpm
kernel-livepatch_4.4.27_600.1.9-1-1.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

Hotfix XS71ECU1031 – For XenServer 7.1 CU1

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.1 Cumulative Update 1.

All customers who are affected by the issues described in CTX239100 – Citrix XenServer 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** Yes
Baselines for Live Patch XS71ECU1026
Revision History

Published on October 26, 2018

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the XenServer 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 XS71ECU1031-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:

  1. Automated Updates
  2. Download update from Citrix
  3. 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:

  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 XS71ECU1031.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. 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.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. 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.
  13. When the update is applied, click Finish to close the wizard.
  14. 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>XS71ECU1031.iso

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

    5b7e23fc-4b4f-43c3-8691-d7b453c771c3

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

    xe update-pool-apply uuid=5b7e23fc-4b4f-43c3-8691-d7b453c771c3

    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=5b7e23fc-4b4f-43c3-8691-d7b453c771c3

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

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

    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.

  6. If the hotfix is applied successfully, restart each host in the pool, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS71ECU1031.iso
Hotfix File sha256 f58de41675ae60d19be43ed8990edba3b9037f58f05292316bf76690735ed9ca
Hotfix Source Filename XS71ECU1031-sources.iso
Hotfix Source File sha256 fc52d65d6173fba1b6f495f6df3159cddcf3675462d66336d775c0a4b11750bb
Hotfix Zip Filename XS71ECU1031.zip
Hotfix Zip File sha256 ac9e69847dcd8e075b03ae463e36e5c88f61eef1071b3928c22190320e2df8cf
Size of the Zip file 31.84 MB

Files Updated

dracut-033-360.el7.centos.xs13.x86_64.rpm
dracut-network-033-360.el7.centos.xs13.x86_64.rpm
kexec-tools-2.0.4-31.x86_64.rpm
linux-firmware-20170622-3.2.noarch.rpm
microcode_ctl-2.1-26.xs1.x86_64.rpm
xen-dom0-libs-4.7.5-1.22.x86_64.rpm
xen-dom0-tools-4.7.5-1.22.x86_64.rpm
xen-hypervisor-4.7.5-1.22.x86_64.rpm
xen-libs-4.7.5-1.22.x86_64.rpm
xen-livepatch_4.7.5_1.21-1-1.x86_64.rpm
xen-tools-4.7.5-1.22.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

Hotfix XS75E006 – For XenServer 7.5

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.5.

All customers who are affected by the issues described in CTX239100 – Citrix XenServer 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** Yes
Baselines for Live Patch XS75E004
Revision History

Published on October 26, 2018

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the XenServer 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 XS75E006-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:

  1. Automated Updates
  2. Download update from Citrix
  3. 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:

  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 XS75E006.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. 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.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. 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.
  13. When the update is applied, click Finish to close the wizard.
  14. 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>XS75E006.iso

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

    76c2ec5c-c6dd-4c19-b825-f6c4391ef5a0

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

    xe update-pool-apply uuid=76c2ec5c-c6dd-4c19-b825-f6c4391ef5a0

    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=76c2ec5c-c6dd-4c19-b825-f6c4391ef5a0

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

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

    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.

  6. If the hotfix is applied successfully, restart each host in the pool, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS75E006.iso
Hotfix File sha256 73e9cea974ec6f8e8bf00d5aa755aadabb0f59b8a452f6da4ef666e38e705c82
Hotfix Source Filename XS75E006-sources.iso
Hotfix Source File sha256 413af08dc7797f752ba263389e6e34fd22d36c30e0de31c57b22022a0ea92e83
Hotfix Zip Filename XS75E006.zip
Hotfix Zip File sha256 3600ee4210b7bc16ef769633f3a3f36b1e655ced973bf0793c10cbeb470ae3e0
Size of the Zip file 31.42 MB

Files Updated

linux-firmware-20170622-3.2.noarch.rpm
microcode_ctl-2.1-26.xs1.x86_64.rpm
xen-dom0-libs-4.7.5-5.6.x86_64.rpm
xen-dom0-tools-4.7.5-5.6.x86_64.rpm
xen-hypervisor-4.7.5-5.6.x86_64.rpm
xen-libs-4.7.5-5.6.x86_64.rpm
xen-livepatch_4.7.5_5.5-1-1.x86_64.rpm
xen-tools-4.7.5-5.6.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts