Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
-
- Posts: 12
- Joined: 11. Sep 2021, 02:11
Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
I have a one-day-old mb pro configured for the U.S., arrived with Big Sur and upgraded itself to macos 11.5.2 on its first day. I downloaded & installed VirtualBox 6.1.26, the latest today. VBox installs and runs, but will not launch a VM, error is "Kernel driver not installed (rc=-1908)". Per comments in this thread (viewtopic.php?f=8&t=103660) and others, I kept the System Preferences -> Security & Privacy panel open on the General tab during the install and also during the attempted launch of a VM. That panel never showed a note about Oracle, never allowed me to grant additional perms to Oracle. Some people have posted that this panel has a "Details" button but I do not see that button.
Followed a suggestion by mh- above, I removed VBox 6.1.26 using its removal tool and installed 6.1.22, again keeping the Security & Privacy panel open on the General tab the whole time, but that tab didn't show that VBox 6.1.22 needs permission either.
Maybe the behavior is different for people who upgraded from Catalina, IDK.
I speculate that Apple is simply ahead of Oracle/VirtualBox right now and Imma have to wait for Oracle to catch up. Frustrating, I finally have shiny new hardware with enough RAM to keep a VM happy but I cannot run a VM. Argh!
Please speculate for me: this new MBP has a lot of corporate lock-down stuff on it. I can sudo but don't have complete sudo powers. For example I cannot change properties like the computer name, whether the lockscreen requires a password (yes), etc. Could those restrictions also block me from approving Oracle as a publisher of kernel extensions?
Followed a suggestion by mh- above, I removed VBox 6.1.26 using its removal tool and installed 6.1.22, again keeping the Security & Privacy panel open on the General tab the whole time, but that tab didn't show that VBox 6.1.22 needs permission either.
Maybe the behavior is different for people who upgraded from Catalina, IDK.
I speculate that Apple is simply ahead of Oracle/VirtualBox right now and Imma have to wait for Oracle to catch up. Frustrating, I finally have shiny new hardware with enough RAM to keep a VM happy but I cannot run a VM. Argh!
Please speculate for me: this new MBP has a lot of corporate lock-down stuff on it. I can sudo but don't have complete sudo powers. For example I cannot change properties like the computer name, whether the lockscreen requires a password (yes), etc. Could those restrictions also block me from approving Oracle as a publisher of kernel extensions?
Last edited by scottgus1 on 11. Sep 2021, 14:51, edited 1 time in total.
Reason: split to new topic, added previous topic's link
Reason: split to new topic, added previous topic's link
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
This could be the blocker. The IT overlords empowered by the bosses can and do control what is installed on a computer they have dominion over if they want to. You'd need to get permission from the boss to have Virtualbox on your company computer, then the IT folks will release what needs to be released to allow Virtualbox to install.chrisinmtown wrote:this new MBP has a lot of corporate lock-down stuff on it.
-
- Posts: 12
- Joined: 11. Sep 2021, 02:11
Re: Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
Anyone try this in Big Sur 11.6 yet?
-
- Volunteer
- Posts: 708
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
One thing you might try is to look at the installer log and see what is failing during the installation.
1. Run the uninstaller & reboot
2. Start the installer and open it's log window. Select the option to show everything (the default is Errors Only)
3. Open the Security & Privacy prefs and unlock (just in case it works this time)
3. Run the installer, but before you quit, copy/paste/save the contents of the log window to a text file.
4. Quit the installer.
You could zip the text file and attach it to this thread. You may be able to spot any permissions errors etc yourself.
1. Run the uninstaller & reboot
2. Start the installer and open it's log window. Select the option to show everything (the default is Errors Only)
3. Open the Security & Privacy prefs and unlock (just in case it works this time)
3. Run the installer, but before you quit, copy/paste/save the contents of the log window to a text file.
4. Quit the installer.
You could zip the text file and attach it to this thread. You may be able to spot any permissions errors etc yourself.
-
- Posts: 12
- Joined: 11. Sep 2021, 02:11
Re: Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
Thanks for the suggestion to watch the installer log. I attached it below. There are definitely some errors about KEXT but I'm not sure how to interpret, it complains about something that does not look like Virtualbox. I'll paste one here:
Sep 15 06:15:47 MYLAPTOP package_script_service[956]: ./postflight: Error Domain=KMErrorDomain Code=31 "Error occurred while building a collection: in '/Library/StagedExtensions/Library/Application Support/Websense Endpoint/DLP/WebsenseEndpointDLP.kext/Contents/PlugIns/WebsenseEndpointProcess.kext/Contents/PlugIns/ WebsenseEndpointProcessKpi.kext/WebsenseEndpointProcessKpi' missing __TEXT segment" UserInfo={NSLocalizedDescription= Error occurred while building a collection: in '/Library/StagedExtensions/Library/Application Support/Websense Endpoint/DLP/WebsenseEndpointDLP.kext/Contents/PlugIns/WebsenseEndpointProcess.kext/Contents/PlugIns/ WebsenseEndpointProcessKpi.kext/WebsenseEndpointProcessKpi' missing __TEXT segment}
- Attachments
-
- vbox-install.txt
- (25.41 KiB) Downloaded 27 times
-
- Volunteer
- Posts: 708
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
That does indeed look odd. Before running the installer, did you try running
Code: Select all
sudo kmutil clear-staging
-
- Posts: 12
- Joined: 11. Sep 2021, 02:11
Re: Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
Thanks for the suggestion to cleared staged kernel extensions. What does that mean anyhow? Why would kernel extensions be staged?
Anyhow, I ran that command and it reported that it cleared staged extensions, then I rebooted and retried the VBox installation. Still get the same kind of error about Websense Endpoint/DLP/WebsenseEndpointDLP.kext as shown in the log attached above. I don't know what kernel extension that is, or if it's even relevant to my problems with VBox, but that's the only obvious error in the install log.
Anyhow, I ran that command and it reported that it cleared staged extensions, then I rebooted and retried the VBox installation. Still get the same kind of error about Websense Endpoint/DLP/WebsenseEndpointDLP.kext as shown in the log attached above. I don't know what kernel extension that is, or if it's even relevant to my problems with VBox, but that's the only obvious error in the install log.
-
- Volunteer
- Posts: 708
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
I think that WebsenseEndpointDLP.kext is part of the software installed by your corporate overlords.
Depending on your relationship with the overlords, it would be good to talk to them about temporary removal to see if that solves your VirtualBox problem.
Depending on your relationship with the overlords, it would be good to talk to them about temporary removal to see if that solves your VirtualBox problem.
-
- Posts: 12
- Joined: 11. Sep 2021, 02:11
Re: Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
A colleague suggested that Forcepoint DLP left behind old kernel extensions that weren't compatible with Big Sur. Same colleague offered this procedure, which worked on a mac *upgraded* to Big Sur. I don't know if it works on a Mac that arrives with Big Sur:
1. Reboot into recovery mode (hold Command-R while the machine boots)
2. From the recovery mode terminal run:
> trigger-panic-medic: Remove the auxiliary kext collection and remove all kext approvals on the next boot.
1. Reboot into recovery mode (hold Command-R while the machine boots)
2. From the recovery mode terminal run:
kmutil trigger-panic-medic --volume-root /Volumes/Macintosh\ HDFrom the man page:
> trigger-panic-medic: Remove the auxiliary kext collection and remove all kext approvals on the next boot.
Re: Big Sur 11.5.2. issues.Kernel driver not installed (rc=-1908)
This is what worked for me on Big Sur 11.6. Sharing in case this helps anyone else:
1. Opened the `VirtualBox-6.1.26-145957-OSX.dmg` and ran the uninstall script from there
2. Cleared the kernel module staging from the terminal with `sudo kmutil clear-staging` ***
3. Installed VirtualBox again
4. NOW the System Preferences -> Security & Privacy had the "Allow" button for me to click and requested a reboot
Modules then loaded:
VirtualBox worked again. No rescue mode surgery needed!
*** Per the man page "The kextcache utility has been deprecated. It should no longer be necessary to use. See kmutil(8)". Clearing staging with kextcache doesn't seem to do anything useful.
1. Opened the `VirtualBox-6.1.26-145957-OSX.dmg` and ran the uninstall script from there
2. Cleared the kernel module staging from the terminal with `sudo kmutil clear-staging` ***
3. Installed VirtualBox again
4. NOW the System Preferences -> Security & Privacy had the "Allow" button for me to click and requested a reboot
Modules then loaded:
Code: Select all
/usr/bin/kmutil showloaded --list-only | grep virtualbox
No variant specified, falling back to release
199 3 0xffffff7f9cc6a000 0xb2000 0xb2000 org.virtualbox.kext.VBoxDrv (6.1.26) 37337E1D-D61B-38BA-BD5B-0A8D9BBB7C30 <8 6 5 3 1>
201 0 0xffffff7f9cd47000 0x5000 0x5000 org.virtualbox.kext.VBoxUSB (6.1.26) 0784DD75-85BE-3C02-9386-FF959F30604D <200 199 66 8 6 5 3 1>
202 0 0xffffff7f9cd42000 0x4000 0x4000 org.virtualbox.kext.VBoxNetFlt (6.1.26) F204C69C-BD5D-3A22-907F-9E45CB2F4241 <199 8 6 5 3 1>
203 0 0xffffff7f9cd3c000 0x2000 0x2000 org.virtualbox.kext.VBoxNetAdp (6.1.26) FB699412-C6ED-3390-85AF-D959FBBC9C79 <199 6 5 1>
*** Per the man page "The kextcache utility has been deprecated. It should no longer be necessary to use. See kmutil(8)". Clearing staging with kextcache doesn't seem to do anything useful.