virtualbox: Mojave box does not boot on 2020 Macbook about macinbox HOT 6 OPEN

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 prevent it from booting...

from macinbox.

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 be something to add to the macinbox scripts modifying the base box?

from macinbox.

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"]

from macinbox.

Would this perhaps enable Mojave building on Catalina if these were set when the vm was being created?

from macinbox.

@frankosterfeld Thanks for investigating this. Its not clear to me how to solve this generally. Presumably we would only want to call cpuid-set with these arguments for a box being run on a MacBook Pro 2020? Since macinbox doesn't know what hardware you're planning to run the box on, how could it properly configure the box? I suppose the Vagrantfile in the box itself could contain logic that determines what hardware it is running on, and passes different arguments?

from macinbox.

@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 on other hardware and operating systems, so it's not specific to the Macbook 2020. But I'm not sure either if it should be baked into the image, one might not want it when run on actually compatible hardware. I'm not sure what the best solution would be, it could be an option, or just a comment in the documentation about what to do in the Vagrantfile.

from macinbox.