WilliamLam.com

Unable to power on vSphere Cluster Services (vCLS) VM in Nested ESXi with no host is compatible with the virtual machine

by // 9 Comments

After deploying a new VMware Cloud Foundation (VCF) Workload Domain using the VCF Holodeck Toolkit, which leverages Nested ESXi, I noticed the vSphere Cluster Services (vCLS) VMs kept failing to power on and threw the following error message:

No host is compatible with the virtual machine


I thought this was quite strange, especially since the vCLS VMs ran fine when the VCF Management Domain was setup.

UPDATE (07/03/2024) - The reason for the vCLS error is actually due to the miss-configuration of the Nested ESXi VM created by VCF Holodeck Toolkit, please see this blog post for an easier fix.

Looking at the vmware.log for the vCLS VM, I quickly found the issue where the VM expects to have the MWAIT CPU instruction exposed:

2024-03-19T16:35:35.736Z In(05)+ vmx - Power on failure messages: Feature 'cpuid.mwait' was 0, but must be 0x1.
2024-03-19T16:35:35.736Z In(05)+ vmx - Module 'FeatureCompatLate' power on failed.
2024-03-19T16:35:35.736Z In(05)+ vmx - Failed to start the virtual machine.

I figure I was probably not the first person to run into this and asked Ben Sier, who works on Holodeck and indeed he ran into this before. It looks like with newer vSphere releases, it expects to configure Per-VM EVC but the vCLS VM may not function properly within a Nested ESXI environment. Luckily, Ben has a workaround that we can quickly use.

[Read more...]

Retrieving detailed vSphere Lifecycle Manager (vLCM) Image information from vSphere Cluster using PowerCLI

by // Leave a Comment

As more and more users are adopting vSphere Lifecycle Manager (vLCM) to simplify the lifecycle and configuration management of their ESXi hosts, you may want to get more information about a given vLCM image that has been associated with a specific vSphere Cluster.

While you can certainly get this information using the vSphere UI, you can also get this detailed information by using the vLCM REST API, which can easily be consumed using variety of vSphere SDK Clients including PowerCLI.

For inventory and/or auditing purposes, automation is typically the answer, especially at scale. I will not bore you with the details, but I recently created the following PowerCLI function called Get-vLCMClusterImageInformation and given the name of a vLCM-enabled vSphere Cluster, it will provide you with the associated ESXi base image and all Solutions and Components that is associated with a given image.

UPDATE (02/06/25) - The script has also been updated to also include information for a vLCM image that has integrated with an Hardware Support Manager (HSM) to provide firmware information.

[Read more...]

Quick Tip - New method to mark HDD to SSD in ESXi 7.x and 8.x using ESXCLI

by // 3 Comments

I recently helped a colleague who wanted to mark an HDD device in ESXi to show up as an SSD, which may be needed if the storage device was not correctly detected or if you are using Nested ESXi and the underlying storage is not an SSD and you need to mark it as an SSD for use with vSAN OSA or ESA.

The easiest way to accomplish this operation is by using the vSphere UI, but that does require vCenter Server to be up and running, which it was not. Alternatively, you can also perform this operation using ESXCLI and configure an Storage Array-Type Plugin (SATP) claim rules, which had been possible since 2013 but it looks like the old method no longer works in the latest ESXi 7.x and 8.x releases.

Note: If you are configuring this for a Nested ESXi VM, another method is to emulate a virtual SSD as shown in this blog post.

[Read more...]