Oh well, I guess that's what you get for running something like macOS as a development machine and update too early. Additionally, VMware appears to be quite a bit more performant compared to VirtualBox. And by purchasing the plugin, I'm actually supporting OSS development of Vagrant. This answer did not work as well for me.Įdit: For the time being, VMware Fusion plus the Vagrant VMware plugin appear to do the job quite nicely. Maybe someone else has experienced the same issue as I have and can shine some light on the steps taken to get stuff working on Big Sur. For the time being, it means I'm dead in the water, probably having to re-install Catalina from scratch or buy both a VMware and a VMware Vagrant plugin license. I need VirtualBox for my Vagrant development boxes. As far I can gather, kernel extensions are no longer supported in Big Sur, hence the breakage of software that relies on them, like VirtualBox.
Like manually accepting kernel extensions via System Preferences > Security & Privacy. The test versions also do not work at all, despite completing the installation.Īll other articles and forum entries as well as Ask Different questions were either dismissed because the author was using a pre-release version of macOS 11 or describe situations that, to the best of my understanding, simply cannot occur on Big Sur.
I then tried pretty much everything in the giant thread out it on the VirtualBox forums. After dismissing it, the VM process crashes (throwing EXC_CRASH (SIGABRT)). On linux, open returned ENOENT.Įrror message. Where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. Make sure the kernel module has been loaded successfully. This fails with a rather expected Kernel driver not installed (rc=-1908)
Trying to start it works, although not booting up VMs. Afterwards, VirtualBox is present on the file system however. I'm apparently not alone in experiencing this. I followed the usual advice of using the VirtualBox_Uninstall.tool script to remove any trace of VirtualBox, rebooting, installing the latest stable version from a VirtualBox-6.1.16-140961-OSX.dmg disk image. The one thing I did not account for is that VirtualBox stopped working. Step 7: Remove sierra.iso and restart VM.During the holidays, I decided to upgrade from Catalina to Big Sur ( macOS 11.1 (20C69) to be precise).
#Macos virtualbox mac os#
Select the VirtualBox disk and choose Erase to format it as a Mac OS Extended (Journaled) drive. Note: In the installer, Go to Utilities > Disk Utility.
#Macos virtualbox install#
Insert sierra.iso to the sierra VM’s optical driver, and follow the instruction to install Sierra. VBoxManage setextradata "Sierra" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 VBoxManage setextradata "Sierra" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "Sierra" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Iloveapple" VBoxManage setextradata "Sierra" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "Sierra" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3"