Troubleshooting tips for accessing XenServer hosted VDA’s console from Director

General Troubleshooting Tips

To support accessing XenServer hosted VDA’s console from Citrix Director, XenServer, XenApp /XenDesktop Delivery Controller, Citrix Director and Citrix Director Client where Citrix administrators logon to Citrix Director are modified. You can perform troubleshooting steps on the 4 involved components:

On the Citrix Director Client

  1. Make sure Citrix Director Client is network reachable to XenServer Host as well as Pool Master.
  2. You can use developer tools of a web browser, check the output logs on the Console tab, or check the response of the GetMachineConsoleUrl API on the Network tab. Normally after clicking Console besides VM name, you’ll see the GetMachineConsoleUrl API returns with Console ID, Host and Master address information, as follows (Take Firefox web developer tool as an example):
If no response after clicking Console besides the VM name, it most probably that GetMachineConsoleUrl failed. You can get the status code from web developer tool, for example:

This might be a transient issue, try to close the web browser and re-open it again.
On the Citrix Director Server

  1. Check system event viewer of Citrix Director Server for Warning or Error messages on Citrix Director Service, for example:

    User-added image
  2. Enable debug logging to get more detailed logging, you can refer to How to Enable Logging for Desktop Director for instructions. Look for “GetMachineConsole*” lines in Director log:
+++++++++++++++++++++++++++++++++++++++++

12/04/2017 17:29:11.7079 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] ENTRY: GetMachineConsoleUrl service called

12/04/2017 17:29:11.7079 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] GetMachineConsoleUrl(machineId=S-1-5-21-2349211030-2087978584-3527138389-1187 and SiteId = bbafdbe6-ebca-4864-9a8d-d38eb603e768 ) called…

12/04/2017 17:29:11.7079 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] No value for setting ‘Connector.Broker.Identity’. Using default ‘User’

12/04/2017 17:29:11.7079 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] GetConnector called. connectionAddress = ‘(http://xd716.penny.cn/Citrix/BrokerAdminService/v2,7.16.0.22)’

12/04/2017 17:29:11.7079 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] GetConnector returning …

12/04/2017 17:29:11.7079 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] GetMachine called. machineSid=S-1-5-21-2349211030-2087978584-3527138389-1187

12/04/2017 17:29:11.7079 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] GetObjects called

12/04/2017 17:29:11.7079 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] PowerShell equivalent: Get-BrokerMachine -SID S-1-5-21-2349211030-2087978584-3527138389-1187 -MaxRecordCount 1 -ReturnTotalRecordCount True

12/04/2017 17:29:11.7925 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] totalAvailableResultCount: 1

12/04/2017 17:29:11.7925 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] objects.length: 1

12/04/2017 17:29:11.7925 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] GetObjects returning

12/04/2017 17:29:11.7925 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] GetMachine returning.

12/04/2017 17:29:11.7925 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] Marking the Connector as active by removing it from failed connectors list

12/04/2017 17:29:11.7925 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] No value for setting ‘Connector.HostingUnitService.Identity’. Using default ‘User’

12/04/2017 17:29:11.7925 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] GetConnector called. connectionAddress = ‘(http://xd716.penny.cn/Citrix/HostContract/v2,7.16.0.22)’

12/04/2017 17:29:11.7925 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] GetConnector returning …

12/04/2017 17:29:11.7925 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] HostingUnitServiceConnector.GetMachineConsole called



12/04/2017 17:29:15.9368 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] HostingUnitServiceConnector.GetMachineConsole returning

12/04/2017 17:29:15.9368 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] Marking the Connector as active by removing it from failed connectors list

12/04/2017 17:29:15.9368 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] GetMachineConsoleUrl(machineId=S-1-5-21-2349211030-2087978584-3527138389-1187 and SiteId = bbafdbe6-ebca-4864-9a8d-d38eb603e768 ) returned…

