After each upgrade: modprobe vboxdrv failed

[AJN]

Starting from v5.0, I constantly have this annoying issue each time VirtualBox is upgraded

sudo /sbin/vboxconfig

Code: Select all

 Adding system startup for /etc/init.d/vboxdrv ...
   /etc/rc0.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc1.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc6.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc2.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc3.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc4.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc5.d/S20vboxdrv -> ../init.d/vboxdrv
 Adding system startup for /etc/init.d/vboxballoonctrl-service ...
   /etc/rc0.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc1.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc6.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc2.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc3.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc4.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc5.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
 Adding system startup for /etc/init.d/vboxautostart-service ...
   /etc/rc0.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc1.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc6.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc2.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc3.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc4.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc5.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
 Adding system startup for /etc/init.d/vboxweb-service ...
   /etc/rc0.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc1.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc6.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc2.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc3.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc4.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc5.d/S35vboxweb-service -> ../init.d/vboxweb-service
Starting VirtualBox kernel modules ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Starting VirtualBox web service ...fail!

dmesg

Code: Select all

[ 2852.791160] vboxdrv: module verification failed: signature and/or  required key missing - tainting kernel
[ 2852.798020] vboxdrv: Found 4 processor cores
[ 2852.798322] vboxdrv: fAsync=0 offMin=0x302 offMax=0x115d
[ 2852.898512] vboxdrv: TSC mode is Synchronous, tentative frequency 2327827604 Hz
[ 2852.898516] vboxdrv: Successfully loaded version 5.0.10 (interface 0x00240000)
[ 2853.104323] VBoxNetFlt: Successfully started.
[ 2853.107154] VBoxNetAdp: Successfully started.
[ 2853.109711] VBoxPciLinuxInit
[ 2853.113200] vboxpci: IOMMU not found (not registered)
[ 2889.201193] VBoxPciLinuxLinuxUnload

[Perryg]

Minimal information needed to be able to help

[AJN]

inf.
- Version 5.0.10 r104061 + Guest Additions installed in the guest
- All guests are 32-bits
- Host Information:

Code: Select all

Linux gns3-iouvm 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Host time: 2015-11-22T03:55:24.988000000Z
Processor online count: 4
Processor count: 4
Processor online core count: 4
Processor core count: 4
Processor#0 speed: 2336 MHz
Processor#0 description: Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
Processor#1 speed: 2336 MHz
Processor#1 description: Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
Processor#2 speed: 2336 MHz
Processor#2 description: Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
Processor#3 speed: 2336 MHz
Processor#3 description: Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz
Memory size: 7984 MByte
Memory available: 4914 MByte
Operating system: Linux
Operating system version: 3.13.0-68-generic

This issue concerns all hosts, I get the message when I start virtualbox

sudo virtualbox &

Code: Select all

[3] 19688
ajn:~$ WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (3.13.0-68-generic) or it failed to
         load. Please recompile the kernel module and install it by

           sudo /sbin/vboxconfig

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

[Perryg]

Did you remove the previous version before you installed the 5.* version?

Also keep in mind that adding gns3, docker, & vagrant makes it all but impossible to support your VirtualBox install.

[AJN]

Hi Perryg,
Thanks for your reply, I indeed completely uninstalled VirtualBox versions, I found both v4.x and v5 which didn't uninstall via apt-get, I had to do it from Synaptic.
Reinstalled and installations gone smooth!

I am wondering about these messages:

Code: Select all

00:00:00.109915 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br105: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.112409 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br115: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.117697 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br0: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.120373 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br102: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.122779 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br112: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.125325 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br107: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.127600 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br104: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.129847 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br114: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.132345 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br109: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.134790 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br101: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.137052 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br111: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.139885 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br106: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.142170 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br116: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.144560 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for lxcbr0: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.156386 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br103: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.158819 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br113: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.161794 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br108: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.164418 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for br110: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.167444 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for docker0: VBoxNetAdpCtl: ioctl failed: Operation not supported

The interface in question are simple bridge interfaces created/used by Docker, done using usual commands such:

Code: Select all

ip link .. type bridge
brctl

What is the implications of this failure to read link speed? Doesn it makes the link unusable by Virtualbox?[/b]

[Perryg]

I have no idea as I said it makes it impossible to diagnose or help with all the third party applications you are using.

I can tell you that VirtualBox does not use the configuration you are running. If you want to run VirtualBox native as it was intended to run then we can help.