My hope was that this was a fluke, and problem solved yesterday. So thinking this may be an update issue, I updated everything to the latest on the VMWare Fusion side, and after the update re-installed the VMWare tools into the VM (Ubuntu 19.04). Both systems after that were totally responsive and happy.
On the "top" active terminal I immediately saw the hgfs process disappear, and CPU spike / root cause was truly terminated - the CPU spike nose dived back to normal "cool" levels - around 3% to 5% on the VM, and OS X host too in turn CPU nose dived back to normal levels. (Identify the top process monopolizing the CPU - it should be obvious 100%++ CPU utilization and note the PID) On the far left column of top is the PID (Process ID) which I noted, opened another terminal trying to complete before the system froze, and was able to type the command:
Just before I upgraded, I was able to open a terminal on the VM (Ubuntu) and ran "top" to see if I could identify the process spike - and thankfully the offending process was clearly visible as an "hgfs" process. So I updated, and then re-installed VMWare tools on the VM (Ubuntu 19.04 Disco Dingo). I upgraded to this latest version of VMWare after running into the CPU spike of the vmware-vmx process (running well beyond 100% resulting in both vm and native OS freezing, unfreezing, system panic across the board, and all fans turning on on the MacBook Pro). I had the same issue - running OS X Mojave Version 10.14.5, and VMWare Fusion Version 11.1.1 (14328561). Save the changes and power up the virtual machine.These changes will enable the graphics rendering using OpenGL. vmx file with a Textedit, then from the top Apple menu bar go to Edit > Substitutions and make sure that Smart quotes are not enabled.Īdd these lines at the end of the vmx file. Then go the concerned virtual machine and click on show package contents (by doing a right click or using a single tap with two fingers).ģ. First, the virtual machine should be shut down (not suspended or in sleep mode).Ģ. vmx file (configuration file) for the virtual machine. There are two entries that have to be added in the. Solution is to use OpenGL, since Metal API uses both OpenGL and OpenCL.
Incase someone finds this useful, it's possible that the Metal (hardware-accelerated 3D graphic and compute shader application programming interface in MacOS) is causing the performance issues.
Finally got it resolved with help of Support. I lived with this problem for a long time and I just shied away from using Fusion.
0 kommentar(er)