12/04/2017 17:29:15.9368 : [t:105, s:d1lrlk2e3s3bxzc45uf5hxa5] EXIT: GetMachineConsoleUrl service returning

+++++++++++++++++++++++++++++++

On the Delivery Controller

You can get either CDF traces or text log of Host service on Delivery Controller, look for “GetMachineConsole*” lines Host service log, and then filter thread id to get the whole process log:


+++++++++++++++++++++++++++++++++++++++++

04/12/17 17:29:12.604 6996 0006 3740:HostLog:-> GetMachineConsole – Entry

04/12/17 17:29:12.604 6996 0006 3740:HostLog:-> Citrix.Host.Logic.GetMachineConsole – Entry

04/12/17 17:29:12.604 6996 0006 3740: HostInterService:Enter:WcfClientBase.CallAndRetry T: Citrix.InterService.DelegatedAdminApi.V2.IDelegatedAdminApiV2, TResult:System.Boolean

04/12/17 17:29:12.604 6996 0006 3740: HostInterService:Enter:WcfClientBase.VerifyMachineIsRegistered

04/12/17 17:29:12.604 6996 0006 3740: HostInterService:Enter:InterServiceManager.IsThisMachineRegistered computerSid:S-1-5-21-2349211030-2087978584-3527138389-1186

04/12/17 17:29:12.604 6996 0006 3740: HostInterService:Enter:InterServiceManager.InternalIsSidTrusted sid:S-1-5-21-2349211030-2087978584-3527138389-1186

04/12/17 17:29:12.604 6996 0006 3740: HostInterService:InterServiceManager.InternalIsSidTrusted isTrusted:True

04/12/17 17:29:12.604 6996 0006 3740: HostInterService:Enter:WcfClientBase.RegisteredCallAndRetry T: Citrix.InterService.DelegatedAdminApi.V2.IDelegatedAdminApiV2, TResult:System.Boolean

04/12/17 17:29:12.604 6996 0006 3740: HostInterService:WcfClientBase.RegisteredCallAndRetry CurrentServiceInstance:

04/12/17 17:29:12.604 6996 0006 3740: HostInterService:Enter:WcfClientBase.SelectNewConnection



04/12/17 17:29:12.858 6996 0006 3740: HostLog:7 Hypervisors found.

04/12/17 17:29:12.858 6996 0006 3740: HostLog:Hypervisor is: Citrix.Host.Logic.HypervisorAdapter

04/12/17 17:29:12.875 6996 0006 3740: HostLog:The connection address: http://10.71.124.122

04/12/17 17:29:12.875 6996 0006 3740: HostLog:The connection uid: 898d69ab-4a12-4e1e-bab7-7ecdde8a732b

04/12/17 17:29:12.875 6996 0006 3740: HostLog:The connection Name: xenrt

04/12/17 17:29:12.875 6996 0006 3740: HostLog:The username is : root

04/12/17 17:29:12.875 6996 0006 3740: HostLog:The connection is premise-based

04/12/17 17:29:12.875 6996 0006 3740: HostLog:The connection custom properties:

04/12/17 17:29:12.875 6996 0006 3740: HostLog:The connection zone is : c4991db6-cd06-4d28-b472-b0a26f42d14a, Primary

04/12/17 17:29:12.875 6996 0006 3740: HostLog:The connection has no volume service configuration.

04/12/17 17:29:12.875 6996 0006 3740: HostLog:The connection ssl thumbprints

04/12/17 17:29:15.903 6996 0006 3740: HostLog: Citrix.Host.Logic.GetMachineConsole – Exit

04/12/17 17:29:15.903 6996 0006 3740: HostLog: GetMachineConsole – Exit

+++++++++++++++++++++++++++++++



On XenServer Host

  1. You can check /var/log/xensource.log for console connection related problem:
+++++++++++++++++++++++++++++++

