Hi,
Looks like Hyper-V is still running (even while it might be disabled in the UI), have a look at:
where @bluefirestorm gives all the details you need to know for addressing this.
--
Wil
Hi,
@erleed wrote:
Thank you for the tip wila. Unfortunately, my computer doesn't have the hypervisorlaunchtype entry in bcdedit.
There's quite a few more steps than that....
To quote:
Follow the steps in this KB
https://kb.vmware.com/s/article/2146361
Also make sure that Memory Integrity is OFF
Windows Security -> Device Security -> Core Isolation details
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).
If it still doesn't work, then please attach a recent vmware.log file to your reply here.
--
Wil
We're not talking about ESXi and you didn't attach your vmware.log file ... so can't answer your question.
--
Wil
@bluefirestorm wrote:
It is documented as per the KB in the error dialog.
https://kb.vmware.com/s/article/81623
Which can be confirmed by looking at the vmware.log file to see if Hyper-V is turned off or not.
My guess is that it isn't, which is the main reason why I asked for the log.
--
Wil
Hi bluefirestorm,
Yes I understood your reply was to the topic starter.
Agreed on all points.
I just wish that Microsoft didn't make it so difficult to disable Hyper-V.
It really makes no sense that it keeps running when you uncheck the Hyper-V option, that's not transparent at all.
All other options that depends on Hyper-V shouldn't be enabled anymore once you uncheck it, but sadly that's not how it works.
--
Wil
@erleed wrote:
My thoughts exactly @wila.
Regarding the vmware.log. I cannot find this, I found an article showing how to get logs for different products and vmware log did not come up in the methods I tried.
I even ran the vbs file manually and there was no vmware.log file generated. Can you point me to where it is located?
My apologies, sometimes I forget not everyone knows where to find these log files.
The vmware.log file(s) are generated in the same folder as where all the files of your virtual machine are. They are kept along with your VM.
--
Wil
Hi,
FWIW, are you even using performance counters in your VM?
Because if you're not then you can simply uncheck the checkbox in the VM's configuration.
Btw, if you are unsure if you need them... then you don't need them as it is a very specific use case.
To sum it up from the picture above.
- Don't check Intel VT-x/EPT ... unless you are actually trying to run a VM in a VM...
- Don't check CPU performance counters ... unless you are in need to profile your VM for performance bottlenecks in specific software
- Don't check virtualize IOMMU .. unless you need VBS to be enabled.
More details here:
https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3140DF1F-A105-4E...
Lots of people seem to think that having the above checked helps to speed things up (hint: it doesn't)
--
Wil
