Supported Hypervisors for Virtual Desktops (XenDesktop) and Provisioning Services

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

Citrix is committed to ensuring that our products function with the latest VMware, Microsoft, and Citrix Hypervisors.

Click the following products to view the supported configurations matrix.

XenServer – Provisioning Services XenServer – XenDesktop
vSphere – Provisioning Services vSphere – XenDesktop
SCVMM – Provisioning Services SCVMM – XenDesktop
Nutanix Acropolis – Provisioning Services Nutanix Acropolis – XenDesktop

Note:

  • This matrix indicates supported configurations of Virtual Desktops (XenDesktop) and Provisioning Services with various hypervisor solutions. When Yes is listed for a combination, it means Citrix will provide technical support to assist with any issues encountered. Any known issues and requirements for certain combinations are indicated with notes.
  • XenApp 6.0 and 6.5 are hypervisor agnostic. If XenApp is deployed through Citrix Provisioning Services, refer to the Provisioning Services product support for the hypervisor.
  • This article will be updated periodically as new information becomes available.

What has changed from the last release of the matrix?

  • Added support for vSphere 6.7 update 2.
  • Added support for Citrix Hypervisor (XenServer) 8.0


Citrix Hypervisor (XenServer) – Provisioning Services (PVS)

Supported Hypervisors / XenServer Provisioning Services
1906/1903 1811 7.15 LTSR 7.6 LTSR
Citrix Hypervisor 8.0 Yes No Yes(With CU3 or higher) No
XenServer 7.6 Yes Yes Yes No
XenServer 7.5 No No Yes No
XenServer 7.1 LTSR Yes(CU2 only) Yes(CU2 only) Yes(Up to CU2) Yes(Up to CU2)
XenServer 7.0 No No No Yes

Go back to top

Citrix Hypervisor (XenServer) – Virtual Desktops (XenDesktop)

Supported Hypervisors

/XenServer
Virtual Desktops (XenDesktop)
1906/1903 1811 7.15 LTSR 7.6 LTSR
Citrix Hypervisor 8.0 Yes No Yes(With CU3 or higher) No
XenServer 7.6 Yes Yes Yes No
XenServer 7.5 No No Yes No
XenServer 7.1 LTSR Yes(CU2 only) Yes(CU2 only) Yes(Up to CU2) Yes(Up to CU2)
XenServer 7.0 No No No Yes

Go back to top


vSphere – Provisioning Services (PVS)

Note:

  • Citrix performs compatibility tests only with the major updates of VMware vSphere, like Update 1, 2 and so on. The minor updates like 1a, 1b, 2a and so on are not tested, however they are expected to work fine.
  • Testing of updates for the earlier version of VMware vSphere might be limited, as priority is given to the updates of the current version. When using earlier releases of these products, Citrix recommends validating product updates for proper functionality and interoperability in a test environment first before updating production environments.
Supported Hypervisors / vSphere Provisioning Services
1906/1903/1811 7.15 LTSR 7.6 LTSR
vSphere 6.7 (Up to update 2) Supported. Refer to CTX235513

for more details
(CU3 or higher) No
vSphere 6.5

(Up to update 2)
Supported.

Refer to CTX219808

for more details
Supported.

Refer to CTX219808
Supported.

Refer to CTX219808
vSphere 6

(Up to update 3)
Supported.

Refer to CTX200969

for more details
Supported.

Refer to CTX200969

for more details
Supported.

Refer to CTX200969

for more details
vSphere 5.5

(Up to update 3)
Supported.

Refer to CTX140135

for more details
Supported.

Refer to CTX140135

for more details
Supported.

Refer to CTX140135

for more details

Go back to top

vSphere – Virtual Desktops (XenDesktop)

Supported Hypervisors

/vSphere
Virtual Desktops (XenDesktop)
1906/1903/1811 7.15 LTSR 7.6 LTSR
vSphere 6.7 (Up to Update 2) Supported. Refer to CTX235513

for more details
CU3 or higher No
vSphere 6.5 (Up to update 2) Supported.Refer to CTX219808

for more details
Supported.Refer to CTX219808

for more details
Supported.Refer to CTX219808

for more details
vSphere 6 (Up to update 3) Supported.Refer to CTX200969

for more details
Supported.Refer to CTX200969

for more details
Supported.Refer to CTX200969

