Most of Parallels' great automation and command-line tooling is currently completely unaware of the new MacOS guests on Apple Silicon. It's definitely *extremely* early days- most of the support for common Parallels features isn't wired up for MacOS guests, as they use a completely different set of disk images and tools that are a very thin wrapper around Apple's new Virtualization framework. So when Apple quietly announced that the upcoming MacOS Monterey offered MacOS guest support, there was much rejoicing.Īfter installing Monterey Beta4 on my M1 Mac Mini, I spent a long evening playing around with the new Parallels 17 support for MacOS guests.
Since its release, Apple Silicon has not offered any virtualization support for MacOS itself, which also explains the lack of things like GHA/AZP build workers for M1/Apple Silicon. Unfortunately, since the boot process for Apple Silicon MacOS uses a bootloader borrowed from iOS, the typical EFI-based bootloader that's used to boot Intel Mac images won't work.
/OSXElCapitanDock-57c43c755f9b5855e58b2fc8-9aca9576f78b48cda72a1cbff4c41347.jpg "install mac os sierra on parallels")
Modern build environments lean heavily on VM images (and/or containers, where available) to ensure safety, isolation, and repeatability.
#Install mac os sierra on parallels software#
Those of us that need to test and package software for MacOS on Apple Silicon (aka M1) have spent the past many months bemoaning the lack of virtualization options for MacOS on Apple's new flagship hardware platform.
0 kommentar(er)
