VM’s Power State Does Not Update And Shows As “Unknown” After vCenter Server Reboots

This is an issue with Citrix hypervisor communication library plugin since version Xenapp/XenDesktop version 7.16.

When vCenter server goes alive after reboot i.e “https://<vCenter FQDN>/sdk” becomes accessible, BrokerHostingPlugin still fails to login the vCenter server with exception “The session is not authenticated.”.

CDF Traces from Delivery Controller

109369,0,2018/09/05 11:35:54:09721,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Attempting connection”,””

109370,0,2018/09/05 11:35:54:09729,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”***** Get Hypervisor Certificate for Connection to ‘https://vcenter.***.***/sdk‘ *****”,””

109371,1,2018/09/05 11:35:54:17750,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Certificate is untrusted: False”,””

109372,1,2018/09/05 11:35:54:17761,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Time elapsed to get the hypervisor certificate: 80ms”,””

109373,1,2018/09/05 11:35:54:17770,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”***** Login Connection – 0 to ‘https://vcenter.***.***/sdk‘ as ‘administrator’ *****”,””

109374,0,2018/09/05 11:35:54:49296,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”VMware plugin initialisation times: create service 0ms, content time 315ms, total 315ms”,””

109375,0,2018/09/05 11:35:54:49301,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Connected to ‘VMware vCenter Server 6.0.0 build-3018524′”,””

109376,0,2018/09/05 11:35:54:51280,1972,8384,1,BrokerHostingPlugin,,0,,1,Error,”System.Web.Services.Protocols.SoapException: The session is not authenticated.

109377,0,2018/09/05 11:35:54:51541,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Connection attempt threw exception System.Web.Services.Protocols.SoapException: The session is not authenticated.

109378,0,2018/09/05 11:35:54:51548,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Connection is still down”,””

109379,0,2018/09/05 11:35:54:51554,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Sleeping for 00:00:30 before trying to reconnect again”,””

Related:

  • No Related Posts

Driver Disk for Microsemi smartpqi 1.1.4-132 – For XenServer 7.1

Who Should Install this Driver Disk?

Customers running a Citrix XenServer 7.1 LTSR who use Microsemi’s smartpqi driver and wish to use the latest version of the following:

Driver Module Version
smartpqi 1.1.4-132

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Firmware requirements for this Driver Disk

Please ensure that your hardware is running firmware versions greater or equal to the ones specified below, according to the chipset of your particular device:

  • Microsemi Adaptec SmartHBA 2100 Adapters with Firmware 1.60 [0]
  • Microsemi Adaptec SmartRAID 3100 Adapters with Firmware 1.60 [0]

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the driver disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. After you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Note: If installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod smartpqi

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-microsemi-smartpqi-1.1.4_132.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=043e662c-d5a3-4d65-8ede-6df19e7f8554

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-microsemi-smartpqi-1.1.4_132.iso
File sha256 6b041541144d6b0605f6973495bea29511dc6f52aec86bc03a432cf06773a02f
Source Filename driver-microsemi-smartpqi-1.1.4_132-sources.iso
Source File sha256 44acad5ed431a3bfaf938daf808a59c3156a9ca34c1b44da59818784026b0e91
Zip Filename driver-microsemi-smartpqi-1.1.4_132.zip
Zip File sha256 a73a39847ec87c58ebec877b853ab1cfe1de0ec9064b8d4b6b1c1a93f8463967
Size of the Zip file 135.16 MB

RPMs Provided

RPM Name
microsemi-smartpqi-1.1.4_132-1.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer Supplemental Packs and the DDK Guide .

Related:

Driver Disk for Microsemi aacraid – 1.2.1.56008 – For XenServer 7.1

Who Should Install this Driver Disk?

Customers running a Citrix XenServer 7.1 LTSR who use Microsemi’s aacraid driver and wish to use the latest version of the following:

Driver Module Version
aacraid 1.2.1.56008

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Firmware requirements for this Driver Disk

Please ensure that your hardware is running firmware versions greater or equal to the ones specified below, according to the chipset of your particular device:

  • Microsemi Adaptec HBA 1000 Series Host Bus Adapters with Firmware 4.02 [0]
  • Adaptec RAID 8805 with Firmware 33263

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the driver disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. After you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Note: If installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod aacraid

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-microsemi-aacraid-1.2.1.56008.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=63cd3ae9-3ff6-43f7-8d51-e1e04f4d46cf

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-microsemi-aacraid-1.2.1.56008.iso
File sha256 6855c036b6fadbc691dae6fe81d7f7bee40ab23ad59984cc365a9e49f0e9e177
Source Filename driver-microsemi-aacraid-1.2.1.56008-sources.iso
Source File sha256 8beccd28d27c627a332abb58966853d9ebd32af7e6d62ac054eaad94515c898f
Zip Filename driver-microsemi-aacraid-1.2.1.56008.zip
Zip File sha256 120a940313699cf9ec7703caf739af40102eebc722806186bc7a456643a59672
Size of the Zip file 135.42 MB

