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. During the holidays, I decided to upgrade from Catalina to Big Sur ( macOS 11.1 (20C69) to be precise).

Virtualbox extension pack 5.2.20