VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Discussions related to using VirtualBox on Linux hosts.

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby khatkarrohit » 24. Apr 2016, 18:30

I ran
Code: Select all   Expand viewCollapse view
sudo /sbin/rcvboxdrv setup
[sudo] password for My-PC:
Stopping VirtualBox kernel modules ...done.
Removing old VirtualBox pci kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)


Last few lines when I ran dmesg:
Code: Select all   Expand viewCollapse view
[   35.713126] cfg80211: Regulatory domain changed to country: US
[   35.713142] cfg80211:  DFS Master region: FCC
[   35.713145] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   35.713190] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
[   35.713193] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
[   35.713194] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
[   35.713196] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
[   35.713198] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
[   35.713200] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[  398.030365] powercap intel-rapl:0: package locked by BIOS, monitoring only
[  529.716572] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)


Last line is interesting. Do i need to add 32-bit arch support to 64 bit Ubuntu? Newer Linux kernel changed some interface and deprecated maybe.
Last edited by khatkarrohit on 24. Apr 2016, 18:49, edited 1 time in total.
khatkarrohit
 
Posts: 10
Joined: 23. Apr 2016, 21:12

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby khatkarrohit » 24. Apr 2016, 18:39

I even added the 32 bit support.
Code: Select all   Expand viewCollapse view
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get dist-upgrade


Still the same issue.
Code: Select all   Expand viewCollapse view
sudo /sbin/rcvboxdrv setup
Stopping VirtualBox kernel modules ...done.
Removing old VirtualBox pci kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)


dmesg last line says:
Code: Select all   Expand viewCollapse view
[  529.716572] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
khatkarrohit
 
Posts: 10
Joined: 23. Apr 2016, 21:12

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby Perryg » 24. Apr 2016, 18:53

Using 16.04 and the 5.0.18 package from VirtualBox I installed with dpkg -i


Code: Select all   Expand viewCollapse view
ubuntu@ubuntu-16:~/Downloads$ sudo dpkg -i virtualbox-5.0_5.0.18-106667~Ubuntu~xenial_amd64.deb
.
.
.
dpkg: dependency problems prevent configuration of virtualbox-5.0:
 virtualbox-5.0 depends on libsdl1.2debian (>= 1.2.11); however:
  Package libsdl1.2debian is not installed.

Code: Select all   Expand viewCollapse view
sudo apt-get install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libsdl1.2debian
The following NEW packages will be installed:
  libsdl1.2debian
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 168 kB of archives.
After this operation, 483 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
.
.
.
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMS ...done.
Starting VirtualBox kernel modules ...done.




Typing virtualbox in the terminal opens the GUI and seems to work. I would run apt-get install -f and see if it finds missing packages that you missed.
Perryg
Site Moderator
 
Posts: 34372
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby khatkarrohit » 24. Apr 2016, 19:18

I ran the same and I got same error again:
Code: Select all   Expand viewCollapse view
sudo dpkg -i virtualbox-5.0_5.0.18-106667~Ubuntu~xenial_amd64.deb
Selecting previously unselected package virtualbox-5.0.
(Reading database ... 201646 files and directories currently installed.)
Preparing to unpack virtualbox-5.0_5.0.18-106667~Ubuntu~xenial_amd64.deb ...
Unpacking virtualbox-5.0 (5.0.18-106667~Ubuntu~xenial) ...
Setting up virtualbox-5.0 (5.0.18-106667~Ubuntu~xenial) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
Stopping VirtualBox kernel modules ...done.
Removing old VirtualBox pci kernel module ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu4) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160415-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.59ubuntu1) ...


Ran VirtualBox and tried to start a VirtualMachine and got error. Please see attachment.
Screenshot from 2016-04-24 12-23-42.png
Screenshot from 2016-04-24 12-23-42.png (70.32 KiB) Viewed 47213 times

Ran again:
Code: Select all   Expand viewCollapse view
sudo /sbin/rcvboxdrv setup
Stopping VirtualBox kernel modules ...done.
Removing old VirtualBox pci kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
khatkarrohit
 
Posts: 10
Joined: 23. Apr 2016, 21:12

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby hrobache » 24. Apr 2016, 19:23

It's the same for me

I tried a modprobe

Code: Select all   Expand viewCollapse view
# modprobe -v vboxdrv
insmod /lib/modules/4.4.0-21-generic/updates/dkms/vboxdrv.ko
modprobe: ERROR: could not insert 'vboxdrv': Required key not available


Maybe a clue? Is it an apt key?
hrobache
 
Posts: 9
Joined: 23. Apr 2016, 21:22

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby khatkarrohit » 24. Apr 2016, 19:31

I tried one from Ubuntu repositories and its asked me to disable UEFI and choose a password instead. Is this happening because of UEFI boot on host machine.

Code: Select all   Expand viewCollapse view
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 install virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

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


When running:
Code: Select all   Expand viewCollapse view
sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
khatkarrohit
 
Posts: 10
Joined: 23. Apr 2016, 21:12

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby Perryg » 24. Apr 2016, 19:44

Well I don't use UEFI on a Linux so nothing more I can tell you. If I find time I will try and see but as I posted it works for me.
Perryg
Site Moderator
 
Posts: 34372
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby hrobache » 24. Apr 2016, 20:02

My workstation is also UEFI

I saw a post about vboxdrv issue with UEFI
hrobache
 
Posts: 9
Joined: 23. Apr 2016, 21:22

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby hrobache » 24. Apr 2016, 20:49

Well, I eventually managed to modprob vboxdrv. What I have doe is the following
- reboot my system and change the boot mode in order to disable UEFI
- I then have to spécify to boot on the UEFI Ubuntu partition
- I run then "monprobe vboxdrv". No error!
- Vbox can be lauched and the guest machines as well

Unfortunately, once back with UEFI, the issue is bak again!
Last edited by hrobache on 24. Apr 2016, 22:12, edited 1 time in total.
hrobache
 
Posts: 9
Joined: 23. Apr 2016, 21:22

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby Perryg » 24. Apr 2016, 20:53

I do like a challenge so I made time to install with EFI.
Brand new install of 16.04 using EFI and it works as advertised. See information below. If anything it might be the upgrade to 16.04 that is causing an issue.

Code: Select all   Expand viewCollapse view
ubuntu@ubuntu-16:~/$ cat /var/log/syslog | grep efi
Apr 24 13:08:37 ubuntu-16 systemd[1]: Mounting /boot/efi...
Apr 24 13:08:37 ubuntu-16 systemd[1]: Mounted /boot/efi.
Apr 24 13:08:37 ubuntu-16 kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=895688ea-e8cd-4583-acb2-0b8b1dae845e ro quiet splash vt.handoff=7
Apr 24 13:08:37 ubuntu-16 kernel: [    0.000000] efi: EFI v2.40 by EDK II
ubuntu@ubuntu-16:~/$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"

ubuntu@ubuntu-16:~/$


Code: Select all   Expand viewCollapse view
ubuntu@ubuntu-16:~/Downloads$ sudo dpkg -i virtualbox-5.0_5.0.18-106667~Ubuntu~xenial_amd64.deb
[sudo] password for ubuntu:
Selecting previously unselected package virtualbox-5.0.
(Reading database ... 173238 files and directories currently installed.)
Preparing to unpack virtualbox-5.0_5.0.18-106667~Ubuntu~xenial_amd64.deb ...
Unpacking virtualbox-5.0 (5.0.18-106667~Ubuntu~xenial) ...
dpkg: dependency problems prevent configuration of virtualbox-5.0:
 virtualbox-5.0 depends on libqt4-opengl (>= 4:4.7.2); however:
  Package libqt4-opengl is not installed.
 virtualbox-5.0 depends on libsdl1.2debian (>= 1.2.11); however:
  Package libsdl1.2debian is not installed.

dpkg: error processing package virtualbox-5.0 (--install):
 dependency problems - leaving unconfigured
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu4) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160415-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.59ubuntu1) ...
Errors were encountered while processing:
 virtualbox-5.0

ubuntu@ubuntu-16:~/Downloads$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libqt4-opengl libsdl1.2debian
The following NEW packages will be installed:
  libqt4-opengl libsdl1.2debian
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 468 kB of archives.
After this operation, 1,735 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 libqt4-opengl amd64 4:4.8.7+dfsg-5ubuntu2 [301 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 libsdl1.2debian amd64 1.2.15+dfsg1-3 [168 kB]
Fetched 468 kB in 0s (736 kB/s)     
Selecting previously unselected package libqt4-opengl:amd64.
(Reading database ... 174008 files and directories currently installed.)
Preparing to unpack .../libqt4-opengl_4%3a4.8.7+dfsg-5ubuntu2_amd64.deb ...
Unpacking libqt4-opengl:amd64 (4:4.8.7+dfsg-5ubuntu2) ...
Selecting previously unselected package libsdl1.2debian:amd64.
Preparing to unpack .../libsdl1.2debian_1.2.15+dfsg1-3_amd64.deb ...
Unpacking libsdl1.2debian:amd64 (1.2.15+dfsg1-3) ...
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Setting up libqt4-opengl:amd64 (4:4.8.7+dfsg-5ubuntu2) ...
Setting up libsdl1.2debian:amd64 (1.2.15+dfsg1-3) ...
Setting up virtualbox-5.0 (5.0.18-106667~Ubuntu~xenial) ...
Adding group `vboxusers' (GID 129) ...
Done.
Stopping VirtualBox kernel modules ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...done.
Processing triggers for libc-bin (2.23-0ubuntu3) ...

Code: Select all   Expand viewCollapse view
ubuntu@ubuntu-16:~/Downloads$ rcvboxdrv status
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are loaded.
ubuntu@ubuntu-16:~/Downloads$
Perryg
Site Moderator
 
Posts: 34372
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby GMihovics » 25. Apr 2016, 18:41

I ran into this issue today with a co-worker's laptop and the issue was SecureBoot. Seems if SecureBoot in enabled in the machine's BIOS then Ubuntu enforces the signing chain of bootloader, kernel and kernel modules. This, I assume, is what is causing modprobe to fail when installing the virtualbox kernel modules.

Check out the Ubuntu's SecurityTeam SecureBoot page for more information including potential workarounds. I would post the link but I just signed up and can't post links yet. Should be the first result in google for ubuntu SecurityTeam SecureBoot.

We took the easy way out and just disabled SecureBoot and everything works fine now.

Hope that helps.
GMihovics
 
Posts: 1
Joined: 25. Apr 2016, 18:20

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby khatkarrohit » 28. Apr 2016, 18:00

I am thinking to disable secure boot completely. Does secure boot is of any use on a linux machine? No such thing exists that will hurt linux kernel like viruses.
khatkarrohit
 
Posts: 10
Joined: 23. Apr 2016, 21:12

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby khatkarrohit » 28. Apr 2016, 18:42

Actually I solved my issue by going to BIOS settings and completely disabling Secure Boot and enabling the legacy boot option. Ubuntu still boot in the same way. Virtualbox started to work fine now but have to reinstall the Windows 10 VirtualMachine, no issues windows needed to be reinstalled after every few months for better performance. :D

Thanks for your help.
khatkarrohit
 
Posts: 10
Joined: 23. Apr 2016, 21:12

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby Fayce66 » 6. May 2016, 08:37

I had the same problem. After searching for a solution for days, I finally found an easy fix here: "gorka(dot)eguileor(dot)com(slash)vbox-vmware-in-secureboot-linux" (sorry can't fully post the link as I'm a new member)

If you have a Linux system running in Secure Boot and you install VirtualBox or VMware player you will see, with some frustration, that you won’t be able to run any VMs. I haven’t found any post that explains this properly, and most people suggest disabling Secure Boot as a solution and I find that to be a very poor solution, so here’s my 2 cents. Earlier picture shows what you’ll see from the GUI, but if you run it from the console you’ll see:

user@localhost:$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (3.15.8-200.fc20.x86_64) or it failed to
load. Please recompile the kernel module and install it by

sudo /etc/init.d/vboxdrv setup

You will not be able to start VMs until this problem is fixed.


But probably even before that, when you installed VirtualBox you already had an error that you missed:

user@localhost:$ sudo yum localinstall VirtualBox-4.3-4.3.14_95030_fedora18-1.x86_64.rpm

Installing : VirtualBox-4.3-4.3.14_95030_fedora18-1.x86_64 1/1

Creating group 'vboxusers'. VM users must be member of that group!

No precompiled module for this kernel found -- trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.

Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMS [ OK ]
Starting VirtualBox kernel modules [FAILED]
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Verifying : VirtualBox-4.3-4.3.14_95030_fedora18-1.x86_64 1/1

Installed:
VirtualBox-4.3.x86_64 0:4.3.14_95030_fedora18-1


You’ll realize that dmesg will not tell you much so you’ll probably check the vboxdrv service:

user@localhost:$ sudo systemctl status vboxdrv
vboxdrv.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/rc.d/init.d/vboxdrv)
Active: inactive (dead)


And see there’s not much info here either, so maybe you’ll try to load the module yourself to see what the problem is:

user@localhost:$ sudo modprobe -v vboxdrv
insmod /lib/modules/3.15.8-200.fc20.x86_64/extra/vboxdrv.ko
modprobe: ERROR: could not insert 'vboxdrv': Required key not available


And then you’ll realize what the problem is, modprobe is complaining about required key not being available. Which actually means that the module is not signed and therefore cannot be loaded.

Now that you know what the problem is, the solution is quite simple; you just need to sign the module and make sure that the system recognizes the key as valid. If you already have a X.509 key you can skip the key creation part and go directly to signing the module and enrolling the key But if you don’t, you’ll need to generate a key to sign any third party module you want to install or any custom module you use.

Creating an X.509 Key Pair to sign the driver is easy:

user@localhost:$ openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=Akrog/"

In the above command, replace MOK with the name of the file you want for the key and Akrog with the Common Name you want to use. It’s usually the organization that signs it.

Now you just need to sign the driver, but where’s the driver located?

user@localhost:$ modinfo vboxdrv
filename: /lib/modules/3.15.8-200.fc20.x86_64/extra/vboxdrv.ko
version: 4.3.14 (0x001a0007)
license: GPL
description: Oracle VM VirtualBox Support Driver
author: Oracle Corporation
srcversion: 6284D16B33B2564B26EFAB2
depends:
vermagic: 3.15.8-200.fc20.x86_64 SMP mod_unload
parm: force_async_tsc:force the asynchronous TSC mode (int)


Now we’ll proceed to sign the module using modinfo to locate the driver:

user@localhost:$ sudo /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vboxdrv)

user@localhost:$ modinfo vboxdrv
filename: /lib/modules/3.15.8-200.fc20.x86_64/extra/vboxdrv.ko
version: 4.3.14 (0x001a0007)
license: GPL
description: Oracle VM VirtualBox Support Driver
author: Oracle Corporation
srcversion: 6284D16B33B2564B26EFAB2
depends:
vermagic: 3.15.8-200.fc20.x86_64 SMP mod_unload
signer: Akrog
sig_key: D5:D3:E2:00:89:07:A7:CE:BC:89:14:78:0B:D2:9B:03:FE:CC:21:4B
sig_hashalgo: sha256
parm: force_async_tsc:force the asynchronous TSC mode (int)


PS: on ubuntu 16 you have to use:
sudo /usr/src/linux-headers-4.4.0-21-generic/scripts/sign-file sha256 ./MOK.priv ./MOK.der /lib/modules/4.4.0-21-generic/updates/dkms/vboxdrv.ko


We have confirmed that the module has been signed.

To enroll the public key in the MOK (Module owned Key) your UEFI partition must have MokManager.efi installed.

Now we have to manually add the public key to shim’s MOK list:

user@localhost:$ sudo mokutil --import MOK.der

Now you just need to reboot and follow the screen menus that will appear during the UEFI boot to enroll the new key (on ubuntu 16 it's automatic it seems).
This is a persistent operation, so you’ll only need to do this once.

When you have finished booting you can check that the key is in the system:

user@localhost:$ sudo keyctl list %:.system_keyring

112560593: ---lswrv 0 0 asymmetric: Fedora kernel signing key: e948c9015e04bd4cd5879fe2f9230a1d70859c7d
489921950: ---lswrv 0 0 asymmetric: Fedora Secure Boot CA: fde32599c2d61db1bf5807335d7b20e4cd963b42
98641885: ---lswrv 0 0 asymmetric: Akrog: d5d3e2008907a7cebc8914780bd29b03fecc214b
525156767: ---lswrv 0 0 asymmetric: Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4
1001714488: ---lswrv 0 0 asymmetric: Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53

And that it was EFI who loaded it:

user@localhost:$ dmesg | grep Loaded
[ 0.456158] EFI: Loaded cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' linked to '.system_keyring'
[ 0.456194] EFI: Loaded cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' linked to '.system_keyring'
[ 0.457111] EFI: Loaded cert 'Akrog: d5d3e2008907a7cebc8914780bd29b03fecc214b' linked to '.system_keyring'
[ 0.457768] EFI: Loaded cert 'Fedora Secure Boot CA: fde32599c2d61db1bf5807335d7b20e4cd963b42' linked to '.system_keyring'


Now vboxdrv should be loaded and ready to run your VMs.
Fayce66
 
Posts: 1
Joined: 6. May 2016, 08:13

Re: VirtualBox on Ubuntu 16.04 fails to load VirtualBox Kernel Modules

Postby khatkarrohit » 11. May 2016, 10:46

Thanks Fayce66 for a perfect solution.
khatkarrohit
 
Posts: 10
Joined: 23. Apr 2016, 21:12

PreviousNext

Return to VirtualBox on Linux Hosts

Who is online

Users browsing this forum: No registered users and 19 guests