Update 2023/03/20
The latest revision of VMWare has not solve the issue: 17.0.1 build-21139696
Environment:
OS: Windows 11 with Virtual Machine Platform installed. All patches installed.
Software: VMWare Professional 17
VM: Ubuntu 22.04 with all patches.
Windows Host Power savings config: Never put computer to sleep.
Symptoms:
No TTY response. No response to CTRL-ALT-DELETE
Have to hard reboot the VM to get things working again.
Window does not resize and no interaction keyboard or otherwise works.
I have to hard boot the VM to restore functionality.
Frequency of problem:
When I have logged out for a long period of time, when I return to the VM again it is dead.
Hardware:
Intel i9 10900K
Graphics: Nvidia 3060
64 Gig of RAM
I run a VPN on the host Windows 10 PC.
I don't run a VPN within Ubuntu.
I found a workaround.
Context:
(I also have this problem, running Worstation 17 Pro on ArchLinux, so this is not happening only when host is Windows)
When installing an Ubuntu system from creating a VM (not duplicating one), Workstation auto-detects it and automatically sets up the Guest OS to "Linux" and Version to "Ubuntu 64-bits".
Action:
I changed that detected Version, and manually set it "Other Linux 6.x kernel 64-bit", then continue the installation.
Result:
Nothing no longer freeze.
PS: how to send that information to VMWare devs?
@toukay Ticket has been raised internally. Relevant team will look into the same.
There are unfortunately a number of separate issues being reported here I think.
Some of these things have already been noted here, but he's my recommendations for things people should try:
(1) Disable Hyper-V on the Host
(2) Disable the E cores on your system
I'm not an expert on the CPU side of this, but my understanding is that both of those things will put you on some different code paths that are triggering performance issues or intermittent stalls for some users.
(3) Disable Guest Sleep/Hibernate/PowerSave
Recent versions of Ubuntu are being more aggressive at putting the Guest into Power Save modes and engage Sleep or Hibernate when the screensaver engages. This is sometimes provoking keyboard hangs that then don't restore when the Guest wakes up again, or fails to trigger a wake-up via the keyboard.
(4) Power off the VM, and add the config option: keyboard.allowBothIRQs = FALSE
This might make the Sleep/Hibernate hangs worse, but seems to avoid a different keyboard hang that people are hitting during normal keyboard usage.
(5) Make sure the VM has a USB controller.
This gives us an alternate mouse path which is generally better behaved, and helps reduce the traffic on the PS/2 port decreasing the chances of hitting keyboard hangs there.
(6) As a last resort, you can try switching to the virtual USB keyboard for the VM.
After making sure the VM has a USB controller, power off the VM and add this config option: keyboard.vusb.enable = TRUE
That will switch us from sending keyboard events using the PS/2 keyboard to the USB keyboard. On some Linux distros this may make your key-repeat get stuck more often, but again avoids any PS/2 keyboard hangs you might be hitting. This is however unlikely to fix any general host performance issues (if the host is stalling or generally slow on it's own), and is a less common configuration.
Ah sorry, or also:
(7) Toggle 3D graphics in the VM.
That changes portions of our console path, and might make this better/worse depending on the system and graphics card.
I found a solution but might apply for a just a few.
First, some context:
This hang during IPv6 mode DNS resolution was responsible of the freezes. Again, it was my case, I am not saying it is general.
I disabled IPv6 on the host system, and also on the guests, then eveything is OK now
Found a tip, but forgot where (kudos for the one that wrote it).
Just add these two lines to the bottom of the VM's vmx file:
keyboard.allowBothIRQs = "FALSE"
keyboard.vusb.enable = "TRUE"
this fixed all freezing problems for me.