06-28-2025 03:34 PM
I'm currently trying to get CML personal (v2.7.2) working on VMware Workstation 17 Pro (v17.6.3 build-24583834), and I keep getting an error message that says, "VMware Workstation does not support nested virtualization on this host. Module 'HV' power on failed. Failed to start the virtual machine." I have a Windows 10 x64-based Lenovo laptop with an Intel Core i7-11850H Processor. I've tried.
bcdedit /set hypervisorlaunchtype off
Ensured that my CPU supports virtualization extensions
Disabled Virtualization-based Security (VBS)
Nothing seems to work. Does anyone have a clue what I can do to get CML working
Solved! Go to Solution.
06-29-2025 01:10 PM
This message from VMware Workstation, and its companion message from the CML installer "Virtualized Intel VTx/EPT is not supported on this platform", comes up frequently on the CML-Personal community support site. The root cause is that the VTx extensions enabled in BIOS are not being propagated up from the physical CPU, through Windows, and into WMware so that Workstation's virtual CPUs for the CML VM have VTx support that can be exposed to CML's KVM. Cisco's CML team has has put together a procedure that is a superset of the steps you have taken to expose the VTx extensions to VMware from Windows. If those steps do not work for you and you have Windows 11 Pro, you might also try running CML on Hyper-V using the steps on the CML github site.
FWIW, you might run with CML 2.8.1 instead of 2.7.2, as it has been out for some time, though it does not address this nested virtualization issue (this is a Microsoft security "feature").
06-28-2025 10:32 PM
= @jollysonan FYI : https://community.broadcom.com/vmware-cloud-foundation/discussion/vmware-workstation-does-not-support-nested-virtualization-on-this-host-module-hv-power-on-failed
M.
06-29-2025 01:10 PM
This message from VMware Workstation, and its companion message from the CML installer "Virtualized Intel VTx/EPT is not supported on this platform", comes up frequently on the CML-Personal community support site. The root cause is that the VTx extensions enabled in BIOS are not being propagated up from the physical CPU, through Windows, and into WMware so that Workstation's virtual CPUs for the CML VM have VTx support that can be exposed to CML's KVM. Cisco's CML team has has put together a procedure that is a superset of the steps you have taken to expose the VTx extensions to VMware from Windows. If those steps do not work for you and you have Windows 11 Pro, you might also try running CML on Hyper-V using the steps on the CML github site.
FWIW, you might run with CML 2.8.1 instead of 2.7.2, as it has been out for some time, though it does not address this nested virtualization issue (this is a Microsoft security "feature").
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide