From the vmware.log you attached

2021-12-25T06:25:23.476Z In(05) vmx IOPL_Init: Hyper-V detected by CPUID
2021-12-25T06:25:23.657Z In(05) vmx Monitor Mode: ULM

Turn off Hyper-V, follow this KB
https://kb.vmware.com/s/article/2146361

Make sure that Memory Integrity is also OFF.

Windows Security -> Device Security -> Core Isolation details

Monitor Mode in the vmware.log should show as CPL0 in the vmware.log when Hyper-V is no longer detected. CPL0 monitor mode performs much better than ULM.

One other thing, also from the vmware.log it looks like you are running your VM from a OneDrive folder. To avoid any possible corruption to the virtual disks in the future and other associated problems, it is best to avoid using OneDrive folder that synchronises with the OneDrive cloud storage. Just keep your VMs on local storage without any synchronisation to a cloud storage. The default locations of VMs when you create them is %USERPROFILE%\Documents\Virtual Machines.

They both are already off

It seems quite common for people to miss this step from the KB

“bcdedit /set hypervisorlaunchtype off” step followed by reboot

Another possibility is that if the laptop is a member of an AD domain, GPO could be enforcing things like Credential Guard/Memory Integrity. If it is, I can't help you with that and you need talk to your domain admin.

If you did do the bcedit step and it is not a member of an AD domain, you could try reinstalling the Windows 11 Professional OS on the host machine from scratch. Some weeks back, another person with a brand new Lenovo Thinkpad had to do a clean install to make it stop detecting presence of Hyper-V; as the laptop was not a domain member and he said he did all the steps in the KB and turned memory integrity off.