Page 1 of 1

vbox kernel module installtion failed with wrong message

Posted: 18. Jan 2021, 14:21
by MrSunilJ
I am installing virtualbox 6.1 on ubuntu 14.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may 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
But the secure boot is disabled on the system and I have checked it in BIO's settings and using below command.

Code: Select all

mokutil --sb-state
SecureBoot disabled
I believe the new/updated vbox script is not doing validation properly and giving wrong message.
Thanks in advance.

Re: vbox kernel module installtion failed with wrong message

Posted: 18. Jan 2021, 14:38
by fth0
MrSunilJ wrote:I believe the new/updated vbox script is not doing validation properly and giving wrong message.
Why do you think so? The script output names 4 different steps for you to take, and you'd only reach the 3rd step (Secure Boot), if taking the two steps before didn't solve the problem.

Re: vbox kernel module installtion failed with wrong message

Posted: 19. Jan 2021, 06:04
by MrSunilJ
Thanks @fth0. Below are the dmesg logs
capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[13093.954565] perf interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[14077.778965] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[14077.781386] vboxdrv: Found 4 processor cores
[14077.798300] vboxdrv: TSC mode is Invariant, tentative frequency 3192632534 Hz
[14077.798301] vboxdrv: Successfully loaded version 6.1.16 (interface 0x00300000)
[14078.038820] VBoxNetFlt: Successfully started.
[14078.039585] VBoxNetAdp: Successfully started.

error warning: `VirtualBox' uses 32-bit capabilities (legacy support in use) is warning. So I think it will not impact much. and the other important error "vboxdrv: module verification failed: signature and/or required key missing - tainting kernel" again pointing to the same point that secure boot is enable on the system.