Upgraded my EndeavourOS host to version 16.2 yesterday. Now I'm noticing a lag when typing in any VM terminal window - Arch, Ubuntu, openSUSE are experiencing the same thing. I'm using open-vm-tools, which has never been a problem before. I have not changed any settings on the VMs since their creations: 8GB RAM, 4GB vGPU, 8 vCPUs.
Anyone else seeing this? I haven't tried with my Windows 10 host yet (also on v16.2).
UPDATE: working great with Windows 10 (Home) host.
I just updated all of my VMs and verified that the issue still exists. However, it seems much worse on Debian/Fedora-based VMs; my Arch and openSUSE VMs don't seem to be affected. After trying both of them this morning, I found that these (2) releases - both rolling - are using the latest open-vm-tools client, version 11.3.5. While I did not see any related issues posted on the GitHub site, I'd be willing to bet that the v11.3.5 version fixes this issue.
Have you tried turning 3D acceleration off?
Does that help?
Now the following might sound strange.. but I once had this issue a few years ago and it was ....
Typing anything in a terminal was pretty frustrating.
After setting the DNS server to 126.96.36.199 everything worked as it did before.
Yes, disabling 3D acceleration fixes the lag. But I don't think that should be the solution, I want to be able to use 3D acceleration. The issue seems to be with Debian based distros.
Also, this still doesn't explain why my Arch/openSUSE VMs are working as expected.
Not sure, but I would guess that there's a different vmwgfx driver?
I just looked over at https://github.com/vmware/open-vm-tools/issues and I'm not seeing this issue mentioned.
Perhaps a good idea to log it there.
Sorry, my bad, not had enough coffee yet, vmwgfx is a kernel module and thus it is part of the kernel.
Just did a few searches on it and the results of that are here: https://wiki.vi-toolkit.com/index.php?title=Vmwgfx
While this may be related to kernel modules, (3) things still don't make any sense to me:
Have the same lag, and when searching around i found this :
In my case it might be Nvidia Driver related.
I am having the same issue, in a really extreme form on Fedora 34, Host is Windows 10 Professional though.
I did not find any solution for it and it is so bad that simply working quick is not possible at all. I am a very quick writer but even upper and lowercase get completely mixed up as the shift key is registered way too late for. Never had these issues before Workstation 16.
Upgraded all the VMs to 16, installed latest open-vm-tools in Fedora. Nothing works. Aside from that the integration of copy/paste in login screen of Fedora seems completely broken, it simply does not work. It did with 15 without issues. Once I am logged in copy/paste works as it should. This is a massive disappointment, too, as I have to type 30 cryptic chars every time I reboot the VM
For me I also found out what it was in my case. And that is totally weird. If I switch the host (Windows 10) sound output to speakers while the VM is running, the GNOME terminal shell is not able to play the sound of the terminal bell correctly because it seems the sound output of the VM is messed up. This means that with every keystroke that would play the terminal bell the VM hiccups so bad that typing on the keyboard gets unusable. If I disable the terminal bell then in the GNOME terminal application typing and also autocomplete gets as fast as it can get.
So there is definitely an issue with that on a Windows 10 host to at least a Fedora VM, did not test other VMs until now with that.