for more details
vSphere 5.5 (Up to update 3) Supported.Refer to CTX140135 for more details Supported.Refer to CTX140135for more details Supported.Refer to CTX140135for more details

Go back to top

SCVMM – Provisioning Services (PVS)

Supported Hypervisors / SCVMM Provisioning Services
1906/1903/1811 7.15 LTSR 7.6 LTSR
SCVMM 2016 Yes Yes No
SCVMM 2012 R2 Yes Yes Yes
SCVMM 2012 SP1 Yes Yes Yes
SCVMM 2012 Yes Yes Yes

Go back to top

SCVMM – Virtual Desktops (XenDesktop)

Supported Hypervisors / SCVMM Virtual Desktops (XenDesktop)
1906/1903/1811 7.15 LTSR 7.6 LTSR
SCVMM 2016 Yes Yes No
SCVMM 2012 R2 Yes Yes Yes
SCVMM 2012 SP1 Yes Yes Yes
SCVMM 2012 Yes Yes Yes

Go back to top

Nutanix Acropolis – Provisioning Services (PVS)

Supported Hypervisors / Nutanix Acropolis Provisioning Services
1906/1903/1811 7.15 LTSR 7.6 LTSR
Acropolis Operating System (AOS) 5.5 or later Yes Yes No

Go back to top

Nutanix Acropolis – Virtual Desktops (XenDesktop)

Supported Hypervisors / Nutanix Acropolis XenDesktop
1906/1903/1811 7.15 LTSR 7.6 LTSR
Acropolis Operating System (AOS) 4.6.1.x or later Supported. Refer to CTX202032

for more details.
Supported. Refer to CTX202032

for more details.
Supported. Refer to CTX202032

for more details.

Go back to top

Additional Resources

Related:

  • No Related Posts

Citrix Hypervisor Hardware Compatibility List Explained

This article provides an understanding of the Citrix Hypervisor Hardware Compatibility List (HCL). This article also contains information about how products get qualified for inclusion in the HCL and what listing in the HCL represents from a support perspective.

Background

Citrix maintains a Hardware Compatibility list for Citrix Hypervisor containing information about which hardware and software components are currently certified and supported for use with Citrix Hypervisor.

Because of the use of industry-standard open source device drivers in Citrix Hypervisor, the actual hardware compatibility for Citrix Hypervisor is broader than what is listed on the HCL. For servers and storage not specifically listed on the HCL, Citrix provides a self-certification test kit and program. The self-certification test kit includes tools and processes to follow for certifying specific servers and storage, and should be completed with the assistance of a Citrix Hypervisor Systems Engineer from Citrix or a Citrix Solution Provider. Completed self-certification test documentation can be e-mailed to CitrixReady@citrix.com. Once the submission has been reviewed and accepted by the Citrix Hypervisor HCL team, the hardware is added to the HCL and is eligible for full support.

How does Hardware Qualify for Inclusion in the Citrix Hypervisor HCL

The Citrix Ready program is used to qualify hardware for inclusion on the Citrix Hypervisor HCL.

Users and vendors are encouraged to submit the configurations of systems on which they have successfully installed Citrix solutions to share the information with the Citrix Ready community verified site.

Verification Test Kits and Forms for Citrix Hypervisor can be downloaded from http://citrix.com/partner-programs/citrix-ready/test.html.

The following test kits are available to allow vendors to demonstrate the compatibility of their computer systems with Citrix Hypervisor:

  • Citrix Hypervisor GPU Self-Test Kit

  • Citrix Hypervisor Hardware Test Kit

  • Citrix Hypervisor Storage Hardware Test Kit

  • Citrix Hypervisor hclIntegrated ISV Self-Certification Kit

When the Citrix Ready team has reviewed the submissions, they will consider including the tested hardware on the HCL. For some hardware and software components, Citrix will undertake to qualify the component for inclusion on the HCL.

Support Policy for Components not on the HCL

Hardware that is included on the HCL is fully supported by Citrix. For hardware or software not included on the HCL, Citrix provides best effort support.

When providing best effort support, Citrix attempts to address and resolve a reported issue and Citrix will try to assess if the issue directly relates to the unsupported components in that environment. To assist in making that determination, Citrix might ask customers to attempt to reproduce an issue using supported hardware and software. If the issue is found to be related to the unsupported components and that a resolution would require an enhancement to Citrix products that are beyond the scope of a support engagement, Citrix reserves the right to close the support case without providing a solution. In these circumstances, Citrix can log a product enhancement with its engineering teams as part of the case closedown. The implementation of the enhancement is not guaranteed and is at the discretion of our product management teams.

