What utility is there in running Multipass on Apple Silicon, beyond just spinning up instances of Ubuntu in a walled garden?
I address this question to any user in a similar circumstance because I think I may be missing something.
I’m especially interested in hearing from members of the Multipass-on-macOS dev team because I think they really ARE missing something.
When attempting to launch an instance with:
multipass launch --network en0 --network name=bridge0,mode=manual
launch failed: The bridging feature is not implemented on this backend
That “backend” on Apple Silicon being the default QEMU driver.
Documentation tells us Multipass’ ability to create a bridged interface is dependent on VirtualBox being installed on the host Mac and the user switching to the VirtualBox driver.
But of course, VirtualBox does not run on ARM processors and reading the tea leaves over at Oracle, likely never will.
This leaves users of Multipass on Apple Silicon in a bit of a Catch-22. We can neither create bridge interfaces with the default QEMU driver nor can we run VirtualBox and invoke its driver.
Since it appears that QEMU is the only driver available for the new Mac ARM processors I’ve had to recommission an Intel Mac new in 2010 and hack it to run Catalina to get Multipass and VirtualBox running in the same space just to get a feel as to how Multipass can save me cycles spinning up instances of Ubuntu.
To be honest, I’m not sure its any easier than cloning VMs in VirtualBox already configured with bridged interfaces.
What have I missed?