WilliamLam.com

Nested ESXi Virtual Appliances are now back under VMware Flings Community!

by // 25 Comments

I know many of our internal teams (field, engineering, support, etc.), customers and partners have heavily relied on my Nested ESXi Virtual Appliances (VA) over the years which makes it seamless to deploy both VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF) lab environments for learning, testing, troubleshooting, automation and development purposes. To support our customers in troubleshooting and prototyping purposes, I also make use of my Nested ESXi VAs on a regular basis and have found this to be invaluable in aiding my day to day work.

As part of the VMware by Broadcom "Day 2" transition, the hosting platform that housed my Nested ESXi downloads was no longer available and that impacted both the standalone Nested ESXi downloads but also the Nested ESXi Content Library, which provided a convenient way to subscribe to all the VAs from your vCenter Server.

Today, I excited to share that my Nested ESXi Virtual Appliance downloads are back and they are now available under the VMware Flings program! ?

[Read more...]

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...]

vSphere 8.0 Update 1c resolves Windows VBS performance & Hyper-V Generation 2 Nested VM running on AMD CPU

by // 1 Comment

vSphere 8.0 Update 1c was just released and one of the resolved issues mentioned in the ESXi release notes is the following:

Nested virtual machines on AMD CPUs with operational systems such as Windows with virtualization-based security (VBS) might experience performance degradation, timeouts, or unresponsiveness due to an issue with the virtualization of AMD's Rapid Virtualization Indexing (RVI), also known as Nested Page Tables (NPT).

UPDATE (10/11/23) - This is also resolved in the ESXi 7.0 Update 3o release

There are two scenarios in which this fix resolves:

  1. Running Windows Server VM with a Hyper-V enabled Generation 2 VM (Nested Virtualization) on AMD CPU
  2. Running Windows Server VM with VBS Enabled (Non-Nested VM) on AMD CPU

[Read more...]