Hi Bluefire. sorry it took so long. Here is how i set things up according to what i saw in your suggestion. I think i missed something?? thanks for taking time to look at my screen shots as well. I...
See more...
Hi Bluefire. sorry it took so long. Here is how i set things up according to what i saw in your suggestion. I think i missed something?? thanks for taking time to look at my screen shots as well. I have my windows 10 BIOS intel virtualization technology checked (should this be enabled??) ESXi virtulization 0.png I have the "Virtualize Intel VT-x/EPT or AMD-V/RVI" box checked/enabled for my ESXi 7. ESXi virtulization 1.png I have Hyper-v for windows 10 unchecked. ESXi virtulization 2.png If the Windows 10/11 host has Hyper-V enabled, nested virtualisation will not work with Workstation Pro. That is the meaning of the "Virtualized Intel VT-x/EPT is not supported on this platform". Make sure you have Hyper-V removed from the host so that nested virtualisation will work ???. https://kb.vmware.com/s/article/2146361 Is this what you are reffering to? Process to turn off virtualization-based Security: Below steps can be followed to turn off virtualization-based Security for Windows 10 Home & Pro: For Microsoft Windows 10 Pro & above: Edit group policy (gpedit) Go to Local Computer Policy > Computer Configuration > Administrative Templates > System Double Click on Device Guard on the right hand side to open. Double Click on "Turn On Virtualization Security" to open a new window It would be "Not Configured", Select "Disable" and click "Ok" Close the Group Policy Editor. Restart the system Also make sure that Memory Integrity is OFF Windows Security -> Device Security -> Core Isolation details “Memory Integrity is a feature inside a broader set of protections called Core Isolation. It uses hardware virtualisation to protect sensitive processes from infection. These features are a subset of virtualisation-based security features that Microsoft has offered to enterprise users since Windows 10 shipped.Mar 9, 2020” https://nakedsecurity.sophos.com/2020/03/09/microsoft-turn-off-memory-integrity-if-its-causing-problems/ Also make sure that Memory Integrity is OFF Windows Security -> Device Security -> Core Isolation details This is the current state of my Memory Intefrity ESXi virtulization 3.png If your Windows host is a member of an AD domain, items such as Memory Integrity/VBS can also be enforced via domain policy. If that is the case you need to contact your domain admin. When Hyper-V is detected, you will see these lines in the vmware.log <timestamp> In(05) vmx IOPL_Init: Hyper-V detected by CPUID <timestamp> In(05) vmx Monitor Mode: ULM Once Hyper-V is no longer detected, vmware.log Monitor Mode should show as CPL0, and nested virtualisation should work (with the Virtualize Intel VT-x in the VM processor settings enabled). With the above settings, I get this when I power on my ESXi. ESXi virtulization 5.png When Hyper-V is detected, you will see these lines in the vmware.log <timestamp> In(05) vmx IOPL_Init: Hyper-V detected by CPUID <timestamp> In(05) vmx Monitor Mode: ULM In my ESXi log, I see 2022-01-18T16:34:11.659Z In(05) vmx IOPL_Init: Hyper-V detected by CPUID 2022-01-18T16:34:11.777Z In(05) vmx Monitor Mode: ULM Once Hyper-V is no longer detected, vmware.log Monitor Mode should show as CPL0, and nested virtualisation should work (with the Virtualize Intel VT-x in the VM processor settings enabled) ??? thanks for your suggestions and advice