RPMs Provided

RPM Name
microsemi-aacraid-1.2.1.56008-2.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer Supplemental Packs and the DDK Guide .

Related:

Unable to live migrate VMs on AMD hardware

If you are running XenServer on any AMD Family 15h or 16h CPU (including Opteron 42xx, 43xx, 62xx, 63xx and 63xxP processors), attempts to live migrate a VM to a host that has an updated microcode (version 0x600063e) can fail with a VM_INCOMPATIBLE_WITH_THIS_HOST error. This is due to a CPU feature incompatibility issue.

The affected processors with microcode 0x600063e (or later) do not have the Light-Weight Profiling (LWP) feature which was present in previous microcode versions. Therefore, if you live migrate a VM running on a host that has the LWP feature to a host that does not have this feature, migration fails with a VM_INCOMPATIBLE_WITH_THIS_HOST error.

Environment

This issue occurs on AMD processors noted above with an updated microcode (version 0x600063e). The microcode version can change when you update your BIOS, install a XenServer update, or upgrade your XenServer host to a newer version.

Note that the following XenServer updates contain affected AMD microcode versions:

Releases of XenServer up to XenServer 7.5 do not include the affected AMD microcode until you apply one of the updates listed above.

To check the CPU microcode version:

  1. On a XenServer host, open a local shell and log on as ‘root’.
  2. Run the following command:
# cat /proc/cpuinfo | grep microcode

Related:

Recommended instance allocation on Citrix ADC SDX 8900 series appliances

Disk allocation for SDX 8900 series appliances is improved with the following firmware releases and newer: 11.1 build 59.x, 12.0 build 58.x, and all 12.1 general availability builds.

With these improvements disk allocation takes place according to the chart at the bottom of this page.

The SDX 8900 series comes with a 240GB SSD Drive and 32 GB RAM. With the 240GB disk, 220GB are available for use. 60GB is used by the SDX Service Virtual Machine (SVM), 10 GB is used for factory partitions, 4GB is used by the Citrix Hypervisor (XenServer). The remainder of approximately 145GB is available for Citrix ADC VPX instances.

Below are guidelines on how much RAM you assign to an Citrix ADC VPX instance, and how much disk size you will use for each instance. If you want to deploy the maximum 7 instances, you must assign 4GB RAM or less to each instance.

RAM per VPX instance Disk Size
Up to 4GB RAM 20GB primary disk
4GB to 10GB RAM 20GB primary disk + 20GB secondary disk = 40 GB total
10 GB+ RAM 20 GB primary disk + 40GB secondary disk = 60 GB total

Related:

  • No Related Posts

How to Use host-cpu-tune to Fine tune XenServer 6.2.0 Performance

Pinning Strategies

  • No Pinning (default): When no pinning is in effect, the Xen hypervisor is free to schedule domain’s vCPUs on any pCPUs.
    • Pros: Greater flexibility and better overall utilization of available pCPUs.
    • Cons: Possible longer memory access times, particularly on NUMA-based hosts. Possible lower I/O throughput and control plane operations when pCPUs are overcommitted.
    • Explanation: When vCPUs are free to run on any pCPU, they may allocate memory in various regions of the host’s memory address space. At a later stage, a vCPU may run on a different NUMA node and require access to that previously allocated data. This makes poor utilization of pCPU caches and incur in higher access times to that data. Another aspect is the impact on I/O throughput and control plane operations. When more vCPUs are being executed than pCPUs that are available, the Xen hypervisor might not be able to schedule dom0’s vCPUs when they require execution time. This has a negative effect on all operations that depend on dom0, including I/O throughput and control plane operations.
  • Exclusive Pinning: When exclusive pinning is on effect, the Xen hypervisor pins dom0 vCPUs to pCPUs in a one-to-one mapping. That is, dom0 vCPU 0 runs on pCPU 0, dom0 vCPU 1 runs on pCPU 1 and so on. Any VM running on that host is pinned to the remaining set of pCPUs.
    • Pros: Possible shorter memory access times, particularly on NUMA-based hosts. Possible higher throughput and control plane operations when pCPUs are overcommitted.
    • Cons: Lower flexibility and possible poor utilization of available pCPUs.
    • Explanation: If exclusive pinning is on and VMs are running CPU-intensive applications, they might under-perform by not being able to run on pCPUs allocated to dom0 (even when dom0 is not actively using them).

Note: The exclusive pinning functionality provided by host-cpu-tune will honor specific VM vCPU affinity configured using the VM parameter vCPU-params:mask. For more information, refer to the VM Parameters section in the appendix of the XenServer 6.2.0 Administrator’s Guide.

Using host-cpu-tune

The tool can be found in /usr/lib/xen/bin/host-cpu-tune. When executed with no parameters, it displays help:

[root@host ~]# /usr/lib/xen/bin/host-cpu-tune

Usage: /usr/lib/xen/bin/host-cpu-tune { show | advise | set <dom0_vcpus> <pinning> [–force] }

show Shows current running configuration

advise Advise on a configuration for current host

set Set host’s configuration for next reboot

<dom0_vcpus> specifies how many vCPUs to give dom0

<pinning> specifies the host’s pinning strategy

allowed values are ‘nopin’ or ‘xpin’

[–force] forces xpin even if VMs conflict

Examples: /usr/lib/xen/bin/host-cpu-tune show

/usr/lib/xen/bin/host-cpu-tune advise

/usr/lib/xen/bin/host-cpu-tune set 4 nopin

/usr/lib/xen/bin/host-cpu-tune set 8 xpin

/usr/lib/xen/bin/host-cpu-tune set 8 xpin –force

[root@host ~]#

Recommendations

The total number of pCPUs and advise as follows:

# num of pCPUs < 4 ===> same num of vCPUs for dom0 and no pinning

# < 24 ===> 4 vCPUs for dom0 and no pinning

# < 32 ===> 6 vCPUs for dom0 and no pinning

# < 48 ===> 8 vCPUs for dom0 and no pinning

# >= 48 ===> 8 vCPUs for dom0 and excl pinning

The utility works in three distinct modes:

  1. Show: This mode displays the current dom0 vCPU count and infer the current pinning strategy.

    Note: This functionality will only examine the current state of the host. If configurations are changed (for example, with the set command) and the host has not yet been rebooted, the output may be inaccurate.

  2. Advise: This recommends a dom0 vCPU count and a pinning strategy for this host.

    Note: This functionality takes into account the number of pCPUs available in the host and makes a recommendation based on heuristics determined by Citrix. System administrators are encouraged to experiment with different settings and find the one that best suits their workloads.

  3. Set: This functionality changes the host configuration to the specified number of dom0 vCPUs and pinning strategy.

    Note: This functionality may change parameters in the host boot configuration files. It is highly recommended to reboot the host as soon as possible after using this command.

    Warning: Setting zero vCPUs to dom0 (with set 0 nopin) will cause the host not to boot.

Resetting to Default

The host-cpu-tune tool uses the same heuristics as the XenServer Installer to determine the number of dom0 vCPUs. The installer, however, never activates exclusive pinning because of race conditions with Rolling Pool Upgrades (RPUs). During RPU, VMs with manual pinning settings can fail to start if exclusive pinning is activated on a newly upgraded host.

To reset the dom0 vCPU pinning strategy to default:

  1. Run the following command to find out the number of recommended dom0 vCPUs:

    [root@host ~]# /usr/lib/xen/bin/host-cpu-tune advise

  2. Configure the host accordingly, without any pinning:
    • [root@host ~]# /usr/lib/xen/bin/host-cpu-tune set <count> nopin
    • Where <count> is the recommended number of dom0 vCPUs indicated by the advise command.
  3. Reboot the host. The host will now have the same settings as it did when XenServer 6.2.0 was installed.

Usage in XenServer Pools

Settings configured with this tool only affect a single host. If the intent is to configure an entire pool, this tool must be used on each host separately.

When one or more hosts in the pool are configured with exclusive pinning, migrating VMs between hosts may change the VM's pinning characteristics. For example, if a VM are manually pinned with the vCPU-params:mask parameter, migrating it to a host configured with exclusive pinning may fail. This could happen if one or more of that VM's vCPUs are pinned to a pCPU index exclusively allocated to dom0 on the destination host.

Additional commands to obtain information concerning CPU topology:

xenpm get-cpu-topology

xl vcpu-list

Related:

Driver Disk for Microsemi smartpqi 1.1.4-132 – For XenServer 7.X CR

Who Should Install this Driver Disk?

Customers running a Citrix XenServer Current Release 7.2 or later who use Microsemi’s smartpqi driver and wish to use the latest version of the following:

