VMware Fusion 10 was released in August 2017. One interesting change is that its minimum system hardware requirements are more discerning in terms of the Intel CPU families supported. Notably, Mac Pro models from earlier than 2010 (i.e. earlier than
MacPro5,1) are not supported. Attempting to start a VM on such Mac hardware results in the following dialog (screenshot is of version 10.1.2):
Earlier versions had a more ambiguous dialog wording which didn’t explain the incompatible features, however it seems as though currently they seem to be providing more detailed info, mentioning the “unrestricted guest” capability.
Originally I discovered this issue the hard way when VMware Fusion 8.5 on my MacPro4,1 system (dual 6-core X5550 CPUs) advertised the 10.0 upgrade, and happily let me run the upgrade on this system without any mention of this CPU feature requirement. I learned only of the system’s incompatibility to show me the above notification after I was attempted to start an existing macOS VM from my VM library.
Luckily, this has been discussed already on VMware Fusion forums and the solution was quick at hand. There is a VMX config parameter,
monitor.allowLegacyCPU, which can be set either directly within the VM’s VMX file, or as a system-wide default in VMware’s config file at
/Library/Preferences/VMware Fusion/config. This file can simply be edited to set this value to
true. For example:
$ cat '/Library/Preferences/VMware Fusion/config'
monitor.allowLegacyCPU = "true"
Once this is set, VMs seem to happily run on these older generations of CPUs. Today, this MacPro4,1 machine is worth a tiny fraction of my 2017 MacBook Pro 13" with Touch Bar, but it handles the workloads of VMs not only much better than the MacBook Pro, but it also boasts many more cores, ideal for running more in parallel.
This unrestricted guest feature happens is also required for the use of applications leveraging Apple’s Hypervisor framework which was added in OS X 10.10. A few notable such applications:
As Apple documents, one way to check if your hardware supports Apple’s Hypervisor is to use
sysctl and check for the value of
kern.hv_support - if it is
1, your machine should support using the Hypervisor framework. Here’s the output from my MacPro4,1 to confirm that this framework is not supported:
$ sysctl kern.hv_support
Of course, as enabling this
monitor.allowLegacyCPU VMX option on Fusion 10 simply restores functionality on hardware that no longer meets the minimum system requirements, the usual caveats about unsupported software configurations apply. I also haven’t yet noticed any instability or performance regressions in running macOS VMs on this hardware using this VMX option.