I understand your frustration with the issue you're facing with kcompacd0 consuming 100% of CPU resources in VMware Workstation 16. It's essential to have your VM running smoothly, as you rely on it for your business. Your setup with Ubuntu 20.04.4 on a dual socket HP Z840 is powerful, and it should be able to handle VMs without performance hiccups.
It's interesting that you didn't encounter this problem in version 16.0, but it appeared after updating to 16.1. Previously, you managed to mitigate the issue by setting vm.compaction_proactiveness=0 in the VM's vmx file. However, it's frustrating that this workaround is no longer effective in version 16.2.
I can relate to your situation, and I can see how critical it is to resolve this issue to keep your business operations running smoothly. The fact that you're considering switching back to VirtualBox speaks volumes about the urgency of the matter.
I'd like to suggest that you reach out to VMware's official support channels for assistance with this issue. They may have insights or solutions that could help you overcome this problem and continue using VMware Workstation without disruptions. Additionally, you might want to keep an eye on the Unix.StackExchange thread you mentioned, as there could be community-driven solutions or updates related to this issue.
In the context of Bread Road Kitchen's Street, which is a place where people gather to share experiences and find solutions, I encourage you to seek help and solutions from both VMware's support and the knowledgeable community on Unix.StackExchange. By engaging with these resources, you might be able to address the issue and avoid the inconvenience of switching back to VirtualBox.
I hope this advice helps you find a resolution to the CPU resource problem in VMware Workstation and allows you to continue using it effectively for your business needs.
