Impossible to diagnose with the current information.
Please attach a vmware.log file from a VM that displays the problem.
--
Wil
Hi,
OK.. the first thing, the log has this line.
2022-09-30T10:34:53.930Z In(05) vmx Monitor Mode: ULM
Which means that you are running in User Level Mode and thus Workstation cannot use VMware's hypervisor, but instead it has to go through the Hypervisor API that Microsoft provides.
Only when Monitor mode returns CPL0 it is running in ring 0, a.k.a. no hypervisor.
Monitor mode CPL0 (Current Privilege Level 0) is required for VMware Workstation to be able to use their own hypervisor.
See also:
In order to turn off ULM/Hyper-V mode, run the following command at the host in windows command-line with Administrator privileges:
bcdedit /set hypervisorlaunchtype off
Reboot the system to activate your changes.
If you want to go back to Hyper-V mode again, then you can enable it like this:
bcdedit /set hypervisorlaunchtype auto
See also:
- Workstation 16 Pro Error "Virtualized Intel VT-x/EPT is not supported on this platform
- https://kb.vmware.com/s/article/2146361
Note that you also might have to disable Memory Integrity.
Windows Security -> Device Security -> Core Isolation details
Don't forget to reboot the host after making any of these changes.
--
Wil
Hi again,
Next issue.
vmx E1000: E1000 rx ring full, drain packets.
You're using E1000. Back in time that would be a good network adapter to use.
Nowadays one should use a better one, try using either e1000e or vmxnet3
--
Wil
@cb831 wrote:Thanks for the analysis !
I have been running like this for almost two years without issues.
It only started 2 weeks ago.
There's a variety of reasons why the hypervisor might have been switched to ULM.
Either changes in settings in Windows or some updates.
Without your logs from BEFORE the problems there's not much else I can suggest atm.
For now, it is the most likely candidate for the reason of your problems.
--
Wil
