AVX/AVX2 is a CPU feature.
It depends on your CPU, if it supports AVX/AVX2 then your guest would too.
VMware does pass-through the CPU directly to the guest OS, so it isn't emulating features.
What VMware can do for you at CPU level is masking certain features, but I would be really surprised if they masked AVX or AVX2.
FWIW, if you want to figure out the specific CPU name so you can verify the feature online then run the following command from the terminal:
sysctl -n "machdep.cpu.brand_string"
You can also directly test via sysctl if your CPU has AVX/AVX2 support.
For more details on how-to do this see:
Wil| Author of Vimalin. The virtual machine Backup app for VMware Desktop Products
| Vimalin : Automated backups for VMware Fusion and VMware Workstation Professional
| More info at https://www.vimalin.com
| Twitter @wilva
| VMware Wiki at http://www.vi-toolkit.com
1 person found this helpful
Assuming Wikipedia is right, AVX was added in Sandy Bridge processors (2nd generation Core-i3/i5/i7), and AVX2 in Haswell processors (4th generation Core-i3/i5/i7).
For the Mac Pro (Xeon processors), the Late 2013 Mac Pro (MacPro6,1) has an Ivy Bridge Xeon (E5-1620 v2 or better), so it has AVX support (but not AVX2). The 2010/2012 Mac Pro (MacPro5,1) has a Bloomfield/Westmere/Gulftown Xeon, which predates Sandy Bridge and does not support any version of AVX.
Confirmed by checking a selection of processor models at ark.intel.com.
Conclusion: your Mac Pro is too old to implement any variant of AVX.