Skip to content

Instantly share code, notes, and snippets.

@christopher-baek

christopher-baek/VirtualBox Machine Modifications for macOS Monterey.md

Last active February 5, 2022 04:40
Show Gist options
  • Save christopher-baek/d452d75dfa2c22f91d420000cb43f93a to your computer and use it in GitHub Desktop.
Save christopher-baek/d452d75dfa2c22f91d420000cb43f93a to your computer and use it in GitHub Desktop.
Download ZIP
Raw
VirtualBox Machine Modifications for macOS Monterey.md

After creating a machine and BEFORE starting the machine with the ISO, make the following changes:

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

Most online resources say to set the GetKeyFromRealSMC value to 1, but this causes a VirtualBox error. This was needed when WSL2 and VirtualBox were installed at the same time, i.e., Hyper-V for VirtualBox was not working

Alternative DmiSystemProduct, DmiBoardProduct values: MacBookPro15,1, Mac-551B86E5744E2388

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment