Hdiutil attach /tmp/BigSur.dmg -noverify -mountpoint /Volumes/BigSur
VMWARE FUSION OS X ISO
To work around this I had to create an ISO file from the installer and use that to create the VM in Fusion 12: hdiutil create -o /tmp/BigSur -size 17000m -volname BigSur -layout SPUD -fs HFS+J I’ve ran into this issue in the past, where are reboot of the host Mac fixed it, but not this time. Except one glitch which I think VMWare is aware of: Fusion 12 fails to create the installation medium when you select the macOS Big Sur Installer: I basically followed the exact same workflow as my earlier post on VM’s and Automated Enrolment, which all seems to work fine. That said, I still wanted to test the creation of a Big Sur VM, and to do so I started with VMWare Fusion 12. As general advise I’d always crosscheck your testing on a physical machine before putting anything into production, especially when you see some weird behaviour.
VMWARE FUSION OS X PRO
Inconsistent behaviour with Setup Assistant showing or hiding screens you select in the Jamf Pro pre-stage.
Even on a high end Macbook Pro it feels a bit slow, but more problematic is the inconsistent behaviour I see from time to time. Since the release of macOS Catalina I have mixed feelings about using a VM to test macOS deployments.
0 kommentar(er)
