behm015 Tracker

Re: Workstation 17.5.0: (enhanced?) keyboard driver problem

behm015 — Mon, 30 Oct 2023 09:20:28 GMT

UPDATE:

I downgraded from 17.5.0 back to 17.0.2 (old installers can be found under %APPDATA%/../Local/VMware/)

Even if you have upgraded your VM with the migration tool to have hardware compatibility with 17.5.x, you can use that exact same tool for downgrading to 17.0.x again.

If you have a host shared folder(s) mounted, those will be disabled upon upgrading or downgrading, making your VM fail to boot up.

You can enable your shared folder again in your VM settings in order to fix the bootup.

Alternatively you can edit /etc/fstab in rescue mode (the line pointing to your shared folder mount point).

Re: Workstation 17.5.0: (enhanced?) keyboard driver problem

behm015 — Wed, 25 Oct 2023 11:49:23 GMT

UPDATE:

Even with 1 cpu and 1 cpu/core I am still experiencing the issue that the keyboard and mouse input do not work after a random period of time.... it seemingly just takes longer.

Re: Workstation 17.5.0: (enhanced?) keyboard driver problem

behm015 — Tue, 24 Oct 2023 10:55:53 GMT

My specs:

Host System: Windows 11 Enterprise

Build: 22621.2428

CPU: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz 2.59 GHz

RAM: 32,0 GB (31.8 GB usable)

Graphics: NVIDIA Quadro T1000 (4GB)

Hyper-V is enforced (cannot turn it off)

I do NOT have the Enhanced Keyboard Drivers installed.

VM:

Kubuntu 22.04 (tried with Ubuntu 22.04, same problems)

RAM: 16 GB

Processors (1 CPU, 6 cores /cpu)

Two SATA Disks

USB 3.1

3D Graphics acceleration is disabled. (Display)

One shared folder which is always enabled

Copy & Paste and Drag & Drop is enabled

Time Sync is enabled

No auto login

firmware type is bios

(memory page trimming is disabled)

Side channel mitigations are disabled

I have the exact same symptoms where I open Google Chrome (google.com) and then trigger a complete input "freeze" by pressing ctrl + mouse scroll (up/down) which then prevents any further input and only leaves me with a complete restart of the VM preventing me from working....

The VM is not frozen, as I am able to SSH into is using Putty and it is responsive.

A hotfix (which is not a long term solution, as the vm becomes unusable for development) that I found is that you can reduce the number of CPUs and cores/CPU to 1 for each.

With 1 cpu and 1 core/cpu I was not able to respoduce the input freeze using Google Chrome (ctrl + scroll).

Fun fact:

While my VM is running, I am able to increase the number of CPUs to 4 (or even more) and Google Chrome still does not freeze.

If I reboot my VM, then it starts to freeze again when trying to zoom in and out using ctrl + scroll up/down