Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 198737

Re: VMs run a higher CPU load on Catalina

$
0
0

Dear Will:

 

I really appreciate and thanks your promptly answer  but I do not know How to do that?

 

 

You tell me to do the following:

 

You can try adding the following to your VMs vmx file:

mks.enableMTLRenderer = "FALSE" 
mks.enableGLRenderer = "TRUE"

This will enable the openGL renderer instead.

 

Is there any chance to have a "Step by Step" description of How to do it?

 

I am a simple user I am not in anyway an expert as you are.

 

Respectfully Yours

 

Carlos

 

PD: Just in case that you don't have information of my Mac. Please see below:

macOS Catalina. Version 10.15.1

MacBook Air (Retina, 13-inch, 2018)

1.6 GHz Dual-Core Intel Core i5

16 GB 2133 MHz LPDDR3

Intel UHD Graphics 617 1536 MB

Hardware Overview:

Hardware Overview:

 

  Model Name:                                 MacBook Air

  Model Identifier:                            MacBookAir8,1

  Processor Name:                          Dual-Core Intel Core i5

  Processor Speed:                         1.6 GHz

  Number of Processors:                 1

  Total Number of Cores:                2

  L2 Cache (per Core):                     256 KB

  L3 Cache:                                      4 MB

  Hyper-Threading Technology:      Enabled

  Memory:                                        16 GB

  Boot ROM Version:                       1037.40.124.0.0 (iBridge: 17.16.11081.0.0,0)

  Serial Number (system):                [removed]

  Hardware UUID:                            BE9AACD3-7E10-5DC5-B0A6-804447DBE199

  Activation Lock Status:                 Disabled

  Model Name: MacBook Air

  Model Identifier: MacBookAir8,

 

moderator edit by wila: Removed the serial number, it is not required info and can cause you trouble if somebody else starts using it.


Viewing all articles
Browse latest Browse all 198737


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>