In the hands of someone who hasn’t perhaps Hackintoshed a laptop before, these might have been famous last words. Now, Monterey was a little buggy for me in aspects that I considered important-namely webcam quality and audio recording quality-so I thought, hey, let’s downgrade. So I tried it, and it worked, even if I uncovered some limitations with Parallels in the process. I get that Apple is building a new architecture, but it feels like Apple may not fully get the convenience factor of running a virtual machine if this was what I had to go through to run Monterey even for testing. It was basically a black box of sorts, and nothing like the VMs you can usually use on Parallels. You couldn’t throw more RAM at the VM, or increase the size of the virtual disk. And there were some limitations in the format-for one thing, it did not support any changes in settings.

Because Apple is still trying to work out the kinks of its virtualization approach on the M1, apparently, it requires you to run the Monterey virtual machine on Monterey. Now, a clear use case for running a virtual machine using a tool like Parallels is to virtualize an operating system newer than the one you’re running for testing purposes, so you could get a feel for the interface and understand where bugs might be in the process.īut no, that was not what the virtualized Mac-in-a-Mac setup offered.

This was a marquee feature of Parallels Desktop 17, which was just released a little over a week ago.

So the reason I wanted to install Monterey is rooted in the fact that I wanted to test out Monterey-but, additionally, I wanted to see what it was like to virtualize MacOS in Parallels on the M1 processor. (Apple) What led me to install the Monterey beta It looks so clean and simple in press image form.

Qustodio mac big sur