Fusion 12 only runs over Apple Hypervisor on Big Sur. When you run with Catalina, it's the same virtualisation engine as previous versions.
Can we update to fusion 12 in Catalina then?
Fusion 12 only runs over Apple Hypervisor on Big Sur. When you run with Catalina, it's the same virtualisation engine as previous versions.
Should work, but I didn't test it since I'm not going to pay $99 for the Fusion 12 Pro upgrade to be limited to Catalina right now.Can we update to fusion 12 in Catalina then?
Should work, but I didn't test it since I'm not going to pay the Fusion 12 Pro upgrade to be limited to Catalina right now.
Take a look at the Player version or test the full one with the 30-day trial.
Fusion 12 does work in Catalina and Fusion 12 Player is free.Yeah I don't think too many of us pay for it. 😇
XSAVE
is present in 3 binaries:XSAVE
is in a larger function that checks for other important CPU features such as SSE2
, NX,XD
, TSC
, etc. The specific code block we care about is here:static const uint8_t kXsaveOriginal[] = {
0x48, 0x8B, 0x05, 0x29, 0xE7, 0xE8, 0x00, // mov rax, qword [qword_1012c1b18]
0xF6, 0x40, 0x43, 0x08, // test byte [rax+0x43], 0x8
0x75 // jne short
};
static const uint8_t kXsavePatched[] = {
0x48, 0x8B, 0x05, 0x29, 0xE7, 0xE8, 0x00, // mov rax, qword [qword_1012c1b18]
0xF6, 0x40, 0x43, 0x08, // test byte [rax+0x43], 0x8
0xEB // jmp short
};
Transport (VMDB) error -14: Pipe connection has been broken
:2021-11-15T16:19:13.472| ServiceImpl_Daemon: PID 687
2021-11-15T16:19:13.473| ServiceImplRef: Before start().
2021-11-15T16:19:17.870| ServiceImplRef: After start().
git diff
) for those wanting to play around:-allow_xsave
to boot-args to start the patcher/Application/VMware Fusion
. Adjust binary for other pathingI added your kext toIf anyone wants to try the patch set themselves, I've attached both a modded FeatureUnlock.kext as well as a .patch file (git diff
) for those wanting to play around:
I might take another crack at it to better understand why the pipe error happens, though my main goal for today's project was to bypass the XSAVE issue and I *technically* succeeded ;p
- FeatureUnlock-1.0.4-DEBUG-XSAVE.zip
- Add
-allow_xsave
to boot-args to start the patcher- Note this only supports patching
/Application/VMware Fusion
. Adjust binary for other pathing- FU-XSAVE.patch
/Volumes/EFI/EFI/OC/Kexts
and my config.plist includes the -allow_xsave
: <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string>keepsyms=1 debug=0x100 -allow_xsave -wegtree agdpmod=vit9696 -allow_assetcache</string>
<key>csr-active-config</key>
<data>
AwoAAA==
</data>
</dict>
Did you also add the FeatureUnlock in the config.plist to load?I added your kext to/Volumes/EFI/EFI/OC/Kexts
and my config.plist includes the-allow_xsave
:
I still get the XSAVE error in VMware Fusion. I'm running VMware Fusion Professional Version 12.2.1 (18811640).XML:<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>boot-args</key> <string>keepsyms=1 debug=0x100 -allow_xsave -wegtree agdpmod=vit9696 -allow_assetcache</string> <key>csr-active-config</key> <data> AwoAAA== </data> </dict>
Any hints on what I'm missing?
Yup:Did you also add the FeatureUnlock in the config.plist to load?
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>FeatureUnlock.kext</string>
<key>Comment</key>
<string>FeatureUnlock</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/FeatureUnlock</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>16.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
+1 on this. I'm using Parallels v19 on my 5,1 with some pretty hefty VMs and it works very well. The only thing I don't like is the onerous licensing model. It would be better if you could at least easily move the license from one machine to another (like Office 365 does) but no you have to call them if you want to do that. This makes it impractical to test parallels on multiple OS builds for the 5,1 to say the least.Parallels is not free, but it is much better than VMWare Fusion Pro. Even P19 runs fine under Monterey on my cMP 5,1.
You can manage the license on their dashboard. If I remember correctly, you can also enter a license already used and have the app disable the license in the other location.[...] It would be better if you could at least easily move the license from one machine to another (like Office 365 does) but no you have to call them if you want to do that. This makes it impractical to test parallels on multiple OS builds for the 5,1 to say the least.