"Error: The host cannot be admitted to the cluster's current Enhanced vMotion Compatibility mode in VCF 9.1" while vmsp VMs are powered on

Products

• VMware vCenter Server

Issue/Introduction

When attempting to enable Enhanced vMotion Compatibility (EVC) at the cluster level in VMware Cloud Foundation (VCF) 9.1, the task fails with the following error:

• Error: "The host cannot be admitted to the cluster's current Enhanced vMotion Compatibility mode. Powered-on or suspended virtual machines on the host may be using CPU features hidden by that mode."

This can happen because VCF Management Services Runtime (vmsp) VMs are powered on and either do not have an EVC mode enabled, or they are utilizing CPU features not supported by the target EVC mode.

Environment

• VMware Cloud Foundation 9.1
• VCF Management Services Runtime 9.1.0.x

Cause

The vmsp management VMs are deployed before EVC can be enabled on the cluster. If these VMs are powered on when trying to enable EVC on the owning cluster, vCenter cannot mask the CPU features required to match the cluster's EVC baseline.

Resolution

To enable EVC, you must gracefully shut down the VCF Management Services runtime VMs, enable the EVC mode, and then power the VMs back on.

1. Identify a Control Plane node:
   • In the VCF Operations UI, navigate to Build > Lifecycle > Components.
   • Select VCF Services Runtime and note the Control Plane IP address in the Nodes section.
2. Download the vcf_services_runtime_shutdown.sh script from article "How to safely shutdown all nodes within a VCF Services Runtime Cluster".
3. Upload the script to a Linux machine that has access to port 5480 on the control plane node.
4. Make the script executable: chmod +x vcf_services_runtime_shutdown.sh
5. Execute a dry run to validate the environment: ./vcf_services_runtime_shutdown.sh --node-ip <IP> --dry-run
6. Perform the automated shutdown and VM power-off (Requires govc and vCenter credentials): export [email protected] export VCENTER_PASSWORD=<password> ./vcf_services_runtime_shutdown.sh --node-ip <IP> --poweroff-vms
7. Once all vmsp VMs are powered off, enable EVC on the cluster in the vSphere Client.
8. Power the services back on following the standard VCF Startup procedure (see "Start VCF Management Services").

 

Note: Targeted to be fixed in a 9.1.x release.

Additional Information

How to safely shutdown all nodes within a VCF Services Runtime Cluster

Start VCF Management Services

Contact Broadcom Support

To receive updates on the status of this defect, please subscribe to this article. For instructions, see Subscribe to a Broadcom knowledge article.