3

Why the modprobe vboxdrv is not resolved yet for Kernel 4.8?

I have 2 kernels 4.4 and 4.8 and vboxdrv is working fine on 4.4 but whenever i try to launch my vm i get a fatal error with modprobe vboxdrv.

Should I wait for a Virtualbox update is it can be fixed somehow for the newest Kernel?

EDIT: this is my uname-a output

Linux mohsen-SVP1322F4E 4.8.1-040801-generic #201610071031 SMP Fri Oct 7 14:34:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

EDIT2: Updated to kernel 4.8.4 and then removed the virtualbox dkms then reinstall it again. Still the error is found. Vboxdrv is still not found.

EDIT3: Tried to reinstall the virtualbox dkms with no luck. Then removed and reinstalled Virtualbox as per here and everything is working fine now.

Leb_Broth
  • 133
  • 4

1 Answers1

1

With Oracle's Virtual Box 5.1 the DKMS (Dynamic Kernel Management System) is no longer used to download source code and compile it for every Kernel Upgrade.

Go to Install latest VirtualBox 5.1 Ubuntu 16.04 for instructions on:

  • removing old version
  • adding VirtualBox to sources.list (informs Ubuntu where to find it)
  • adding VirtualBox signature key to library
  • installing current version of VirtualBox

Also instead of Kernel version 4.8.1 which has the "Dirty COW" security holes (What is dirty COW bug?), you should use the most recent kernel version 4.8.4 (as of October 27, 2016) which has the bug fix.

Community
  • 1
WinEunuuchs2Unix
  • 102,282