The virtualbox linux kernel driver vboxdrv is either

VirtualBox error : kernel driver not installed(rc=-1908) [closed]

Want to improve this question? Update the question so it’s on-topic for Stack Overflow.

Closed 8 months ago .

I tried to set up an virtual machine on Ubuntu 12.10.I installed Oracle Vm VirtualBox Manager. Then, i followed the steps and i choose .iso file from settings>storage.Then clicked live cd/dvd option.Then OK,when i clicked to start button i get such an error :

I reinstalled program and rebooted pc, but not worked.Also, updated kernel driver but not worked.What can be done to solve it ?

18 Answers 18

Thought I’d give my 2 cents for those who use MACs

ps. I have this issue everytime I get a Linux kernel update in Ubuntu. The instructions that it gives do not work for me but these two commands work everytime. It would be nice if everytime I got a kernel update these two commands would automatically run afterwards.

I have a solution that works for MacOS users:

You have to restart your system and press Command (⌘) + R during the loading. It will start the Recovery mode.

Now that you’re on the Recovery Mode, click on Utilities (top bar) and Terminal.

You have your terminal opened? Enter, it will add Oracle in the authorisation list to access the kernel.

spctl kext-consent add VB5E2TV963

(I’m on a Mac with this solution) I tried the first few answers on this board (so you might need those as well first), but then finally I Allowed Oracle to «load software» under System Preferences -> Security & Privacy -> in the bottom right, click «Allow. » Then a dialog box with checkbox options might come up, search for Oracle and check the box next to it. Click OK out of everything. (I also updated the preference above the «Allow. » button to Allow apps downloaded from: to «App store and identified developers«) After all of this I rebooted and I no longer see this -1908 error when running a VM. Again, I’m on a Mac, running Big Sur 11.2.1.

Goto BIOS setup and Make secure boot Disable It worked for me.

did you try the command /etc/init.d/vboxdrv setup What was the output ?

Had recently the same problem on Ubuntu 18.04. Apparently, virtual box 6.+ has some issues with gcc-7. These steps did the job for me:

sudo apt-get purge virtualbox-*

sudo apt-get install gcc-8 g++-8

setting default gcc to gcc-8

sudo update-alternatives —install /usr/bin/gcc gcc /usr/bin/gcc-8 800 —slave /usr/bin/g++ g++ /usr/bin/g++-8

and reinstalling virtualbox with the debian installer did it for me!

Источник

Virtualbox Kernel driver not installed [duplicate]

I tried to use my Virtual Box and this is the error I received — (I just updated to the new Ubuntu also) and I am VERY new at this Linux OS.

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

24 Answers 24

Re-install virtualbox-dkms package first

After that You can enable it manually

Most probably all you have to do is run

(or install dkms from the software center)

and write your password.

if you have any error with this commands use this one

here is solution which works for me on 12.10:

Install the latest version of virtualbox according your architecture and distribution version from https://www.virtualbox.org/wiki/Linux_Downloads

run sudo apt-get install build-essential linux-headers-`uname -r`

run sudo /etc/init.d/vboxdrv setup

Last two steps quoted from one of the comments to the bug on the same theme — https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1016165

In Ubuntu 14.04, 64 bit, what worked for me is

On 12.10, these solutions all failed for me. However the following worked:

and paste in this line, then save:

(replace quantal with your release’s codename)

to update your machine to the latest

Then install Oracle’s version:

(replacing 4.3 with the version you are targeting)

Should work now. Don’t forget to download the extension pack from http://www.virtualbox.org as well.

Another reason why this can happen is that you have an older GCC version (like I had GCC 4.8 installed on Ubuntu 16.04) set as default (by, for example, using update-alternatives ) when you try to update or reinstall VirtualBox.

Just go back to default GCC version that came with your distro for VirtualBox installation, and it’ll work fine.

You can then switch back to an older GCC version after VirtualBox is installed.

I have the same issue and solved by these two steps:

I have deb http://download.virtualbox.org/virtualbox/debian precise contrib in my /etc/apt/sources.list , to be able to use Virtualbox 5.x.

Faced with the same error, I tried all of the methods here and none work but this (bandwith-wasting) one:

1. sudo apt-get purge virtualbox virtualbox-4* virtualbox-5*
2. Reboot
3. sudo apt-get install virtualbox-5.0
4. Install the latest extension pack from https://www.virtualbox.org/wiki/Downloads

Just use three command for ubuntu users.

Took me a long time to solve this issue. Had this problem with vBox across 2 distros (Ubuntu and Arch).

I had dkms and all the modules already installed and compiled into my kernel, yet I still got a module related error message when I tried to run a vBox virtual machine.

If your vBox GUI starts without a hitch but get an error telling to install the VBoxDrv kernel module when you try to run a virtual machine, your problems are not related to installing the modules into your kernel but ACTIVATING THEM in modprobe which the module installation script fails to do.

To load a module manually (such as vboxdrv in your case), open a terminal prompt and put in :

If you Virtual Machine runs after that without giving you an error message, then you can activate the vboxdrv module permanently by going to /etc/modules-load.d/ and making a .conf file (such as vbox.conf ). In the .conf file the names of the vbox kernel modules you want to add, such as: vboxdrv .

Save and reboot

You can also ad these optional modules: vboxnetadp , vboxnetflt and vboxpci

From Vbox’s wiki:

vboxnetadp and vboxnetflt are both needed when you intend to use the «Host-only networking» feature. More precisely, vboxnetadp is needed to create the host interface in the VirtualBox global preferences, and vboxnetflt is needed to launch a virtual machine using that network interface.

vboxpci is needed when your virtual machine needs to pass through a PCI device on your host.

Note: If the VirtualBox kernel modules were loaded in the kernel while you updated the modules, you need to reload them manually to use the new updated version. To do it, run vboxreload as root.

Источник

VirtualBox выдаёт ошибкуKernel driver not installed (rc=-1908)(linux ubuntu 20.04LTS)

В линукс честно говоря нуб. Вот что пишет программа:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please reinstall virtualbox-dkms package and load the kernel module by executing

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system’s documentation for more information.

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

Телепаты в отпуске. У тебя проблема с запуском Ubuntu внутри VirtualBox или проблема с запуском VirtualBox на Ubuntu?

Что в чем ты запускаешь?

Судя по всему, у тебя не подтягивается модуль коробки.

VirtualBox на Ubuntu

А, хорошо. Теперь покажи выводы

Linux ivan-X551CA 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal

ls -l /sys/firmware/efi

итого 0 -r–r–r– 1 root root 4096 авг 25 19:05 config_table drwxr-xr-x 2 root root 0 авг 25 16:51 efivars -r–r–r– 1 root root 4096 авг 25 19:05 fw_platform_size -r–r–r– 1 root root 4096 авг 25 19:05 fw_vendor -r–r–r– 1 root root 4096 авг 25 19:05 runtime drwxr-xr-x 32 root root 0 авг 25 19:05 runtime-map -r——– 1 root root 4096 авг 25 19:05 systab drwxr-xr-x 97 root root 0 авг 25 19:05 vars

apt list –installed | grep -i virtualbox

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

ubuntu1.20.04.1 amd64 [установлен] virtualbox-qt/focal-updates,now 6.1.10-dfsg-1

ubuntu1.20.04.1 amd64 [установлен] virtualbox-source/focal-updates,now 6.1.10-dfsg-1

ubuntu1.20.04.1 amd64 [установлен, автоматически] virtualbox/focal-updates,now 6.1.10-dfsg-1

Источник

virtualbox keeps showing error «Kernel driver not installed»

I’m trying to install a Windows7 guest on a Linux host with Virtual box. I’ve set my guest up but when I hit start , I keep getting the message:

I’ve ran /etc/init.d/vboxdrv setup n the shell but nothing happens and the error keeps popping up, how can I get this resolved?
Oh yeah, and I’ve installed dkms already:
# apt-get install dkms

EDIT 1

EDIT 2

There’s virtualbox-guest-dkms and virtualbox-dkms and I have them both installed but I still get the same error.

6 Answers 6

You need to install the VirtualBox kernel modules. I believe the package you need is virtualbox-ose-dkms .

Took me a long time to solve this issue. Had this problem with vBox across 2 distros (Ubuntu and Arch).

I had dkms and all the modules already installed and compiled into my kernel, yet I still got a module related error message when I tried to run a vBox virtual machine.

If your vBox GUI starts without a hitch but get an error telling you to install the VBoxDrv kernel module (or any other modules) when you try to run a virtual machine, your problems are not related to installing the modules into your kernel but activating them in modprobe which the module installation script fails to do.

To load a module manually (such as vboxdrv ), open a terminal prompt and put in:

if your error message is telling you that your missing another module, be sure to activate it as well.

If you Virtual Machine runs after that without giving you an error message, you’ve found the solution. Then you can activate the vboxdrv module permanently by going to /etc/modules-load.d/ (or whatever .d directory your modprobe uses) and making a .conf file within it (such as vbox.conf ). In the .conf file, put in the names of the vbox kernel modules you want to add, such as: vboxdrv and optionally vboxnetadp , vboxnetflt and vboxpci . If you don’t know what they do, see the excerpt below that I took out of vBox’s wiki. Save the .conf file and reboot

From Vbox’s wiki:

vboxnetadp and vboxnetflt are both needed when you intend to use the «Host-only networking» feature. More precisely, vboxnetadp is needed to create the host interface in the VirtualBox global preferences, and vboxnetflt is needed to launch a virtual machine using that network interface.

vboxpci is needed when your virtual machine needs to pass through a PCI device on your host.

Note: If the VirtualBox kernel modules were loaded in the kernel while you updated the modules, you need to reload them manually to use the new updated version. To do it, run vboxreload as root.

Источник

Ticket #11577 (new defect)

Last modified 21 months ago

Secure Boot doesn’t allow ‘vboxdrv’ module to load (now works for Ubuntu and Debian 10+ hosts)

Reported by:	quickbooks	Owned by:
Component:	other	Version:	VirtualBox 4.2.8
Keywords:	Cc:	quickbooks.office@…
Guest type:	all	Host type:	Linux

Description

Host — Fedora 18 64 bit Bios has Secure Boot enabled.

When I try to start any machine it says:

Attachments

Change History

comment:1 Changed 9 years ago by quickbooks

comment:2 Changed 9 years ago by frank

• priority changed from blocker to major

This is not really a VirtualBox bug. Oracle cannot sign kernel modules using the Fedora key. See also the Fedora FAQ in this regards.

comment:3 Changed 6 years ago by marcmerlin

If I build my own kernel with signed modules, I have the key, dkms builds the virtualbox modules on my laptop which has the kernel source and my signing key. Can you enhance the dkms script to use /usr/src/linux-xxx/signing_key.* and sign the modules if those files are present?

comment:4 Changed 6 years ago by bryanhundven

This is still an issue on Fedora 22, I cannot disable secure boot on my workstation. The change marcmerlin suggested would work.

comment:5 Changed 5 years ago by khatkarrohit

Still a major problem on Ubuntu 16.04 using VirtualBox 5.0

comment:6 Changed 5 years ago by Jdot

im having problems too on Ubuntu 16.04 using VirtualBox 5.1.6. when will this be sorted?

comment:7 Changed 3 years ago by equalitytech

Same problem today Ubuntu 17.10.

I can sign the libraries, but still the installer doesn’t work.

./VirtualBox-5.2.13-122773-Linux_amd64.run

tail /var/log/vbox-install.log

comment:8 Changed 3 years ago by DiegoRivera

I applied the following workaround for Ubuntu Bionic (18.04). I’m sure it’ll also work for Artful (17.10) and Zesty (17.04). Possibly even further back in time. This is based on systemd’s RequiredBy capability, shim and mokutils. Please note that you’ll need to have MOK keys already created and enrolled, otherwise there won’t be anything to sign the modules with.

First, create the following systemd unit as /etc/systemd/system/ensure-vboxdrv-signed.service:

The above unit is meant to be executed before vboxdrv.service (i.e. before the VirtualBox startup service is run), and be required by it (i.e. can’t load the service if driver sigining fails).

Then, create the following script and store it as /usr/bin/ensure-vbox-signed:

All that said, grafting a modified version of the above code into the ‘/usr/lib/virtualbox/vboxdrv.sh’ script to be executed during module installation (check to see if signed, if not then sign) and compilation (sign immediately after compiling) would also do the trick.

Another solution could be to port the entire thing to DKMS and leverage the existing infrastructure, but that’s probably far too much work at this point (which is likely why it hasn’t been done).

So, for now, you can use the above workaround. This should work fine in other Linux distributions that also use systemd and mokutil. Please note that the path that the service unit needs to be created in may change for different Linux distributions.

comment:9 Changed 3 years ago by michael

Part of the problem is that any automatic way to sign kernel modules is probably only marginally safer than disabling signing altogether. Of course, it is hard to say for sure, just as it is hard to say for sure how much security benefit signing modules even provides, particularly on a desktop system.

comment:10 Changed 2 years ago by michael

This is fixed for Ubuntu as of the current 6.0 and trunk test builds . The reason it was possible to do it for Ubuntu is that they already provide a mechanism of their own for use with DKMS modules. The problems I mentioned in my last comment still apply, but since Ubuntu has decided to provide this themselves this was their decision not ours.

comment:11 Changed 2 years ago by michael

• Summary changed from Secure Boot doesn’t allow ‘vboxdrv’ module to load — Required key not available to Secure Boot doesn’t allow ‘vboxdrv’ module to load (now works for Ubuntu and Debian 10+ hosts)

Please note that I am not marking this as fixed, just mentioning that the special case of Ubuntu and Debian 10+ hosts now works.

comment:12 Changed 2 years ago by michael

A suggestion for anyone who wants this fixed for other host distributions: ask your distributions to provide a mechanism we can use. If the mechanism is compatible with Ubuntu’s one then it will be automatically supported, as we only check for the mechanism, not the distribution.

comment:13 Changed 2 years ago by michael

If it helps anything, this is the change:

comment:14 Changed 2 years ago by zardoz

Unfortunately, you have completely broken this for Fedora SecureBoot users.

The unconditional «return 0» on line 280 of https://www.virtualbox.org/changeset/79186/vbox means that the modules will not even be compiled. This leaves us Fedora users, who are quite capable of signing kernel modules, with nothing to sign.

It would be far better, if it’s not a Debian/Ubuntu environment, for the code to complete as previously, regardless of the SecureBoot status of the system and a simple, warning to be printed.

I have been manually applying the following patch to vboxdrv.sh to do the post-compile module signing on Fedora 2x & 3x versions. Now, the above changes have crippled any chance of this working.

comment:15 follow-up: ↓ 18 Changed 2 years ago by zardoz

Changing the above patch, for VB 6.0.10, seems to work for Fedora 30 again.

comment:16 Changed 2 years ago by ploni

This has also completely broken this for me (Ubuntu 19.04 with Secure Boot).

didn’t provide any warnings.

sudo /sbin/vboxconfig just gives the standard output:

But my signing script, which uses modinfo -n vboxdrv to find the files to sign, fails with:

After further testing, my problem is the same as #14, except that my computer has the correct files. The problem is that (for whatever reason) it’s not enrolled, cutting me off with the same unconditional «return 0».

comment:17 Changed 2 years ago by michael

@pioni See the patch provided by zardoz above, specifically the commented out «return 0». Make just that change locally.

@zardoz Thank you for pointing out the problem, would you like to be credited in the change log?

comment:18 in reply to: ↑ 15 Changed 2 years ago by CW Huling

This worked for CentOS 7, thank you.

Changing the above patch, for VB 6.0.10, seems to work for Fedora 30 again.

comment:19 Changed 2 years ago by zardoz

@michael — No need to credit me for anything.. Thanks for sorting it out.

comment:20 Changed 2 years ago by beta_tester

Please note that I am not marking this as fixed, just mentioning that the special case of Ubuntu and Debian 10+ hosts now works.

i can not confirm that VirtualBox is working under Debian 10.
see #18770.
i can’t get VirtualBox Version 6.0.10 r132072 (Qt5.11.3) running under
Debian Buster 10 64bit (KDE) + UEFI + SecureBoot.

comment:21 Changed 2 years ago by Haase

Yes. Indeed, I have a some issue with drivers of virtualbox 6.0.10. I solved the updated issue of linux-headers for VBox 6.0.10 but I am problem with drivers. The OS I using is Ubuntu 18.04 Bionic at x64.How must I proceed? The virtualBox open, compile but not running. My hardware architecture is a Intel i5 with UEFI.

WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for current kernel (4.18.0-25-generic) or it failed load. Please recomplile the kernel module install it by

You will not able to start VMs untill this problem fixed.

However, the VBox open but did not running host ISO.Thus, whenever I did type the instruction:

vboxdrv.sh: Stopping VirtualBox services.

vboxdrv.sh: Starting VirtualBox services.

vboxdrv.sh: You must sign these kernel modules before using

VirtualBox: vboxdrv vboxnetflt vboxnetadp vboxpci

See the documentation for your Linux distribution

In the interface of VBox show the other one joint that information — you’re use EFI SECURE BOOT. Yes, indeed, it onboard my architecture. The news architectures are coming with this UEFI secure boot. But I did try off that and the VBox following reporting me about Error: KERNEL DRIVE NOT INSTALLED (rc=1908)

Источник