WITHDRAWN: Hotfix XS70E067 – For XenServer 7.0

This hotfix introduces an issue that prevents newer versions of XenCenter from connecting to XenServer hosts that have XS70E067 applied. As a result, the hotfix was withdrawn on Jun 7, 2019.

Important: If you have already downloaded XS70E067, do not install it on your XenServer 7.0 hosts.

If you have already installed XS70E067, you will experience the following issues:

  • XenCenter 7.1 and later does not connect to XenServer 7.0 hosts that have XS70E067 applied and reports the following error: “This pool contains servers earlier than Citrix Hypervisor 7.0. Please use an earlier version of XenCenter to manage this pool.” To work around this issue, use XenCenter 7.0.1 to connect to these hosts.
  • XenServer 7.0 hosts with XS70E067 applied cannot be upgraded to XenServer 7.1. Do not attempt to upgrade these hosts to a later version of XenServer.

Citrix is working on a hotfix to supersede XS70E067 that will include a fix for the issues introduced by XS70E067.

Related:

  • No Related Posts

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.1 CU2 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 XS76E003 –

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

This hotfix also includes the following previously released hotfixes:

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 XS75E008 –

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

This hotfix also includes the following previously released hotfixes:

Content live patchable** No

XenServer 7.1 Cumulative Update 2 (XS71ECU2) must be installed by all customers running XenServer 7.1 CU1 as , since March 12 2019 no further hotfixes will be produced for XenServer 7.1 CU1.

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

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

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
Hotfix XS71ECU2001 – For XenServer 7.1 Cumulative Update 2

This hotfix resolves the following issue:

  • The XenServer host can experience a memory leak in dom0. This memory leak is triggered by invalid responses to FLOGI messages from connected FCoE equipment.
Content live patchable** Yes
Hotfix XS71ECU2003 – For XenServer 7.1 Cumulative Update 2

This hotfix resolves the following issues:

  • Depending on the guest OS and device, devices passed through to a guest might not function correctly due to missed interrupts.
Content live patchable** No
Hotfix XS71ECU2004 – For XenServer 7.1 Cumulative Update 2

This hotfix resolves the following issues:

  • If you attempt to reboot a Windows VM from XenServer at the same time as you attempt to reboot the Windows VM from within the VM, the reboot can fail with the following error: “You attempted an operation on a VM that needed to be in state ‘Running but was in state ‘Halted’.
  • Scheduled metadata backups can fail intermittently when the pool backup metadata VDI gets full. The default size of the pool backup metadata VDI has been increased to 500MiB.
  • A VM taking more than 30 seconds to shut down no longer leads to “Domain stuck in dying state after 30s.”
  • While applying a hotfix to a pool, if XAPI restarts on a pool member, it detaches the hotfix update from all hosts in the pool as part of clean-up operations. This can cause the hotfix to fail to apply to other pool members.
Content live patchable** No
Hotfix XS71ECU2007 – For XenServer 7.1 Cumulative Update 2

This hotfix resolves the following issues:

  • Improvements to VM performance and stability.
  • 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.
  • Windows VMs with the XenVBD driver installed can experience a high number of system interrupts when performing storage operations, especially if you are using fast storage and transferring large amounts of data.

This hotfix also includes the drivers required to support Windows Server 2019 VMs on XenServer 7.1 CU2.

Content live patchable** No
Hotfix XS71ECU2008 – For XenServer 7.1 Cumulative Update 2 All customers who are affected by the issues described in CTX251995 – Citrix XenServer Multiple Security Updates should install this hotfix.

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 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 XS70E065 – For XenServer 7.0

This hotfix resolves the following issues:

  • A race condition caused Windows VMs to hang repeatedly and give an error with Event ID 129: “StorPort detected a SRB timeout, and issued a reset”.
  • XenVBD can consume 100% of a vCPU and can block other processes from using that vCPU.
  • If a restart is performed without clicking on the Yes or No buttons of the restart to complete installation dialog box, the dialog box continues to appear even after restarting the VM.

This hotfix also includes the following previously released hotfixes:

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

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

This hotfix also includes the following previously released hotfixes:

Related:

  • No Related Posts

Hotfix ProfileMgmt_19_03_2001 for Profile Management 1903

Hotfix package name: ProfileMgmt_19_03_1000.zip

For: For computers running Profile Management 1903. System Requirements

Replaces: None

Date: April, 2019

Languages supported: English (US)

Readme version: 1.00

Readme Revision History

Version

Date

Change Description

1.00

April, 2019

Initial release

Important Disclaimer – Limited Release Hotfix

If the Download link is not available on this page and you wish to obtain this limited distribution release, visit our support site at http://www.citrix.com/support and open a support case using your Citrix account credentials, or contact your reseller at http://www.citrix.com/partners/locator.

Testing of this release was targeted only at the affected functionality, and regression and stress testing were minimal. Introduce this release to a test environment for evaluation before deploying it to a production environment.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CITRIX AND ITS SUPPLIERS MAKE AND YOU RECEIVE NO WARRANTIES OR CONDITIONS, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, AND CITRIX AND ITS SUPPLIERS SPECIFICALLY DISCLAIM WITH RESPECT TO THE HOTFIX ANY CONDITIONS OF QUALITY, AVAILABILITY, RELIABILITY, SECURITY, LACK OF VIRUSES, BUGS OR ERRORS, OR SUPPORT AND ANY IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT PERMITTED BY APPLICABLE LAW, NEITHER CITRIX, NOR ITS SUPPLIERS SHALL BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL, MULTIPLE, PUNITIVE OR OTHER DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF DATA, LOSS OF INCOME, LOSS OF OPPORTUNITY, LOST PROFITS, COSTS OF RECOVERY OR ANY OTHER DAMAGES), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, AND WHETHER OR NOT FOR BREACH OF CONTRACT, NEGLIGENCE OR OTHERWISE, AND WHETHER OR NOT CITRIX, ITS SUPPLIERS, OR LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Important Notes about This Release

Caution! This release may require you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

Where to Find Documentation

This document describes the issue(s) resolved by this release and includes installation instructions. For additional product information, including system requirements, see Profile Management 1903 on the Citrix Product Documentation site.

New Fixes in This Release

  1. With the Enable search index roaming for Outlook feature enabled, Profile Management might fail to mount the OutlookSearchIndex.vhdx file on logon. The issue occurs when a user uses the feature for the first time or the first time a user uses the feature after a profile reset. As a workaround, log off and log back on. [UPM-1658]

Fixes from Replaced Hotfixes

No hotfixes were replaced by this release.

Installing and Uninstalling this Release

Notes:

  • This release is packaged as a .zip file containing the replacement profilemgt.msi file. For more information about deploying msi files, see Microsoft article 884016 or visit the Microsoft Web site and search on keyword msiexec.
  • Caution: Downgrades, also known as rollbacks, from this upgrade are not supported and might leave your systems in an unstable state. This upgrade does not patch the existing installation – it fully replaces it with a new installation. As a result, uninstalling this package removes the entire component from the computer. If the need arises to revert to an earlier version of the product, you must uninstall this package and then reinstall the earlier version of the product. Reverting to an earlier version of the product might result in the loss of settings you configure while this upgrade is installed.
  • If the need arises to restore the original settings and functionality provided by this hotfix, you must uninstall the hotfix before reinstalling it according to the installation instructions below.
  • To install this package successfully, servers must not have registry modification restrictions in place.
  • This hotfix might or might not prompt you to restart the server when the installation or uninstallation is complete. You must restart the server for the installation to complete.

To install this hotfix:

  1. Copy the file to a shared folder on the network.
  2. Extract the compressed file and save the profilemgt.msi file on the computer you want to update.
  3. Run the .msi file.
  4. Restart the computer.

To uninstall this hotfix:

  1. From the Start menu, select Settings > Control Panel.
  2. In Control Panel, double-click Programs and Features.
  3. Highlight the hotfix you want to remove and click Uninstall.
  4. Follow the directions on-screen.

Related:

  • No Related Posts

Hotfix Install/Uninstall or XenApp Repair Ended Prematurely on XenApp 5.0/6.0/6.5

