Virtualbox On Mac Big Sur



Hello Everyone,
I have a Windows 10 PC and I use VirtualBox to host MacOS. This is done to learn the OS and to test a program.
I had MAC OS Mojave virtual machine and it worked okay. However I wanted to upgrade to MAC OS BIG SUR but upgrade failed as file system was not APFS. So I created a new machine and installed mac os big sur and after installation when it starts it stops at
'IOConsoleUsers : gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0'
What to do ? I am running latest version of virtual box.
Regards,
GR

Click and drag the slider bar to allocate memory to the virtual machine. You can also type the amount of memory in megabytes (MB) in the box to the right of the slider bar. MacOS needs at least 4 GB (8 GB recommended) to run macOS Big Sur. The more memory you can allocate, the better it will run. How to install macOS Big Sur on windows 10 PC / laptop via VirtualBox using macOS bootable ISO.Steps to install Apple Mac OS:1. Download & Install VirtualBox.

After I upgraded my Mac OS from version 10.15.7 to Big Sur 11.0.1, the Virtualbox VM crashed all the time. Erro message is below: Becker brothers piano serial number.

Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

I did a few searches on the web, it seems the problem occurred when the VirtualBox kernel driver is not loaded or permission is not right. In my case, it is related to the security setting in Mac OS. I need to provide permission to system modules from Oracle.

Note: This message only popup after you have new installation of Virtualbox.

I tried to reinstall Virtualbox a few times in my Mac to allow this, but did not work for me. Then I found another procedure with CMD line from web.

Source: https://www.virtualbox.org/ticket/19795

Apparently, there was a long discussion since Big Sur beta was released. Fortunately, there was a solution tested and posted by NickyD at the bottom of the thread.

Tested by NickyD: VirtualBox 6.1.16 r140961 running on BigSur macOS 11.0.1 (20B29) / Darwin 20.1.0

Tested by me: Virtualbox Offical release 6.1.16 ( r140961 (Qt5.6.3)) + BigSur MacOS11.0.1 (first public release of Big Sur), It worked well for me, too.

Step 1: sudo kextload -b org.virtualbox.kext.VBoxDrv

Step 2: Go into System Preferences->Security & Privacy

Step 3: Unlock the security center

Step 4: Approve the software by Oracle

Step 5:

sudo kextload -b org.virtualbox.kext.VBoxNetFlt
sudo kextload -b org.virtualbox.kext.VBoxNetAdp
sudo kextload -b org.virtualbox.kext.VBoxUSB

Step 6: Reboot

Info about Virtualbox kernel modules: https://www.virtualbox.org/manual/UserManual.html#externalkernelmodules

  • VBoxDrv: VirtualBox Linux kernel driver
  • VBoxNetFlt and VBoxNetAdp: network driver
  • VBoxUSB: USB support

I was not familiar with kextload, so I summarize some info collected from https://osxdaily.com/2015/06/24/load-unload-kernel-extensions-mac-os-x/

kext is Kernel extensions for short, which are modules of code that are loaded directly into the kernel space of Mac OS X, able to run at a low-level to perform a variety of tasks. Most kexts are part of the core Mac OS X system software, typically hardware device drivers, but some third party apps will install a kext as well.

kextload: cmd to load a kernel extension into Mac OS X.

sudo kextload /path/to/kext.kext

kextload -b: use the bundle identifier (which are frequently the targets of defaults commands)

sudo kextload -b com.apple.driver.ExampleBundle

Either way, hit return and with the entry of the administrator password the kernel extension will be loaded into Mac OS X.

kextstat: list the kernels loaded

$ kextstat |grep com.apple.driver.ExampleBundle
125 0 0xdddddd7f23351040 0x5000 0x5000 com.apple.driver.ExampleBundle (1) 12 8 7 5 4 2 1

kextunload: unload a kernal extension.

Virtualbox On Mac Big Sur

sudo kextunload -b com.apple.driver.ExampleBundle

Virtualbox

Or by pointing directly to the kernel extensions path:

Virtualbox Macos Big Sur Guest Additions

sudo kextunload /System/Library/Extensions/ThirdPartyMystery.kext