If during the analysis and troubleshooting of the reported issue, Citrix determines that the issue is related to an issue with a component provided by a third party vendor, Citrix attempts to find a workaround for the issue. If a workaround is not possible, Citrix might ask the customer to open a support incident with the third-party vendor to allow parallel troubleshooting to take place. If in the end, the issue is determined to be only addressable by the third party vendor, and in addition, that vendor refuses to provide any workaround because they do not support interoperability with our technology, then Citrix reserves the right to close the case without providing a resolution.

Related:

  • No Related Posts

How to license Citrix Hypervisor versions 5.6 and higher

Upgrading Citrix Hypervisor 5.6-6.1

Free Citrix Hypervisor 6.2

Installation of license for Citrix Hypervisor 6.2

Retail Citrix Hypervisor


Upgrading Citrix Hypervisor 5.6-6.1

Note: Free Citrix Hypervisor 5.6-6.1 is no longer available; only upgrades.
  1. To upgrade 5.6 – 6.1 software, refer to: https://activate.vmd.citrix.com

Free Citrix Hypervisor 6.2

With the release of Citrix Hypervisor 6.2, Citrix has unlocked all features in the free version and removed the need for a license. To obtain the free version, follow the below steps:

  1. Go to www.xenserver.org
  2. Select the Software link at the top of the page
  3. The next page provides all downloads applicable to Citrix Hypervisor, Select the media desired
  4. Save the media on the desktop and proceed to install.


Installation of license for Citrix Hypervisor 6.2 Free version

There is no license to install therefore there will be no need for a license. To view the system and verify there is no license, follow the below steps:

  1. Open XenCenter
  2. Navigate to the Tools menu and click License Manager
  3. This will show the license manager server option as Unsupported

Retail Citrix Hypervisor editions

There are two types of Citrix Hypervisor editions available which uses retail licensing. The types of hypervisor editions are Citrix Hypervisor Standard Edition, and Citrix Hypervisor Premium Edition. All Citrix Hypervisor editions licenses have to be added to a separate Citrix Licensing Server. The license files are maintained and controlled using Citrix License Administrative (LAC) console

Each host in a resource pool must be individually licensed. (For example, if you are supporting four hypervisor hosts in a resource pool, you must configure the license type to use on each of the four hosts separately.) As a result, license settings are configured on each host in the pool. However, in XenCenter, you can select multiple hosts at once in the License Manager and apply the same settings to them.


Tasks required to License Citrix Hypervisor retail editions

Follow the below tasks to license Citrix Hypervisor retail editions:

  1. Create a Citrix license server. Citrix Hypervisor release requires the Citrix License Server, version 11.6.1 or higher http://support.citrix.com/proddocs/topic/licensing-1110/lic-install.html

  2. Download and add the Citrix Hypervisor license file to the Citrix License Server CTX130884-How to Download the Citrix Hypervisor License File from My Account Portal / CTX126338-How to Add Allocated License Files to the License Administration Console.

  3. Configure each Citrix Hypervisor host to use the Citrix License Server that is hosting the license you allocated for it CTX130884-How to Download the Citrix Hypervisor License File from My Account Portal / CTX126338-How to Add Allocated License Files to the License Administration Console.

Retail Licensing for Citrix Hypervisor activation using License Manager in XenCenter

Follow the below procedure to activate Citrix Hypervisor using License Manager in XenCenter:

  1. Open XenCenter. Click Tools and select License Manager.
  2. The License Manager pop up box is displayed. Select required hosts (you can select more than one host file) and Click Assign License.
  3. The Apply License dialog box is displayed. Under the License Edition section, select the type of your hypervisor (For example, if you have Citrix Hypervisor Premium Edition, click on the radio button against it).
  4. Under License Server section, enter the name of the server in Name field (by default, it will have Local host text, Delete it and enter the name of the server) and port number of the server in Port Number field.
Note: If you have changed the port on the Citrix License Server, specify the changed port number in the Port Number field. If you have not changed the port, leave the default value 27000 as is. 27000 is the default port number used by Citrix products.
  1. Click OK.
  2. The licensing file will be associated with Citrix Hypervisor and the server is ready to use.

Related:

App Layering: Machine Time on a Published Image is Wrong at First Boot

You can always manually set the time once the machine starts, but that might be a pain to remember to do every time you publish a new image.

The initial clock time in Windows on a physical machine comes from a battery-powered clock on the motherboard (called TOD for Time Of Day), which is set to the local time in Windows’ current timezone. In a virtual machine, the virtualized TOD clock is set by the hypervisor at bootup. Since hypervisors normally know the time in GMT rather than a local timezone, your hypervisor has to know what “local time” is for your Windows instance in your virtual machine before it powers on. If the hypervisor doesn’t know the conversion factor for the VM’s local timezone, the initial time can be off by hours. Hypervisors learn the machine’s local time zone pretty quickly, but it means that the first boot for any VM is usually wrong.

In a published App Layering image, unless your template is derived from a VM that was originally a full Windows machine set to the correct timezone, the first boot usually has bad clock time. However, if your Platform Layer was added to the domain, your published VM should also have the correct information for how to sync its clock with the Domain Controller.

So make sure your Platform Layer was joined to the domain, so it can immediately correct the clock discrepancy.

Otherwise, consider setting this registry key so that Windows will treat the motherboard clock as being in UTC rather than the local timezone:

[HKEY_LOCAL_MACHINESystemCurrentControlSetControlTimeZoneInformation]

“RealTimeIsUniversal”=DWORD 1

Some hypervisors store the local timezone offset for a VM as a virtual motherboard resource. When Windows is running, every time it updates the clock time, it sets the motherboard resource to be the correct time. This is how your hypervisor finds out what the timezone offset for this VM is: because Windows is always writing local time to the motherboard, all your hypervisor has to do is compare the motherboard resource for the TOD clock to the hypervisor’s own clock. That timezone offset is an attribute of the VM itself, not part of Windows and not part of the virtual disk.

For instance, in vSphere, the time-of-day offset can be set as a parameter in the VMX (or VMTX) file. You can force the CMOS TOD clock’s offset to be initialized to a specific value at power on. To do so, set the option rtc.diffFromUTC in the virtual machine’s .vmx/.vmtx configuration file to a value in seconds. For example, setting rtc.diffFromUTC = 0 sets the clock to UTC at power on, while setting rtc.diffFromUTC = -25200 sets it to Pacific Daylight Time, seven hours earlier than UTC.

Note that Nutanix does not currently notice and record the time zone offset of a VM. You would need to set it manually. See this thread, for instance:

https://next.nutanix.com/installation-configuration-23/windows-vm-time-issues-22562

It may be worthwhile to generate a new template for your Connector, by having (or building) a Windows VM that has booted in the correct time zone. If you have a template you want to continue using, for instance, convert it to a VM, attach a bootable Windows disk (or boot from PVS or something like that – it’s just important that Windows run on this machine), power the machine on, and set the clock correctly. When you adjust the clock, Windows writes it to the motherboard, and your hypervisor records the offset in the virtual machine parameters. Then you can shut the machine down, remove any extra disks, and convert it back to a template.

You can also just take a working Windows machine with a correct local time, shut it down, clone it, remove any extra disks, and convert that to a VM template. This is one good reason to make a template out of a clone of your original Gold VM that you imported your OS Layer from: it already has all the virtual hardware parameters you want, including the local clock offset. Now that your template includes the current timezone offset, your hypervisor will be able to set the initial motherboard TOD clock correctly, meaning Windows has the correct time immediately and doesn’t need to wait for a jump when AD comes in to set the clock.

Configure your Connector to use this template so that newly published images will be correct. If you are using PVS, you should also use this template to build your Target Machines so that the virtual hardware of your Target Machines matches the hardware your layers were built from, including the local timezone offset.

Note that it’s also possible to have your hypervisor’s internal clock wrong. Also, your PVS server will try to set the machine’s clock based on the PVS server’s local clock. If any of these are wrong, you will need to get them synched as well.

Related:

Supported Hypervisors for XenDesktop and Provisioning Services

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

Citrix is committed to ensuring that our products function with the latest VMware, Microsoft, and Citrix Hypervisors.

Click the following products to view the supported configurations matrix.

XenServer – Provisioning Services XenServer – XenDesktop
vSphere – Provisioning Services vSphere – XenDesktop
SCVMM – Provisioning Services SCVMM – XenDesktop
Nutanix Acropolis – Provisioning Services Nutanix Acropolis – XenDesktop

Note:

  • This matrix indicates supported configurations of XenDesktop and Provisioning Services with various hypervisor solutions. When Yes is listed for a combination, it means Citrix will provide technical support to assist with any issues encountered. Any known issues and requirements for certain combinations are indicated with notes.
  • XenApp 6.0 and 6.5 are hypervisor agnostic. If XenApp is deployed through Citrix Provisioning Services, refer to the Provisioning Services product support for the hypervisor.
  • This article will be updated periodically as new information becomes available.

What has changed from the last release of the matrix?

  • Removed XenServer versions that are not supported.
  • Updated CU for XenServer 7.1 LTSR


XenServer – Provisioning Services (PVS)

Supported Hypervisors / XenServer Provisioning Services
1811/1903 1808 7.15 LTSR 7.6 LTSR
XenServer 7.6 Yes Yes Yes No
XenServer 7.5 No Yes Yes No
XenServer 7.1 LTSR Yes(CU2 only) Yes(Up to CU2) Yes(Up to CU2) Yes(Up to CU2)
XenServer 7.0 No No No Yes

Go back to top

XenServer – Virtual Desktops (XenDesktop)

Supported Hypervisors

/XenServer
Virtual Desktops (XenDesktop)
1811/1903 1808 7.15 LTSR 7.6 LTSR
XenServer 7.6 Yes Yes Yes No
XenServer 7.5 No Yes Yes No
XenServer 7.1 LTSR Yes(CU2 only) Yes(Up to CU2) Yes(Up to CU2) Yes(Up to CU2)
XenServer 7.0 No No No Yes

Go back to top


vSphere – Provisioning Services (PVS)

Note:

  • Citrix performs compatibility tests only with the major updates of VMware vSphere, like Update 1, 2 and so on. The minor updates like 1a, 1b, 2a and so on are not tested, however they are expected to work fine.
  • Testing of updates for the earlier version of VMware vSphere might be limited, as priority is given to the updates of the current version. When using earlier releases of these products, Citrix recommends validating product updates for proper functionality and interoperability in a test environment first before updating production environments.
Supported Hypervisors / vSphere Provisioning Services
1903/1811/1808/7.18 7.15 LTSR 7.14/7.16/7.17 7.6 LTSR
vSphere 6.7 (Up to update 1) Supported. Refer to CTX235513

for more details
Supported with CU3 No No
vSphere 6.5

(Up to update 2)
Supported.

Refer to CTX219808

for more details
Supported.

Refer to CTX219808
Supported.

Refer to CTX219808
Supported.

Refer to CTX219808
vSphere 6

(Up to update 3)
Supported.

Refer to CTX200969

for more details
Supported.

Refer to CTX200969

for more details
Supported.

Refer to CTX200969

for more details
Supported.

Refer to CTX200969

for more details
vSphere 5.5

(Up to update 3)
Supported.

Refer to CTX140135

for more details
Supported.

Refer to CTX140135

for more details
Supported.

Refer to CTX140135

for more details
Supported.

Refer to CTX140135

for more details

Go back to top

vSphere – Virtual Desktops (XenDesktop)

Supported Hypervisors

/vSphere
Virtual Desktops (XenDesktop)
1903/1811/1808/7.18 7.15 LTSR 7.14/7.16/7.17 7.6 LTSR
vSphere 6.7 (Up to Update 1) Supported. Refer to CTX235513

for more details
Supported with CU3 No No
vSphere 6.5 (Up to update 2) Supported.Refer to CTX219808

for more details
Supported.Refer to CTX219808

for more details
Supported.Refer to CTX219808

for more details
Supported.Refer to CTX219808

for more details
vSphere 6 (Up to update 3) Supported.Refer to CTX200969

for more details
Supported.Refer to CTX200969

for more details
SupportedRefer to CTX200969

for more details
Supported.Refer to CTX200969

for more details
vSphere 5.5 (Up to update 3) Supported.Refer to CTX140135 for more details Supported.Refer to CTX140135for more details Supported.Refer to CTX140135for more details Supported.Refer to CTX140135for more details

Go back to top

SCVMM – Provisioning Services (PVS)

Supported Hypervisors / SCVMM Provisioning Services
1903/1811/1808 7.18 / 7.17 / 7.16 / 7.15 LTSR 7.14 7.6 LTSR
SCVMM 2016 Yes Yes Yes No
SCVMM 2012 R2 Yes Yes Yes Yes
SCVMM 2012 SP1 Yes Yes Yes Yes
SCVMM 2012 Yes Yes Yes Yes

Go back to top

SCVMM – Virtual Desktops (XenDesktop)

Supported Hypervisors / SCVMM Virtual Desktops (XenDesktop)
1903/1811/1808 7.18 / 7.17 / 7.16 / 7.15 LTSR 7.14 7.6 LTSR
SCVMM 2016 Yes Yes Yes No
SCVMM 2012 R2 Yes Yes Yes Yes
SCVMM 2012 SP1 Yes Yes Yes Yes
SCVMM 2012 Yes Yes Yes Yes

Go back to top

Nutanix Acropolis – Provisioning Services (PVS)

Supported Hypervisors / Nutanix Acropolis Provisioning Services
1903/1811/1808 7.18 / 7.17 / 7.16 / 7.15 LTSR / 7.14 7.6 LTSR
Acropolis Operating System (AOS) 5.5 or later Yes Yes No

Go back to top

Nutanix Acropolis – Virtual Desktops (XenDesktop)

Supported Hypervisors / Nutanix Acropolis XenDesktop
1903/1811/1808 7.18 / 7.17 / 7.16 / 7.15 LTSR 7.14/7.6 LTSR
Acropolis Operating System (AOS) 4.6.1.x or later Supported. Refer to CTX202032

for more details.
Supported. Refer to CTX202032

for more details.
Supported. Refer to CTX202032

for more details.

Go back to top

Additional Resources

Related:

  • No Related Posts

Reporter | Please help to confirm information

I need a solution

Dear  All,

  I have got question from customer as  below. please help to recommend.

1. Does a reporter support ESXi hypervisor (free edition) ?

2. In case a customer using ProxySG-VA, is it possible to install on shared storage ? [SAN, NAS]
3. For management center, does it has a feature likes admin over-write protect ?
4. Can we set delegate user for reporter via management center ?
5. For management center, is it possible to set delegate user per ASG/Proxy-SG device ?

Best Regards,

CR

0

Related:

  • No Related Posts

How to pin Citrix Hypervisor Virtual CPUs to specific Physical CPUs

Citrix Hypervisor maps vCPUs to pCPUs by default in a semi-even way to distribute VM load on the host. In some cases it may be needed to have a specific mapping, for example, if some VMs will be CPU intensive while other wont, the intensive VMs can be mapped to exclusive physical CPUs while the others share resources. This can lead to performance improvements in the Hypervisor.

The following example will be used to change hard affinity. This means where the vCPU is allowed to run. In this sense, once a vCPU is pinned to a pCPU with hard affinity, the vCPU won’t be able to run in any other pCPU.

Soft affinity is used to define where does the vCPU prefers to run but it doesn’t restrict where it is allowed to run.

To determine which type of mapping to use, analyze the type of workload that the guest VMs are going to be running. Ultimately the best way to determine the best mapping is through testing different configurations with real workloads and observing the results. There is not a perfect ratio since workloads change depending on many factors, such as OS type, patches, apps run by users, employee work schedules, etc.

Related:

  • No Related Posts

VxRail: Migration of VMs from host fails with “The target host does not support the virtual machine’s current hardware requirements”

Article Number: 524619 Article Version: 3 Article Type: Break Fix



VxRail Appliance Family

When attempting to migrate VMs from a certain host in the cluster, the following compatibility error is encountered in the migration wizard:

The target host does not support the virtual machine’s current hardware requirements.

To resolve CPU incompatibilities, use a cluster with Enhanced vMotion Compatibility (EVC) enabled. See KB article 1003212.

com.vmware.vim.vmfeature.cpuid.ssbd

com.vmware.vim.vmfeature.cpuid.stibp

com.vmware.vim.vmfeature.cpuid.ibrs

com.vmware.vim.vmfeature.cpuid.ibpb

The above instructions are related to the new Intel Spectre/Meltdown Hypervisor-assisted Guest Mitigation fixes.

CPU features can be compared on the affected host and the other hosts via the following:

> Host-01 (affected):$ cat /etc/vmware/config | wc -l57> Host-02:$ cat /etc/vmware/config | wc -l53

Hence, when VMs start on the affected hosts, they have extra CPU requirement that wont be met when migrating to other hosts.

In order to remove these CPU requirements, you will need to refresh the EVC baseline by disabling EVC and re-enable it again. This will update the /etc/vmware/config on all hosts in the cluster.

Related: