How to Make a MacOS 27 Golden Gate Virtual Machine with VirtualBuddy
If you’re curious about testing out MacOS 27 Golden Gate beta but you aren’t ready for the full commitment of installing it as your primary operating system, the simplest and safest way to run MacOS 27 Golden Gate beta is within a virtual machine. While one of our authors dove right into MacOS 27 Golden Gate beta full time out of frustration with Tahoe, running a beta operating system has some risks and stability issues associated with it, so that’s not always a viable solution. In situations like this, a virtual machine is particularly helpful.
Virtual machines are great because they’re self-contained and segregated from the rest of your files and host Mac operating system, meaning there’s no chance anything in the VM, beta or not, can break anything else on the Mac. This offers a nice way to test out new beta MacOS features and functionality without any risk to your main Mac. And when you’re done, or no longer use the VM, you can just delete it.
We’re going to walk through the steps for making a MacOS 27 Golden Gate virtual machine by using the VirtualBuddy VM app. VirtualBuddy is easy to use, free, and handles the downloading of necessary MacOS 27 assets directly within the app as part of the VM setup. This makes it so you don’t have to seek out and download MacOS 27 IPSW and installer files on your own, or deal with any additional steps. The result is that setting up a new VM is super easy with VirtualBuddy. Yes there are many other virtualization apps out there, many of them are great too, but for our purposes here we are using VirtualBuddy. You will also need the host machine to be a MacOS 27 compatible Mac, which includes basically any Apple Silicon Mac (MacOS 27 does not support Intel chips).
How to Make a MacOS 27 Golden Gate Virtual Machine the Easy Way with VirtualBuddy
- Update to macOS Tahoe 26.6 (or later) before going any further
- Download from Apple the “Device Support for macOS 27.0 beta” and install that, it is necessary to be able to setup a MacOS 27 VM
- Grab VirtualBuddy from Github if you don’t have it already, and install that on your Mac too
- Open VirtualBuddy and choose to create a new MacOS virtual machine
- Select “macOS Golden Gate” from the list, and then select the latest developer beta build, and choose “Continue” *
- Go with the default settings (12GB RAM, 64GB virtual storage), or configure the VM as desired and click Continue
- VirtualBuddy will download the relevant IPSW file and begin installing MacOS 27 within the VM, this is just like any other system install so let this process complete
- When the VM is finished being created, choose to boot it by double-clicking the VM and pressing the play button
- You’ll now be walking through the standard macOS Golden Gate setup process, just like you would if this were a brand new Mac being setup
- When finished with the standard MacOS setup process (language selection, account creation, settings, etc), you’ll soon be presented with the standard MacOS Welcome screen, and using MacOS 27 Golden Gate in the virtual machine
And there you go, now you can experience MacOS 27 Golden Gate on your Mac right now, self-contained within a virtual machine, where you can launch it and quit just like any other app. Performance on Mac VMs are quite good, though it’s not quite as good as running the OS natively obviously. You can update MacOS 27 beta within the VM just like normal, it’s a fully functioning installation of Golden Gate.
If you end up enjoying the beta with the VM enough that you feel comfortable diving all the way in, be sure to backup your Mac first, and then you can install the MacOS 27 beta at any time.
* Note: If you see red text saying “Device support update required” and you can not proceed with installation, you need to go back to the second step and download “Device Support for MacOS 27 beta” from the Apple developer site, install that, then relaunch VirtualBuddy.
For the best performance with a virtual machine, you’ll want to have a good amount of RAM on your host Mac. Do not expect great performance with limited RAM. For example, my Mac has 24GB RAM and I allocate 12GB RAM to the VM, and MacOS 27 VM’s perform well.
Have you installed or run MacOS 27 Golden Gate in a virtual machine? What do you think of the experience?
I used VirtualBuddy to set up a Monterey VM. Didn’t need “Device Support for macOS 27.0 beta” (obviously). Will I need that to run27 once it is no longer Beta?
The big problem I had was that the fonts in the intro screens are way small, I’m on an M1 MacBook Air, 13″ screen. Still, the setup process was very easy. Easier than VirtualBox or UTM.
I replaced Mac Tahoe with the Golden Gate beta, it runs just as good as Tahoe in my experience. It certainly is not worse, but that’s not saying much.
I like the idea of virtual machine but they take up so much storage space that my SSD does not have a lot of room to run them.
Great, but how can you run MacOS 27 without Tahoe? Your step one is update to current TahoeOS. How about how to run MacOS 27 from MacOS 15.7.x Sequoia? Or is the only answer a separate boot drive?
Trying out macOS 27 using VirtualBuddy is really enticing and the only thing that gives me pause are the relatively recent allegations of github software being infected with malware. E.g., in r/netsec there is a thread titled [Analysis] Massive Active GitHub Malware Campaign | Hundreds of Malicious Repositories Identified. Is there any other safe/secure way to download VirtualBuddy?
This is a very reasonable concern, and it is wise to be cautious about downloading software from all sources. There were known attacks on Github open source projects and many fake repositories were created to push malware, but Github has been quite active in tackling that problem.
One of the ways to confirm a project is valid is to make sure the URL and account updating the repository matches precisely that of the developer. This is helpful because one of the methods the attackers were using was to create lookalikes by cloning repositories and making similar URLs and usernames but that had hosted the compromised codebases instead of legitimate code. Thus it is absolutely critical to know the source URL and account at codebase is legitimate.
It’s also worth mentioning there are alternatives to VirtualBuddy that do not require using Github, including apps like UTM, or the command line tart utility, Parallels (paid, 14 day free trial), etc.