I am not sure why the other Monterey thread is locked.
1. When installing virtualbox on OSX, it will fail. In Preferences, Security, General, VirtualBox/Oracle needs to be added as allowed identities. After that, the installation should succeed.
2. The kernel modules are not loaded, because the VirtualBoxStartup.sh script does only check for Big Sur for an alternative way of loading the virtualbox kernel modules.
Edit '/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh' (as root/via sudo), and change:
At line 73, add:
Code: Select all
MACOS_MAJOR_VERSION=$(sw_vers -productVersion | sed 's/\([0-9]*\).*/\1/')
Code: Select all
if [[ ${MACOS_VERS} != 11.* ]]; then
Code: Select all
if [[ ${MACOS_MAJOR_VERSION} -lt 11 ]]; then
This script is executed at startup time, and will load the needed kernel modules.
If you just done this, you can execute 'sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart' or restart your Mac.
3. When starting up a virtual machine in headless mode, it will fail:
Code: Select all
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "622d3cc8-858f-4237-b102-1b6167ecaa70", "--type", "headless"]
Stderr: VBoxManage: error: The virtual machine 'alma8-rf1_yb-1_1634050416725_18262' has terminated unexpectedly during startup because of signal 10
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
The blunt solution to this is to startup the VMs not in headless mode (in vagrant: set the virtualbox property 'gui' to true (default false, which means headless mode):
Code: Select all
subconfig.vm.provider :virtualbox do |vb|
vb.gui = true