Dec 3 07:11:31 xrtuk-11-06 xapi: [debug|localhost|26306 ||mscgen] xapi=>xapi [label=”event.from”];

Dec 3 07:11:31 xrtuk-11-06 xapi: [debug|localhost|26307 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:event.from D:3a213de71420 created by task D:818552b352c5

Dec 3 07:11:52 xrtuk-11-06 xapi: [debug|localhost|26309 INET :::80|session.login_with_password D:4071df99be84|xapi] Success: local auth, user root from HTTP request from Internet with User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0

Dec 3 07:11:52 xrtuk-11-06 xapi: [ info|localhost|26309 INET :::80|session.login_with_password D:4071df99be84|xapi] Session.create trackid=32a7ec2118612aba83b3de362d6cbcd7 pool=false uname=root originator= is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49

Dec 3 07:11:52 xrtuk-11-06 xapi: [debug|localhost|26309 INET :::80|session.login_with_password D:4071df99be84|mscgen] xapi=>xapi [label=”pool.get_all”];

Dec 3 07:11:52 xrtuk-11-06 xapi: [debug|localhost|26310 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:pool.get_all D:03c9598d4a50 created by task D:4071df99be84

Dec 3 07:11:53 xrtuk-11-06 xenopsd-xc: [debug|localhost|4229 |Connection to VM console R:caee43407296|xenops_server] VM.stat 32ca60de-ff7e-4056-0a4a-492e5a9548dd

Dec 3 07:11:53 xrtuk-11-06 xapi: [debug|localhost|26311 INET :::80|Connection to VM console R:caee43407296|console] VM OpaqueRef:868081dc-1cd9-4ee9-9b37-f9137adf6745 console port: Some localhost:5901

+++++++++++++++++++++++++++++++
  1. You can also check how many VNC console connections for a specific VM by following steps:
    • Get dom_id of the target VM (VDA) by command list_domains|grep <VM_UUID>, for example:
[root@xrtuk-11-06 ~]# list_domains |grep 32ca60de-ff7e-4056-0a4a-492e5a9548dd

32 | 32ca60de-ff7e-4056-0a4a-492e5a9548dd | B H
  • Get the VNC server listening port by command netstat –lptn |grep qemu-dm-<DOMID>, for example:
[root@xrtuk-11-06 ~]# netstat -lptn|grep qemu-dm-32

tcp 0 0 127.0.0.1:5901 0.0.0.0:* LISTEN 21364/qemu-dm-32
  • Then you can check how many VNC connections to this port (5901, in this example) by command netstat –ano|grep <PORT_NUMBER>. In following example, there are two VNC connections to the same VM:
User-added image

Related:

Security Update for Citrix XenServer

Hotfixes have been released to address these issues. Citrix recommends that affected customers install these hotfixes as part of their normal patching schedule. The hotfixes can be downloaded from the following locations:

Citrix XenServer 7.2: CTX230237 – https://support.citrix.com/article/CTX230237

Citrix XenServer 7.1 LTSR CU1: CTX230236 – https://support.citrix.com/article/CTX230236

Customers using the LivePatching feature of Citrix XenServer 7.2 will not need to reboot servers to apply this hotfix. However, customers using Citrix XenServer 7.1 LTSR CU1 will need to reboot servers for this hotfix to be effective.

Related:

How to Reset root Password of NetScaler SDX Running on XenServer

This article describes how to reset the root password of NetScaler SDX running on XenServer.

Background

For both XenServer and the XenServer component of a NetScaler SDX, a lost root password can be overwritten through the use of “linux single user mode” access. The purpose of single user is to utilize physical access to the host, reboot it, pass in temporary kernel flags, and boot directly into the single user (root) shell. From there, the root password can be set to a known token. The host must be rebooted for the changes to take affect.

Points to Note

You will require physical access (iLO, DRAC, console, or physical console) to the XenServer to complete this procedure.

The following are some of the points to note before starting this procedure:

  • At least two reboots will be required to complete this procedure.
  • The entire process should take no more than 10 minutes.
  • Read the instructions in their entirety as there is a small window of time to interact with the boot process.

Related:

the vm manager connection is ok but no vm manager data

Hi I am having issues getting the VM manager to work as designed. I have 9.2.9 of ILMT and 9.5.6.63 for bigfix installed on Linux all in one server.
In the ILMT UI the VM manager has a status of OK. But yet the Capacity Data Completeness widget show 2 vm managers with no data.
I have been reading the various manuals, tech notes and websites to troubleshoot the issue with no success.
I see this error in the vtech folder;
2017-12-12:08:10:51 Supported virtualization not found
2017-12-12:08:10:51 Command: ‘virsh –readonly capabilities 2>/dev/null | cat | grep “domain type” | grep -i kvm | wc -l’ exited with 1 with output: ‘0’
2017-12-12:08:10:51 Command: ‘virsh –readonly capabilities 2>/dev/null | cat | grep “domain type” | grep -i xen | wc -l’ exited with 1 with output: ‘0’
2017-12-12:08:10:51 Command: ‘xl list 2>/dev/null | cat | wc -l’ exited with 127 with output: ‘0’
2017-12-12:08:10:51 Exiting.

Thanks, Eric

Related:

Agent installation in citrix – xenserver

Hi,
We are facing issue regarding installation of Bigfix/ILMT anent in Xenserver since long.
major issue is : We have been communicated from Cirix technical support that “Xenserver does not support the ‘installation’ of ANY 3rd party software on the hypervisor.” . can you suggest, Now how to proceed further with this ?

Thanks,

Koushik Adhikary

Related:

How to upgrade SDX11500 SVM from 10.1-123 to 11.1

Background

For 10.5 and previous releases, the NetScaler SDX appliance setup includes setting up XenServer hypervisor, its supplemental packs and hotfixes, the Management Service (SVM), NetScaler virtual machines (VPX instance), and LOM firmware. Each of these components has a different release cycle. Therefore, updating each component independently, as allowed by NetScaler SDX 10.5 and earlier releases, makes maintenance difficult. Updating each component separately also leads to unsupported combinations of components.

The Single bundle upgrade, available from 11.0 and later releases, combines all the components including the Management Service, and except the NetScaler image and LOM firmware in a single image file, called the NetScaler SDX image. Using this image, you can upgrade all the components in a single step, eliminating the chances of incompatibility between various components. Single bundle upgrade also ensures that your appliance is always running a version that is tested and supported by Citrix. Because all the SDX components are combined in a single file, the NetScaler SDX image file is significantly larger than the image files of NetScaler SDX release earlier than 11.0.

The file name of the image is of the format build-sdx-11.1-<build_number>.tgz. After the Management Service is upgraded to NetScaler SDX 11.1, the new GUI does not appear the options to upload the XenServer image file, supplemental packs, or hotfixes. This is because NetScaler SDX 11.0 does not support upgrading individual components.

If you are currently running version 10.5.66.x or later of the NetScaler SDX Management Service, you can use the NetScaler SDX 11.0 image file to upgrade the appliance. If your Management Service is running an older version, you must first upgrade it to version 10.5.66.x or later.

Upgrade process

Upgrade SDX to the latest version of 10.5 (e.g. at the time of writing the article it is build 67.10):

First, upgrade the SVM – NetScaler Service VM to 10.5 Build 67.10.

Then, upgrade the platform image – NetScaler SDX Platform Image 10.5 Build 8.1.

Upgrade SDX to version 11.1 using the SDX Bundle. The most current version at the moment is 11.1 56.15.

Other resources

Single Bundle Upgrade: https://docs.citrix.com/en-us/sdx/11/single-bundle-upgrade.html

Related:

Error: “One or more issues were detected with your licensing configuration” during XenApp/XenDesktop upgrade to 7.16


Verify that you have valid XenApp/XenDesktop licenses installed prior to upgrade, and that the SA date is 2017.1115 or newer. You can view this on the license server by logging on to the Citrix licensing administration console. If not, make sure you upgrade your CSS/SA or download and install renewal licenses on the license server. How to Download and Install Updated License Files after a renewal

Also, make sure that your License Server is version 11.14.01 (any build number)

If all licensing is in order, you can safely check the box next to Let me continue, and click Next.

Related:

Hotfix XS71E018 – For XenServer 7.1

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.1.

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

Information About this Hotfix

Component Details
Prerequisite None
Post-update tasks None
Content live patchable* No
Baselines for Live Patch None.
Revision History Published on Dec 01, 2017
* 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. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS71E018-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 section Applying Automated Updates in the XenServer 7.1 Installation Guide.

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

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

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

    8593b10e-8e6a-4efe-855f-0dc9dd1e0367

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

    xe update-pool-apply uuid=<UUID_of_file>

    Run the following command if you would like to apply the hotfix for a individual host

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

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

    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, carry out any specified post-update task on each host, starting with the master.

    Note: After applying the hotfix, customers must restart any VMs that were running before the hotfix was applied. Alternatively, you can migrate any running VMs to a host that has the hotfix already applied.

Files

Hotfix File

Component Details
Hotfix Filename XS71E018.iso
Hotfix File sha256 a42bde26878f93a99011ebbfca6771062ed5f119920fa5bfda29c93fa30c2bf9
Hotfix Source Filename XS71E018-sources.iso
Hotfix Source File sha256 620ead4d71f5be4e2e9d4500c794d50812a667827799bb9885f4b5b7516311bf
Hotfix Zip Filename XS71E018.zip
Hotfix Zip File sha256 5749e1c909a60bcee6e202cc1576a7ea2f934df5a627d0d5c9e446b8dbfd7ec5
Size of the Zip file 0.51 MB

Files Updated

xen-device-model-0.10.2.xs-1.3.x86_64.rpm

More Information

For more information see, XenServer 7.1 Virtual Machine User’s Guide.

If you experience any difficulties, contact Citrix Technical Support.

Related:

Hotfix XS72E012 – For XenServer 7.2

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.2.

All customers who are affected by the issues described in CTX230138 – 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* Yes
Baselines for Live Patch XS72E008, XS72E009
Revision History Published on Dec 01, 2017
* 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. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS72E012-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 section Applying Automated Updates in the XenServer 7.2 Installation Guide.

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

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 XS72E012.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. In addition, the Install Update wizard checks whether a live patch (this is an Enterprise Edition feature) is available for the hotfix and if the live patch can be successfully applied to the hosts. For more information, see Live Patching in XenServer in XenServer 7.2 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 requiredon 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 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>XS72E012.iso

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

    eb79b610-cfe7-4f68-88bf-c97101c4eb0a

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

    xe update-pool-apply uuid=<UUID_of_file>

    Run the following command if you would like to apply the hotfix for a individual host

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

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

    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, carry out any specified post-update task on each host, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS72E012.iso
Hotfix File sha256 3272760a708b5fdd47bcc2d00ab9964da9e42453664955279773c598f37c9134
Hotfix Source Filename XS72E012-sources.iso
Hotfix Source File sha256 b846da5ae1cb114e8751bcc74af7e88b7a54cf67a0ecad02f8e6ba7e5bd164b7
Hotfix Zip Filename XS72E012.zip
Hotfix Zip File sha256 f386f36dd36a7be8c1adfbd9ac2a0f33253c20aeefa62965ddcd5182a350f3ea
Size of the Zip file 2.05 MB

Files Updated

xen-hypervisor-4.7.2-2.8.x86_64.rpm
xen-livepatch_4.7.2_2.7-1-1.x86_64.rpm
xen-livepatch_4.7.2_2.6-2-1.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

Related: