VirtualBox 6.1.28 kext issues on MacOS Monterey

For discussions related to using VirtualBox on Mac OS X pre-releases
iainH
Posts: 2
Joined: 27. Oct 2021, 02:52

VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by iainH »

This issue is also recorded in the Vagrant GitHub page ("Vagrant up issues in Mac OS Monterey #12557")

Attempt to start the VM from the VirtualBox GUI:
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.

This is after kexts apparently are loaded:
sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart
Password:
Unloading VBoxUSB.kext
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxUSB
Unloading VBoxNetFlt.kext
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxNetFlt
Unloading VBoxNetAdp.kext
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxNetAdp
Unloading VBoxDrv.kext
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxDrv
Error: VBoxDrv.kext is already loaded
Error: VBoxUSB.kext is already loaded
Error: VBoxNetFlt.kext is already loaded
Error: VBoxNetAdp.kext is already loaded
Fatal error: VirtualBox
This issue is also recorded in the Vagrant GitHub page ("Vagrant up issues in Mac OS Monterey #12557")
Attempt to have vagrant start the VM via the CLI:
...
==> local-BAPC9: Checking if box 'geerlingguy/drupal-vm' version '2.0.12' is up to date...
==> local-BAPC9: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp
DimaStorozhuk
Posts: 2
Joined: 31. Oct 2021, 18:45

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by DimaStorozhuk »

Similar issue on docksal.
(docksal) Progress state: NS_ERROR_FAILURE
(docksal) VBoxManage: error: Failed to create the host-only adapter
(docksal) VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
(docksal) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(docksal) VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp
(docksal) 
(docksal) This is a known VirtualBox bug. Let's try to recover anyway...
Error creating machine: Error in driver during machine creation: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninsta
DimaStorozhuk
Posts: 2
Joined: 31. Oct 2021, 18:45

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by DimaStorozhuk »

I am not sure why admins locked the related discussions:
forums . virtualbox . org /viewtopic.php?f=39&t=104265
forums . virtualbox . org /viewtopic.php?f=39&t=103438
iainH
Posts: 2
Joined: 27. Oct 2021, 02:52

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by iainH »

I must admit that I have found an alternative route since I have Parallels Desktop installed on my Mac and provisioning a new Virtual Ubuntu machine was a matter of 1) changing the name of the vagrant box and 2) using

Code: Select all

vagrant plugin install vagrant-parallels   && vagrant up --provider=parallels
and deleting VirtualBox from my machine.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by scottgus1 »

DimaStorozhuk wrote:I am not sure why admins locked the related discussions:
Usually we'll lock a series of duplicate-discussion topics where the problem has been discussed in another topic, to encourage 'me-too' posters to read the topic where the solution was presented.

Solution to this one, essentially, is that Monterey is not a supported host OS yet, and the devs are working on it. Monterey just went final release a few days ago, meaning Apple should theoretically have stopped twiddling with it. Now the devs can lock in on what they need to do to support Monterey. Same thing happened with Catalina and Big Sur.
darksk4
Posts: 1
Joined: 2. Nov 2021, 16:47

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by darksk4 »

I do have workaround though, you just need to reinstall the installer again and again once the error is encountered. Still waiting for the correction
ewalbridge
Posts: 1
Joined: 2. Nov 2021, 23:06

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by ewalbridge »

No need to re-install VB. After reboot just run the commands below to re-load the kexts.
sudo kextload -b org.virtualbox.kext.VBoxDrv
sudo kextload -b org.virtualbox.kext.VBoxNetFlt
sudo kextload -b org.virtualbox.kext.VBoxNetAdp
sudo kextload -b org.virtualbox.kext.VBoxUSB

NOTE: Headless Start does not work using the commands above, only Normal Start.
Last edited by ewalbridge on 3. Nov 2021, 18:58, edited 1 time in total.
SRM-1355
Posts: 1
Joined: 3. Nov 2021, 05:16

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by SRM-1355 »

ewalbridge wrote:No need to re-install VB. After reboot just run the commands below to re-load the kexts.
sudo kextload -b org.virtualbox.kext.VBoxDrv
sudo kextload -b org.virtualbox.kext.VBoxNetFlt
sudo kextload -b org.virtualbox.kext.VBoxNetAdp
sudo kextload -b org.virtualbox.kext.VBoxUSB
This worked for me, thank you! I didn't have to give permissions via "Security & Privacy" either
Glen Palmer
Posts: 4
Joined: 24. Jan 2014, 17:18

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by Glen Palmer »

ewalbridge wrote:No need to re-install VB. After reboot just run the commands below to re-load the kexts.
sudo kextload -b org.virtualbox.kext.VBoxDrv
sudo kextload -b org.virtualbox.kext.VBoxNetFlt
sudo kextload -b org.virtualbox.kext.VBoxNetAdp
sudo kextload -b org.virtualbox.kext.VBoxUSB

NOTE: Headless Start does not work using the commands above, only Normal Start.
Thanks ewalbridge, this worked perfect for me also .... I was using the uninstall / reinstall method until this morning!

Thanks again

Glen
hectornavarro
Posts: 3
Joined: 24. Sep 2021, 17:55

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by hectornavarro »

still same issue ... vboxnet0 appears after kext loaded but not after reboot ... vagrant fails too so I have a mix of issues ... no vboxnet0 interface or vagrant error (even w/ vboxnet0 interface) when headless.
thnx in adv. cheers.
XavierR
Posts: 23
Joined: 11. Apr 2012, 20:22

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by XavierR »

ewalbridge wrote:No need to re-install VB. After reboot just run the commands below to re-load the kexts.
sudo kextload -b org.virtualbox.kext.VBoxDrv
sudo kextload -b org.virtualbox.kext.VBoxNetFlt
sudo kextload -b org.virtualbox.kext.VBoxNetAdp
sudo kextload -b org.virtualbox.kext.VBoxUSB

NOTE: Headless Start does not work using the commands above, only Normal Start.
Thanks, but sorry, it did not work for me: when I started the VM the Macos (host) kernel crashed (stack overflow) and the computer restarted itself.
I have several computers and as usual update early the one that I do not use much so as to see the problems; thus this is not blocking for me (the machines that I use every day are still on Big Sur) and I will patiently wait for Monteray support in VB.
granada29
Volunteer
Posts: 691
Joined: 3. Mar 2015, 07:27
Primary OS: Mac OS X other
VBox Version: OSE other
Guest OSses: Linux, macOS, Windows

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by granada29 »

XavierR wrote: Thanks, but sorry, it did not work for me: when I started the VM the Macos (host) kernel crashed (stack overflow) and the computer restarted itself.
Are you running VirtualBox 6.1.28 ?
I saw this kernel crash before updating to 6.1.28
XavierR
Posts: 23
Joined: 11. Apr 2012, 20:22

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by XavierR »

granada29 wrote:
XavierR wrote: Thanks, but sorry, it did not work for me: when I started the VM the Macos (host) kernel crashed (stack overflow) and the computer restarted itself.
Are you running VirtualBox 6.1.28 ?
I saw this kernel crash before updating to 6.1.28
Indeed, you are right, I was running on an old version.
I just updated to 6.1.28. In the process, it first failed until I allow some extensions in the privacy settings, and after I did and restart the computer, the update completed smoothly. Now, the VM runs right away under the new version of VB.
I guess what I just did is the reinstall thing mentioned upthread.

I will use the VM some to see if compatibility issues arise.
klaus
Oracle Corporation
Posts: 1115
Joined: 10. May 2007, 14:57

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by klaus »

The stack overflow fix went last minute into 6.1.28, so any older VirtualBox version won't be usable with Monterey. 6.1.28 still has bugs, as mentioned. Could you try with this test build? It is notarized, to avoid the usual SIP trouble...
ehaase
Posts: 2
Joined: 22. Apr 2017, 10:06

Re: VirtualBox 6.1.28 kext issues on MacOS Monterey

Post by ehaase »

klaus wrote:The stack overflow fix went last minute into 6.1.28, so any older VirtualBox version won't be usable with Monterey. 6.1.28 still has bugs, as mentioned. Could you try with this test build? It is notarized, to avoid the usual SIP trouble...
Test build installation ends with some error. However, after okaying the kexts in Security Settings and rebooting, the 6.1.29 test build comes up when you start it, no longer complains about missing drivers.
So finally, great, a VirtualBox installation survives a reboot again (no longer needs to be reinstalled or have the magic kext script above executed).

Thanks a bunch!
--Enver
Post Reply