Driver Module Version
smartpqi 1.1.4-132

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Firmware requirements for this Driver Disk

Please ensure that your hardware is running firmware versions greater or equal to the ones specified below, according to the chipset of your particular device:

  • Microsemi Adaptec SmartHBA 2100 Adapters with Firmware 1.60 [0]
  • Microsemi Adaptec SmartRAID 3100 Adapters with Firmware 1.60 [0]

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the driver disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. After you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Note: If installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod smartpqi

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-microsemi-smartpqi-1.1.4_132.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=ed6639fb-a291-408b-bca9-6652e7c4266c

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-microsemi-smartpqi-1.1.4_132.iso
File sha256 62a9bc058fe9ea441e61a803506cadd7ed3d72d778526596ac2368c82f463693
Source Filename driver-microsemi-smartpqi-1.1.4_132-sources.iso
Source File sha256 9bbaea0095e8b17853350072881a1265b103ccd8c342672b127d6304ac63a77f
Zip Filename driver-microsemi-smartpqi-1.1.4_132.zip
Zip File sha256 7b4e31cafea8797551a40cfc9b79aeb7a849a80b343991f6912c9cb8cedfc014
Size of the Zip file 135.22 MB

RPMs Provided

RPM Name
microsemi-smartpqi-1.1.4_132-1.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer ® Supplemental Packs and the DDK Guide .

Related:

Driver Disk for Microsemi smartpqi 1.1.2-125 – For XenServer 7.x CR

Who Should Install this Driver Disk?

Customers running a Citrix XenServer 7.x Current Release who use Microsemi’s smartpqi driver and wish to use the latest version of the following:

Driver Module Version
smartpqi
1.1.2-125

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Firmware requirements for this Driver Disk

Please ensure that your hardware is running firmware versions greater or equal to the ones specified below, according to the chipset of your particular device:

  • Microsemi Adaptec SmartRAID 3100 Adapters with Firmware 1.32 [0]
  • Microsemi Adaptec SmartHBA 2100 Adapters with Firmware 1.32 [0]

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the driver disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code ISO is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod smartpqi

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-microsemi-smartpqi-1.1.2_125.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=119da241-7a63-42f1-852e-803a7fa5bbdb

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-microsemi-smartpqi-1.1.2_125.iso
File sha256 4ff3a0f63c1042a508c4f747b853d9ce1437d5ca380de1641e42b83bfac284e1
Source Filename driver-microsemi-smartpqi-1.1.2_125-sources.iso
Source File sha256 0e9a02a23b5416ce8631dfd405b64a985c616d43dad07e6be21c8867196bc4a3
Zip Filename driver-microsemi-smartpqi-1.1.2_125.zip
Zip File sha256 079a37b5fcfbf28a74b8484fc18407142b445ef38d34ff77bdaa515932fca472
Size of the Zip file 0.12 MB

RPMs Provided

RPM Name
microsemi-smartpqi-1.1.2_125-1.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer ® 7.2 Supplemental Packs and the DDK Guide.

Related:

Driver Disk for Microsemi aacraid – 1.2.1.56008 – For XenServer 7.x CR

Who Should Install this Driver Disk?

Customers running a Citrix XenServer Current Release 7.2 or later who use Microsemi’s aacraid driver and wish to use the latest version of the following:

Driver Module Version
aacraid 1.2.1.56008

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Firmware requirements for this Driver Disk

Please ensure that your hardware is running firmware versions greater or equal to the ones specified below, according to the chipset of your particular device:

  • Microsemi Adaptec HBA 1000 Series Host Bus Adapters with Firmware 4.02 [0]
  • Adaptec RAID 8805 with Firmware 33263

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the driver disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. After you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Note: If installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod aacraid

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-microsemi-aacraid-1.2.1.56008.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=fb34e49f-c66c-453f-9128-7c2f8f3eb93f

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-microsemi-aacraid-1.2.1.56008.iso
File sha256 17fd3d6bf413816771dab0f230eb172aa3d5623d1b004978a6ce54e95fcd086b
Source Filename driver-microsemi-aacraid-1.2.1.56008-sources.iso
Source File sha256 3c540b1da6558d5a3850c5a66469bb07f4dfe47d4a012e50f1621c074cacb70b
Zip Filename driver-microsemi-aacraid-1.2.1.56008.zip
Zip File sha256 0160e4ebc28c5f71a85104d92b37cc27e361e3219ec730a42069d19096335c83
Size of the Zip file 135.48 MB

RPMs Provided

RPM Name
microsemi-aacraid-1.2.1.56008-2.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer Supplemental Packs and the DDK Guide .

Related: