Somehow Microsoft have made a change to Windows/HyperV that breaks the resource sharing between Windows and the VMWare Workstation running in user mode (because Hyper-V is also present). The problem has already been thoroughly debugged and debated in the VMWare community as indicated in the main question and it was brought here for further insight. With all respect, this is a bug/change introduced by Windows Update and first included in the cumulative update for Windows 10 in September. Is there any solution or explanation of the cause of the problem? I did install KB5017308 and have recently installed the October KB5018410 update, but the problem still exists VMWare Workstation 16 Pro + Ubuntu 22.04.1 - VM unresponsive with high CPUĪccording to the discussion in the VMWare community, some users believe that the problem is caused by the installation of KB5017308
"Soft lockup, CPU stuck" on Red Hat guests after upgrade to Fusion 12.2.0 There are also several posts in the VMWare Workstation community reporting the same problem: In some cases, the tasks running in the virtual machine also print "Soft lockup, CPU#~ stuck for ~ s ” More specifically, the startup of VM is normal, but if we switch back to the host and left the VM background for a while (like 5~30 min), then turn back, the VM will sometimes become unresponsive.Īt this moment, through the task manager you can find that the allocated CPU occupation is very high. Since September, when I try to run Ubuntu22.04 and Kali VMs in VMWare Workstation, the VMs often turn out unresponsive on a random basis.
Since I need to use WSL2, I turned on Hyper-V related features on the host
0 kommentar(er)
