Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Hosting a vSAN Witness Appliance on a physical host which is of a higher ESXi version than the ESXi version installed on the physical host may fail to power on with "Unsupported CPU" (74929)

Last Updated: 7/28/2023Categories: InformationalTotal Views: 6304Language:
Chinese (Simplified)JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Powering on a vSAN Witness Appliance with a higher ESXi version than the ESXi version installed on the physical host may fail with an error "Not allowed to boot" or "Unsupported CPU."

Attempting to upgrade a vSAN WitnessAppliance ESXi version running on a physical server whose CPUs is not compatible with ESXi version you're attempting to upgrade to may cause VUM to report incompliance" against the baseline.

The witness host is showing a supported CPU but showing as unsupported

Cause

With each vSphere ESXi release CPU compatibility requirements change, so it's best to check the VMware Compatibility Guide to ensure the CPU is supported between both versions.

In cases where the vSAN Witness Appliance is used for a vSAN Stretched Cluster or 2 Node configuration, the vSphere Host’s CPU must also be supported by vSphere ESXi version, regardless of the build of ESXi running on the vSphere Host

In cases where the vSAN Witness Appliance is on a supported CPU but showing the error "Unsupported CPU" this is due to cluster level EVC / VM hardware level settings not set to a supported CPU for the version of ESXi in use.

Impact / Risks

The vSAN configuration will be listed as unsupported if you run a vSAN Witness Appliance version on a physical server whose CPUs are not compatible with the ESXi version.

Resolution

Migrate the vSAN Witness appliance VM to a host which is compatible with the installed vSphere ESXi version

If on a supported CPU verify EVC is set to a generation that is supported for the installed ESXi version and that the VM hardware level is upgraded to the supported ESXi version. See the below docs for further details.

Change the EVC Mode for a Cluster
VMware EVC and CPU Compatibility FAQ
How to update the hardware compatibility for the VM.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

unsupportedCPU

Additional Resources

KB
•
[VMC on AWS] VMware HCX の導入後にパブリック IP アドレスが自動的に割り当てられる (75035)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.x

VMware vSAN 6.7.x

Take Our Survey

Support Assistant