Installation of a hotfix, XenApp repair, or hotfix uninstall fails with “Error: Installation ended prematurely because of an error.”

User-added image

The following event might be logged in the Server Application Event Logs for a XenApp repair/uninstall “Event 1035, MsiInstaller: Windows Installer reconfigured the product. Product Name: Citrix XenApp <Version>. Product Language: 1033. Manufacturer: Citrix Systems, Inc. Reconfiguration success or error status: 1603.

User-added image

Related:

  • No Related Posts

XenServer 7.1 Cumulative Update 2

Who Should Install This Cumulative Update?

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.

Information About this Cumulative Update

Component Details
Prerequisite
  • XenServer 7.1 CU1.

  • Licensed customer with Customer Success Service

Post-update tasks Restart Host
Content live patchable* No
Revision History Published on December 12, 2018
* Available to Enterprise Customers.

Included in this Cumulative Update

This cumulative update includes the following previously released hotfixes.

This cumulative update also includes additional fixes. For a list of the issues resolved by XenServer 7.1 CU2, see the Citrix XenServer 7.1 Cumulative Update 2 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 XS71ECU2-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, it is recommended that you update your version of XenCenter to the latest available version for XenServer 7.1 CU 2.

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, seeApply Automated Updates.

For information about installing a cumulative update using the Download update from Citrix option, see Apply an updates to a pool.

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

    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>XS71ECU2.iso

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

    1dbfd41c-a53d-41e7-aa64-a8f39e0baac8

  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=XS71ECU2

    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 XS71ECU2.iso
Hotfix File sha256 64b9d387cfc79fb97245a2425babaa4f46ccf9edf4730cde18fea7fe954a0f42
Hotfix Source Filename XS71ECU2-sources.iso
Hotfix Source File sha256 e46f7d3fb31b8e4bafcd5a49c06ce7b0d55f486489efd618514452aafb6c4305
Hotfix Zip Filename XS71ECU2.zip
Hotfix Zip File sha256 7cb0130b2ac64e4c5c7ccbe57ea232ff1224888b0a4848d20d8ca0674614ba08
Size of the Zip file 277.16 MB

Files Updated

biosdevname-0.3.10-3.x86_64.rpm
blktap-3.5.0-xs.1+1.0_71.1.2.x86_64.rpm
broadcom-bnxt-en-1.5.5.p1-1.x86_64.rpm
busybox-1.22.1-2.x86_64.rpm
ca-certificates-2015.2.6-73.el7.noarch.rpm
citrix-crypto-module-1.0.2n-11.x86_64.rpm
dracut-033-360.el7.centos.xs13.x86_64.rpm
dracut-network-033-360.el7.centos.xs13.x86_64.rpm
ethtool-4.5-3.el7.x86_64.rpm
forkexecd-1.1.2-2.el7.centos.x86_64.rpm
glibc-2.17-106.el7_2.4.x86_64.rpm
glibc-common-2.17-106.el7_2.4.x86_64.rpm
gpumon-0.4.0-3.el7.centos.x86_64.rpm
guest-templates-json-1.1.4-1.noarch.rpm
guest-templates-json-data-linux-1.1.4-1.noarch.rpm
guest-templates-json-data-other-1.1.4-1.noarch.rpm
guest-templates-json-data-windows-1.1.4-1.noarch.rpm
guest-templates-json-data-xenapp-1.1.4-1.noarch.rpm
host-upgrade-plugin-1.1.3.1-1.x86_64.rpm
intel-e1000e-3.4.0.2-1.x86_64.rpm
kernel-4.4.27-600.1.12.x86_64.rpm
kexec-tools-2.0.4-32.x86_64.rpm
kpatch-0.3.2-4.x86_64.rpm
kpatch-4.4.0+2-modules-0.3.2-4.x86_64.rpm
kpatch-modules-0.3.2-4.x86_64.rpm
linux-guest-loader-2.0.2-1.noarch.rpm
linux-firmware-20170622-3.2.noarch.rpm
linux-guest-loader-data-2.0.2-1.noarch.rpm
message-switch-1.4.1-2.el7.centos.x86_64.rpm
microcode_ctl-2.1-26.xs1.x86_64.rpm
ocaml-xenops-tools-1.0.1-5.el7.centos.x86_64.rpm
openssl-1.0.2k-8.el7.x86_64.rpm
openssl-libs-1.0.2k-8.el7.x86_64.rpm
openssl-perl-1.0.2k-8.el7.x86_64.rpm
openvswitch-2.3.2-24.1.3.1.x86_64.rpm
pbis-open-8.2.2-1.7.2.x86_64.rpm
pbis-open-upgrade-8.2.2-4.x86_64.rpm
qlogic-fastlinq-8.10.11.0.p1-1.x86_64.rpm
rrd2csv-1.0.2-3.el7.centos.x86_64.rpm
rrdd-plugins-1.0.4-4.el7.centos.x86_64.rpm
security-tools-1.0.1-1.x86_64.rpm
sm-1.17.0-xs.2+1.0_71.1.6.x86_64.rpm
sm-cli-0.9.8-2.el7.centos.x86_64.rpm
sm-rawhba-1.17.0-xs.2+1.0_71.1.6.x86_64.rpm
squeezed-0.13.2-2.el7.centos.x86_64.rpm
stunnel_xs-4.56-6.el7.centos.xs4.x86_64.rpm
tzdata-2018c-1.el7.noarch.rpm
v6d-citrix-10.0.9-1.el7.centos.x86_64.rpm
vendor-drivers-1.0.0-1.x86_64.rpm
vendor-update-keys-1.3.6-2.noarch.rpm
vgpu-7.1.0.1-1.x86_64.rpm
vhd-tool-0.11.4-2.el7.centos.x86_64.rpm
xapi-storage-0.9.0-3.el7.centos.x86_64.rpm
xapi-core-1.14.45-2.x86_64.rpm
xapi-storage-script-0.13.0-2.el7.centos.x86_64.rpm
xapi-tests-1.14.45-2.x86_64.rpm
xapi-xe-1.14.45-2.x86_64.rpm
xcp-networkd-0.13.6-2.el7.centos.x86_64.rpm
xcp-python-libs-2.0.5-2.noarch.rpm
xcp-rrdd-1.2.0-4.el7.centos.x86_64.rpm
xencenter-7.1.3.6923-1.noarch.rpm
xenopsd-0.17.12-2.el7.centos.x86_64.rpm
xenopsd-xc-0.17.12-2.el7.centos.x86_64.rpm
xenopsd-xenlight-0.17.12-2.el7.centos.x86_64.rpm
xenops-cli-1.0.2-3.el7.centos.x86_64.rpm
xenserver-docs-7.1.0-17.noarch.rpm
xenserver-firstboot-1.0.1.3-1.noarch.rpm
xenserver-pv-tools-7.2.101-1.noarch.rpm
xenserver-release-7.1.2-2.x86_64.rpm
xenserver-release-config-7.1.2-2.x86_64.rpm
xen-dom0-libs-4.7.6-1.26.x86_64.rpm
xen-device-model-0.10.2.xs-1.3.x86_64.rpm
xen-dom0-tools-4.7.6-1.26.x86_64.rpm
xen-hypervisor-4.7.6-1.26.x86_64.rpm
xen-libs-4.7.6-1.26.x86_64.rpm
xen-tools-4.7.6-1.26.x86_64.rpm
xsconsole-10.0.1-1.x86_64.rpm
xs-obsolete-packages-1-1.noarch.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

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

Netstat.db-wal grows out of control again at 14.0 MP2

I need a solution

We have a same issue like before. The netstat.db-wal very large file and continues to increase in size. We don’t know the permanent solution (temporary solution, if stop the smc and after we start again).
I know that, there  were some article in this topic (https://support.symantec.com/en_US/article.TECH239793.html), but our case is a little bit differece. 
Our SEP is working in the ABB800xa DCS (distributed control system) automation system, and we have not internet connection. We need to use some special policy (approved by ABB),and need to update by manualy.
My question that, how we can update the SEP (how we need to download and install the hotfix )?

There is the version of my SEP:

  

Thank you for the answer!!

0

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