VMware Communities
sIsTema_IT
Contributor
Contributor
‎08-22-2022 11:17 PM

Unable to start any VM as long as they are using more than 1 CPU Core. VM with 1 Core still crashing

My Linux VM can´t start whenever i set it to use more than 1 CPU core. When I set it to 1 CPU core it boots and runs a bit until it crashes again. My Windows VM doesn´t even boot when I set it to 1 CPU core.

The file attached is the support file for my Linux VM.

vmsupport-2022-08-23-08-14.zip
0 Kudos
3 Replies
bluefirestorm
Champion
Champion
‎08-23-2022 12:19 AM

2022-08-23T08:14:02.546+02:00| vmx| I005: Log for VMware Workstation pid=9912 version=15.5.7 build=build-17171714 option=Release
2022-08-23T08:14:02.546+02:00| vmx| I005: Host is Windows 10, 64-bit (Build 22000.856)
2022-08-23T08:14:02.622+02:00| vmx| I005: IOPL_Init: Hyper-V detected by CPUID
2022-08-23T08:14:02.654+02:00| vmx| I005: hostCPUID family: 0x6 model: 0x8d stepping: 0x1
2022-08-23T08:14:02.654+02:00| vmx| I005: hostCPUID codename: Unknown
2022-08-23T08:14:02.654+02:00| vmx| I005: hostCPUID name: 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
2022-08-23T08:14:02.716+02:00| vmx| I005: Monitor Mode: ULM

You are running version 15.5.7 on a Windows 11 host with Hyper-V enabled and on an 11th gen Intel CPU laptop.

There is a problem with versions earlier than 16.2.x with 11th Gen CPU with Hyper-V enabled; it has something to do with a CPU feature assumed to be available but is not.

Disable Hyper-V from the host. There are numerous threads/posts on how to remove this. Once Hyper-V is disabled the Monitor Mode should show CPL0 instead ULM.

0 Kudos
sIsTema_IT
Contributor
Contributor
‎08-23-2022 12:53 AM

Thank you. This seems to have resolved the issue.

0 Kudos
axs-priv-dev
Contributor
Contributor
‎11-30-2022 12:31 AM

The problem is still present in VMWare Workstation Pro 16.2.4 (the latest 16.x version). Some, so as I, had upgraded to version 16 because of the promise to be compatible with Hyper-V. Neither switching off Hyper-V (sometimes I have to use both kinds of VM and switching Hyper-V on/off requires a reboot and thus repeated workload preparation, which is impractical) nor reducing CPU and core count to 1 (performance = 0) is a real solution. In my opinion, this has to be fixed as a bug-fix in VMWare Workstation Pro version 16. Paying for a fix by upgrading a new version (17.x), which even might not work any better, is a no go.

0 Kudos