Live data from Hacker News

VirtualBuddy: Virtualize macOS 12 and later on Apple Silicon

github.com

51–60 of 65 posts

Re: VirtualBuddy: Virtualize macOS 12 and later on Apple Silicon

#51

Earlier quoted context omitted.

VirtualBuddy is still experimental

> VirtualBuddy is still experimental Really? You’ve gotta be trolling, right?

Sounds like you're the one trolling when the site says this upfront.

WARNING: This project is experimental. Things might break or not work as expected.

Re: VirtualBuddy: Virtualize macOS 12 and later on Apple Silicon

#54
post #24

Apple provides their own hypervisor framework and virtualization framework. Roughly 50 lines of code and you can boot up a mac vm which they support.

This has been around for a while, but I recall it was incredibly slow compared to even qemu. Has that improved?

Re: VirtualBuddy: Virtualize macOS 12 and later on Apple Silicon

#55

Earlier quoted context omitted.

Reportedly M2 supports nested virtualization though.

But why would you ever want to?

Docker desktop for macOS requires a linux vm on the macOS host, so nested virtualization is required if you want to use docker desktop inside the macOS guest.

Other Tools like multipass kind and minikube on the guest will not work

Re: VirtualBuddy: Virtualize macOS 12 and later on Apple Silicon

#56

Anyone using Parallels to virtualize MacOS on M1 Macs?

Yes, and it's terrible. You can't sign into icloud and you can't maximize a VM to 4k resolutions. It's usable, but for $100 they could do much much better.

Those are well known limitations of Apple virtualized OSes. The threshold for solving those issues involves using a different virtualization framework and a lot of reverse engineering.

Re: VirtualBuddy: Virtualize macOS 12 and later on Apple Silicon

#57
post #3

Earlier quoted context omitted.

There are additional instructions only available on Apple chips beyond the aarch64 standard, so I don't think that this could be done in hardware (someone correct me if I'm wrong because this isn't my area) Of course it's possible in software in principle but obviously that would be awful.

Of course it's possible in software in principle but obviously that would be awful. The Hackintosh community emulated SSE2/3 to allow OS X to run on CPUs that didn't have those extensions, and AFAIK it worked reasonably well: http://www.tutilapia.com/2011/11/a-little-about-hackintosh-i...

That’s all well & good, but it’s a completely different game when you’ve got custom secure enclaves & “AI” blocks to deal with.

Re: VirtualBuddy: Virtualize macOS 12 and later on Apple Silicon

#58
post #51

Earlier quoted context omitted.

> VirtualBuddy is still experimental Really? You’ve gotta be trolling, right?

Sounds like you're the one trolling when the site says this upfront. WARNING: This project is experimental. Things might break or not work as expected.

Look at the code for the one he’s suggesting. It’s the same essentially. One is just more upfront about giving its visitors a clear understanding. Taken out of context I can maybe see what you mean, but like come on, it’s not an effort to keep up is it?

Re: VirtualBuddy: Virtualize macOS 12 and later on Apple Silicon

#60

Earlier quoted context omitted.

Yes, I use macOS as development VM on a maxed out 16 inch M1 MacBook Pro. It all works as expected, except you don’t have any VM settings (e.g. how much ram / cpu you want to give the VM) and Docker doesn’t run inside the VM.

You can change some of the settings by editing an ini file. https://kb.parallels.com/en/128842

Oh, I didn't know that. Thanks a lot!
Post reply on HN