vinicole's Posts

Hi JavaScriptDude, Did you solve the issue? I just noticed something similar on my Debian system. It was related to the version of the xserver packages. The problem occurred right after an upgrade of these packages and I could solve it by downgrading them to the former version. Kind regards, V

Hi Jack, One more suggestion (and possible work-around): While I experience the issue with kernel version 5.10, I noticed it doesn't occur with my laptop which runs kernel version 5.15 (backport kernel version). I still have to make some tests to fully confirm this. I will keep you posted. You may try to upgrade your kernel version and see if it gives better results. Kind regards, V

Hi Jackbilmorph, I don't have a solution unfortunately but I noticed the same issue with a Linux Debian 11 host. When I try to lock my Windows 10 VM with the shortcut Windows+L, it locks my Linux host (which uses the same keyboard shortcut). I did not experience such an issue when I was running the same version of Vmware workstation (16.2) on Linux Debian 10. It seems we both use an not (yet?) supported host version. See https://kb.vmware.com/s/article/80807 Could this be the reason of this issue? Kind regards, V

Hi Bluefirestorm, Thanks for your message. Does this mean that Debian 11 is not officially supported due to this XP guest 3D graphics issue? Or is it just a matter of time for this host OS to appear on the official list of supported host OSes? Regarding the kernel modules rebuild, you are correct but in my experience, VMware workstation Pro detects when a kernel update has been applied on the system and rebuild the modules before to start. So the update process is managed automatically by VMware workstation. Kind regards, V

Hi Bert, Ubuntu 21.10 doesn't seem to be officially supported with Workstation Pro 16.2.1 as host OS. I don't know whether it can be the cause of the issue but did you experience the same behaviour with Ubuntu 20.04? Best regards, V

Hi, I found the following comment on https://forums.garmin.com/apps-software/mac-windows-software/f/basecamp-mac/45013/basecamp-cpu-usage: "The main reason BaseCamp would take up lots of CPU while idling is if your computer's graphics card ends up running our 3D view in software mode, i.e. rendering on the CPU instead of the GPU. We attempt to detect this and run the 3D view at a lower framerate to compensate for it, but it will still take up much more CPU than running 2D-only view on the same machine." Can you try to run 2D-only view and see if it improves? Regards, Vinicole