Mastodawn

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.

🧵 No success yet.

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

🧵 … 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.

🧵 …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.

🧵 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.

🧵 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.

🧵 So it turns out sharing files without #GuestExtensions between #macOS in #VirtulBox and #Linux as a host system is drop-dead easy.

You just switch on SMB file sharing in macOS (#Monterey in my case).

#Konqueror or other CIFS/SMB-enabled file tools can than access your virtual Mac effortlessly.

Simply reverse the game… not the host is the server, the guest OS is.

This of course works only in bridged network mode.

Funny that I didn't find this solution on the web.

🧵 The entire stupid idea of running #macOS #Monterey in #VirtualBox on #Linux comes from the sad fact that #DanteController by #Audinate keeps crashing in #Windows10 in Virtualbox.

It used to work, but then #Microsoft did some updates to Windows 10 (sic!) and since then it just crashes when it talks to #Dante devices on the network. I dug up an old version of Dante Controller, because I thought it was a problem with the recent version that is targeted to Windows11, but eventually this didn't help.

So, I will see if Dante Controller crashes in Monterey/Virtualbox, too.

The current Blackmagic Switchers app doesn't (yet) run on Monterey, apparently. But it runs in Windows 10.

Oh it's the crazy Linuxer again, nobody in #EventTech would use Linux anyways, blablabla, heard all of it.

But all of this is because software manufacturers don't provide Linux versions for tools that internally use Java or QT, both platform-independent.

Fun fact: Old #QLab (macOS only, no Windows) does work.

#Veranstaltungstechnik

🧵 The Blackmagic Atem Software Control does not run on #macOS #Monterey in #VirtualBox.

It does run on the same installation of Monterey on a MacBook Pro 2017.

So the situation is: #DanteController has quit working in #Windows10 in Virtualbox due to Windows updates (sic!). In macOS however, I can't run #Blackmagic #AtemControl. Funnily, #AtemSetup does work.

These are the three programs I need that don't run in #Wine.

I had a #chatGPT about it. It was interesting, yet not entertaining. This thing still can't handle data sparsity. So it can't help with special problems. It keeps telling shit and even contradicts itself. So, when things get hard, #LLM-based #AI doesn't help at all.

So, is there any human intelligence having an idea?

Morten Mosgaard 3d ago

@nielso oh, Qlab on a Linux!

I haven't tried the audio yet, … but probably the video from QLab doesn't make sense in this setting. 🤪

Morten Mosgaard 3d ago

@nielso the theatreplays I have setup in Qlab is only Lights and Sound, so that could be fine for me!

Herr Irrtum! 🔊4d ago

@nielso Ha, cool out of the box thinking here! Nice you found your solution then :)

Herr Irrtum! 🔊4d 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.

I collected a number of hacky parameters for VirtualBox that are supposed to help running macOS: https://pastebin.com/c0GLNFih

Acually I'm not sure about most of them, but the last line does successfully set screen resolution:

vboxmanage setextradata "macOS" VBoxInternal2/EfiGraphicsResolution 1920x1080

(macOS being the name of the VM)

I don't know yet how stable this entire thing is, but so far file exchange is the only thing I'm missing.

I thought that this would internally work via CIFS anyways, but I might be wrong.

As said, I can access my Samba/CIFS server over the network, but this setup is on my laptop, so that server is out of reach, and I don't want to set up a Samba server locally. I could, but it I'd like to have a simpler solution.

vboxmanage modifyvm "macOS" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebf - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

Pastebin

It might be that Monterey is too new for the guest extensions to work. They are not intended to work anyways… but older versions of macOS might be too old to run what I need.

The shared clipboard seems to work though.