Nielso

Trying to install #macOS #Monterey in #VirtualBox…

… is a lot harder than installing any current Linux anywhere.

Why doing so? Well, because of these suckers called #Audinate and the other suckers called #Microsoft. In Europe, #Windows10 gets occasional updates still, and the combination of an updated Windows 10, VirtualBox and #DanteController by Audinate has quit working… it had worked for many years, but they managed to destroy that. It's actually almost the only program I need to run on Windows directly, because it does not work in #Wine. But now I can't.

Dante Controller runs well on my old MacBook Pro 2017, though… on Monterey.

So, after resolving the issues of not having any drives by using the disk utility, the installer now says:

System rebooted automatically due to panic.

… so afraid.

10:14amWeb
Show threadNielso3h ago

🧵 No success yet.

Parameter tweaking… trying to install #macOS #Monterey in #VirtualBox. So far, only macOS panics and constant reboots.

Show threadNielso1h ago
🧵 … so, I went after some more parameter tweaking, the macOS Monterey installer in VirtualBox would take forever, or hang… so I went on doing other things. All of a sudden, a seemingly infinite time later, a friendly female voice sounded from my speakers, offering help in setting up my Mac in case I was visually impaired.
Show threadNielso1h ago

🧵 …getting closer to #macOS #Monterey in #VirtualBox on #Linux. Failing to install #GuestExtensions now, dunno why yet.

It feels terribly laggy and the screen resolution without the extensions is a joke.

Show threadNielso1h ago

🧵 btw, there is only little help on the web for running #macOS in #VirtualBox not in #Apple hardware, because according to Apple's EULA, it is illegal to run macOS on non-apple hardware.

It's not illegal for #Microsoft to enshittify even #Windows10 in VirtualBox beyond foobar levels, unfortunately. They did for me.

Show threadNielso46m ago

🧵 So, #GuestExtensions fail to install on #macOS #Monterey and I don't know why. I disabled protection using csrutil but that didn't solve it.

I can set different screen resolutions with vboxmanage, but shared folders don't work, altough I can see my Samba server in the network, I can't see the vboxsrv server.

What to do now?

I need to user certain tools that only run on macOS or Windows, but they quit working in #Windows10 after recent updates (sic!) and I don't want to use #Windows11, not even in #VirtualBox.

And yes, running macOS in VirtualBox on #Linux is conflicting with #Apple's EULA.

Show threadHerr Irrtum! 🔊19m ago
@nielso

I've tried it some years ago: There were git repos and even hacker News coverage with one click installers for KVM/Qemu and they worked.
What didn't work (for me, back then around 2020): Proper screen resolution, sound. Sometimes the screen got super glitchy.
Also not safe to run OS updates here. I ended up not using it.

Maybe that's better nowadays?

If not, it makes no sense to switch away from virtual box.

The screen resolution issue may be solved with a remote VNC connection from host to VM. RealVNC was the only VNC client that worked from Linux to Mac back than.

Shared folder: SCP/SFTP has you covered. Try Filezilla. Also try Syncthing instead of samba for direct access (however it's still a syncer, not a network drive). NFS should definitely work. Samba and newer MacOS implementations are no fun at all unfortunately.
sshfs works fine, but as always: Slow and jerky.