I have two new almost identical systems running i7 12700 Alder Lake systems. Host running Windows 11 22H2, mostly experimenting with Win10 guests. I'm using Workstation v17.0 but the notes above seem to suggest it happens on older systems too. So adding just these four lines worked for my i7 12700: e= "FALSE" vmx which processors to exclude (all the others get included anyway). There is a second work-around: start Workstation as administrator.Īlternatively, a slightly simpler implementation of the previous advice seems to be that you can simply tell the. So, Workstation 17.x and later needs to be fixed in terms of virtual CPU hardware, to be able to simultaneously use both P and E cores in Intel's twelvth and later generation x86 processors.įirst, thanks for this thread, it helped me work out what was going on. That necessarily gives AMD CPUs an advantage going forward, until VMware fixes the problem with Workstation. Either "workaround" results in a hobbled system, in which Workstation VMs are only able to utilize a limited number of available physical cores. Here's the problem: Workstation 16.x and earlier does NOT recognize the distinction between those two types of cores, confuses them, and FAILS TO WORK with both types simultaneously in other words, to boot a Workstation VM on a a host system with such a physical CPU, it is necessary to use ONLY ONE CORE in the VM-OR TO DISABLE ALL THE EFFICIENCY OR ALL THE PERFORMANCE CORES via the configuration file beforehand. Regarding Intel's twelfth generation (Alder Lake) and later CPUs, they have a mixture of P (Performance) and E (Efficiency) cores. I have sent this to VMware's technical support: Using harleylg's screenshot and sample 16 vCPU VM configuration, assuming the last 8 logical CPUs are the efficiency cores, adding the following means the last 8 logical CPUs (16-23) won't be used and only Processor 0 to 15 (assuming these are the performance cores with hyperthreading) will be used by the VM. But this should be treated as a workaround as it is not so efficient and not optimal to be setting CPU affinity to VMs. You could try setting processor affinity in the vmx configuration file.
0 Comments
Leave a Reply. |