Frank Osterfeld

For the record, one runs into the same issues with Monterey (I guess that was to be expected).

The host machine is a MacBook Pro (13-inch, 2020), btw, which might be too new for Mojave, I wonder if there's any CPU/EFI flags etc. passed through by virtualbox that...

Actually, the VM works on another (windows...) host! So this might be fixable by explicitly setting one or multiple of "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct", "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion", "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" and so on. I'll investigate. Would that...

If I add the following line to my Vagrantfile, the VM boots on the Macbook Pro 2020: vb.customize ["modifyvm", :id, "--cpuid-set", "00000001", "000306a9", "04100800", "7fbae3ff", "bfebfbff"]

@ekaiser-uptycs I don't think it would help, the installer is run on the host afaik, where it also checks for the host system. @bacongravy the ID also makes it work...

https://github.com/myspaghetti/macos-virtualbox/blob/master/macos-guest-virtualbox.sh might have a solution for this (search for "csr-active-config"), generating a nvram file and loading it in the EFI boot loader, if I read that code correctly.

I've created a pull request, but I can only test virtualbox here, so this needs to be applied for the other providers, too.

I accidentally uploaded the wrong installer... We'll probably do a 1.12.1 release

I updated the 1.12.0 installers to the new ones generated with "Craft", please test.

"It will appear disabled unless the feature enabled while compiling Charm." I guess we should hide it completely then.