You don’t have to edit the configuration file. It’s already mentioned in this guide. So if you want to install macOS on VirtualBox, you should execute some codes before you try to install.
Please have a look at the code which we have provided in this article.

VBoxManage setextradata “macOS Big Sure Beta” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “iMac19,1”
VBoxManage setextradata “macOS Big Sure Beta” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-AA95B1DDAB278B95”

The first line of codes changes the product id and the second line changes the board id on VirtualBox.

I have received the error massage on “VirtualBox MAC OS X”. Would you please guide me how to edit vbox configuration file (XML) and add hw.model and board-id?

Thanks

Hey Faiz !
It works !! Thanks!
My old ‘rig’:
HP Elitebook 8470w (old faithful, military grade components), 14 inch 1600×900, Core i5, Intel4000HD+AMD Firepro, 10GB Ram, SSD 128 for booting, HDD 500GB for all ISO, VMDK (yes, I know, it slow, but for just tasting MAC OS, don’t mind).
VMWare Workstation Player 15 ver 15.5.6.
PLEASE ENSURE YOU ALLOCATEat least 50GB (not 40GB) VIRTUAL DISK for this DISK MONGER BIG MAC.
It’s a little bit tricky: if you have created virtual machine, DELETE IT.
Then create as usual you mount the BIG SUR iso,

That’s already mentioned in this post. The last section is for Virtualbox.
Just use a real Mac Board and Product ID. It should fix the issue.

Hey, Try this

smbios.reflectHost = "TRUE"
hw.model = "MacBookPro14,3"
board-id = "Mac-551B86E5744E2388"

P.S If inserting the above code didn’t solve the issue, then you may have to delete the VM and start over since macOS caches the VM information and does not allow macOS to be installed as VM.

So you can’t install on the disk? Is grayed out?
Do you install macOS on your Desktop or laptop>?

Is not working.

Hey, Jordan thank you for your suggestion. I’ve updated this article. Also, we’ve updated our Virtualbox article as well and last night we figured that how to bypass BiErrorDomain Error 3 message on Virtualbox.

Exit Virtulalbox

Do this on the command prompt (Run as Administrator):

cd "C:\Program Files\Oracle\VirtualBox\"
VBoxManage.exe modifyvm "macOS Big Sure Beta" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
VBoxManage setextradata "macOS Big Sure Beta" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac19,1"
VBoxManage setextradata "macOS Big Sure Beta" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "macOS Big Sure Beta" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-AA95B1DDAB278B95"
VBoxManage setextradata "macOS Big Sure Beta" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata "macOS Big Sure Beta" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

Start virtualbox again and now you will be able to select the drive and install macOS Big Sur Beta.

See here: https://i.imgur.com/xDJtcJG.png

After doing the below the installation on VirtualBox is fast as hell again:

This is due to the Windows 10 Version 2004 May Update !

If you do the following if you have the same issues than it will work again:

1. Control panel -> Programs and Features -> Turn Windows Features on or off -> Uncheck Hyper-V and Windows Hyper-Visor Platform

Additional Notes for Windows Hosts

2. To check the status of Hyper-v in Windows 10, | Run | OptionalFeatures.exe, and look for the “Hyper-V” option. The box should be empty, not checked or shaded. If you want to be absolutely sure that Hyper-v is gone then open an administrator command console and type “bcdedit /set hypervisorlaunchtype off”. Make sure to fully power down and reboot the host after changing the Hyper-v setting.

3. On some Windows hosts with an EFI BIOS, DeviceGuard or CredentialGuard may be active by default, and interferes with OS level virtualization apps in the same way that Hyper-v does. These features need to be disabled. On Pro versions of Windows you can do this using gpedit.msc (set Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security to Disabled. CredentialGuard is a subset of DeviceGuard, so disabling the former should be enough. If you cannot use gpedit for some reason then the equivalent registry hack is to find the key

HKLM|SYSTEM|CurrentControlSet|Control|DeviceGuard|EnableVirtualizationBasedSecurity|Enabled

and set it to 0.

4. On Win10 hosts, check Windows Defender > Device Security > Core Isolation Details and make sure settings in this panel are turned off, reboot the host from power down if you needed to make changes. “Core isolation [includes] security features available on your device that use virtualization-based security” …which is why they can interfere with VirtualBox.

After doing this masOS Big Sure Beta will run normal again on VirtualBox