VirtualBox had been working with Ubuntu 16.04 without any problem. I apply updates as Canonical releases them. Today I got this:
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.
I tried removing and reinstalling VirtualBox to no effect. The log is enclosed.
You are using the Ubuntu fork. You'll either need to ask them about that, or uninstall completely their VBox version and install the official one from https://www.virtualbox.org/wiki/Downloads
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
$ uname -a
Linux maya 4.2.0-35-generic #40-Ubuntu SMP Tue Mar 15 22:15:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ sudo apt remove virtualbox
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
virtualbox virtualbox-qt
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 89.3 MB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 259770 files and directories currently installed.)
Removing virtualbox-qt (5.0.18-dfsg-2ubuntu1) ...
Removing virtualbox (5.0.18-dfsg-2ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
Processing triggers for mime-support (3.59ubuntu1) ...
$ wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
OK
$ wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
OK
$ sudo vi /etc/apt/sources.list
$ sudo apt-get update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://dl.google.com/linux/chrome/deb stable Release
Get:3 http://download.virtualbox.org/virtualbox/debian xenial InRelease [7,894 B]
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [95.7 kB]
Get:8 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Ign:9 http://www.openprinting.org/download/printdriver/debian lsb3.2 InRelease
Hit:10 http://ppa.launchpad.net/aacebedo/fasd/ubuntu xenial InRelease
Hit:11 http://archive.canonical.com/ubuntu wily InRelease
Ign:13 http://download.opensuse.org/repositories/home:/olav-st/xUbuntu_15.10 InRelease
Hit:14 http://www.openprinting.org/download/printdriver/debian lsb3.2 Release
Ign:15 https://dl.bintray.com/sbt/debian InRelease
Get:16 https://dl.bintray.com/sbt/debian Release [814 B]
Hit:16 https://dl.bintray.com/sbt/debian Release
Ign:17 http://ppa.launchpad.net/apachelogger/s3fs-fuse/ubuntu trusty InRelease
Hit:18 http://download.opensuse.org/repositories/home:/olav-st/xUbuntu_15.10 Release
Hit:19 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Get:20 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64 Packages [1,466 B]
Ign:6 http://toolbelt.heroku.com/ubuntu ./ InRelease
Hit:21 http://ppa.launchpad.net/audio-recorder/ppa/ubuntu xenial InRelease
Hit:24 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu xenial InRelease
Get:25 http://download.virtualbox.org/virtualbox/debian xenial/contrib i386 Packages [1,467 B]
Hit:12 http://screenshots.getdeb.net xenial-getdeb InRelease
Hit:26 http://ppa.launchpad.net/fingerprint/fingerprint-gui/ubuntu xenial InRelease
Get:27 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [259 kB]
Hit:22 http://toolbelt.heroku.com/ubuntu ./ Release
Hit:30 http://ppa.launchpad.net/libreoffice/libreoffice-5-1/ubuntu xenial InRelease
Hit:31 http://ppa.launchpad.net/maarten-baert/simplescreenrecorder/ubuntu xenial InRelease
Get:32 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [256 kB]
Get:33 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [172 kB]
Get:34 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [169 kB]
Hit:35 http://ppa.launchpad.net/qos/pulseaudio-dlna/ubuntu xenial InRelease
Hit:36 http://ppa.launchpad.net/qos/pulseaudio-dlna/ubuntu wily InRelease
Hit:38 http://ppa.launchpad.net/simon-cadman/niftyrepo/ubuntu wily InRelease
Hit:39 http://ppa.launchpad.net/ubuntu-desktop/ubuntu-make/ubuntu xenial InRelease
Hit:40 http://ppa.launchpad.net/webupd8team/java/ubuntu xenial InRelease
Hit:41 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu xenial InRelease
Hit:42 http://ppa.launchpad.net/yubico/stable/ubuntu xenial InRelease
Hit:43 http://ppa.launchpad.net/apachelogger/s3fs-fuse/ubuntu trusty Release
Fetched 1,057 kB in 3s (330 kB/s)
Reading package lists... Done
W: http://www.openprinting.org/download/printdriver/debian/dists/lsb3.2/Release.gpg: Signature by key F8897B6F00075648E248B7EC24CBF5474CFD1E2F uses weak digest algorithm (SHA1)
W: http://ppa.launchpad.net/apachelogger/s3fs-fuse/ubuntu/dists/trusty/Release.gpg: Signature by key AEFEA337B2F7FE9222289A46ADAA0E064427DF3B uses weak digest algorithm (SHA1)
$ sudo apt-get install virtualbox-5.1 dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
dkms is already the newest version (2.2.0.3-2ubuntu11).
dkms set to manually installed.
The following packages were automatically installed and are no longer required:
kbuild libgsoap8 libvncserver1 module-assistant virtualbox-source
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
libsdl-ttf2.0-0 virtualbox-5.1
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 62.8 MB of archives.
After this operation, 154 MB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 libsdl-ttf2.0-0 amd64 2.0.11-3 [15.0 kB]
Get:2 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64 virtualbox-5.1 amd64 5.1.0-108711~Ubuntu~xenial [62.8 MB]
Fetched 62.8 MB in 28s (2,171 kB/s)
Preconfiguring packages ...
Selecting previously unselected package libsdl-ttf2.0-0:amd64.
(Reading database ... 259474 files and directories currently installed.)
Preparing to unpack .../libsdl-ttf2.0-0_2.0.11-3_amd64.deb ...
Unpacking libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Selecting previously unselected package virtualbox-5.1.
Preparing to unpack .../virtualbox-5.1_5.1.0-108711~Ubuntu~xenial_amd64.deb ...
Unpacking virtualbox-5.1 (5.1.0-108711~Ubuntu~xenial) ...
Processing triggers for systemd (229-4ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Setting up libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Setting up virtualbox-5.1 (5.1.0-108711~Ubuntu~xenial) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
apt-get install linux-headers-4.2.0-35-generic
(The last command may fail if your system is not fully updated.)
apt-get install linux-headers-generic
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
Processing triggers for libc-bin (2.23-0ubuntu3) ...
$ sudo apt-get install linux-headers-4.2.0-35-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers-4.2.0-35-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'linux-headers-4.2.0-35-generic' has no installation candidate
$ sudo apt-get install linux-headers-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-generic is already the newest version (4.4.0.28.30).
linux-headers-generic set to manually installed.
The following packages were automatically installed and are no longer required:
kbuild libgsoap8 libvncserver1 module-assistant virtualbox-source
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
$ sudo /sbin/vboxconfig
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
apt-get install linux-headers-4.2.0-35-generic
(The last command may fail if your system is not fully updated.)
apt-get install linux-headers-generic
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
apt-get install linux-headers-4.2.0-35-generic
(The last command may fail if your system is not fully updated.)
apt-get install linux-headers-generic
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
Last edited by mslinn on 14. Jul 2016, 15:41, edited 1 time in total.
mslinn wrote:I cannot post the transcript because it has URLs in it. I tried mangling the URLs but the URL detection code seems to consider almost anything as a URL
????????????????????
You couldn't post the transcript because it had a URL in it, yet you posted a URL directly??? Does not compute! Anyway for those that do not feel like going to 3rd party sites, here's what you tried to post:
$ sudo apt remove virtualbox
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
virtualbox virtualbox-qt
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 89.3 MB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 259770 files and directories currently installed.)
Removing virtualbox-qt (5.0.18-dfsg-2ubuntu1) ...
Removing virtualbox (5.0.18-dfsg-2ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
Processing triggers for mime-support (3.59ubuntu1) ...
$ wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
OK
$ wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
OK
$ sudo vi /etc/apt/sources.list
$ sudo apt-get update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://dl.google.com/linux/chrome/deb stable Release
Get:3 http://download.virtualbox.org/virtualbox/debian xenial InRelease [7,894 B]
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [95.7 kB]
Get:8 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Ign:9 http://www.openprinting.org/download/printdriver/debian lsb3.2 InRelease
Hit:10 http://ppa.launchpad.net/aacebedo/fasd/ubuntu xenial InRelease
Hit:11 http://archive.canonical.com/ubuntu wily InRelease
Ign:13 http://download.opensuse.org/repositories/home:/olav-st/xUbuntu_15.10 InRelease
Hit:14 http://www.openprinting.org/download/printdriver/debian lsb3.2 Release
Ign:15 https://dl.bintray.com/sbt/debian InRelease
Get:16 https://dl.bintray.com/sbt/debian Release [814 B]
Hit:16 https://dl.bintray.com/sbt/debian Release
Ign:17 http://ppa.launchpad.net/apachelogger/s3fs-fuse/ubuntu trusty InRelease
Hit:18 http://download.opensuse.org/repositories/home:/olav-st/xUbuntu_15.10 Release
Hit:19 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Get:20 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64 Packages [1,466 B]
Ign:6 http://toolbelt.heroku.com/ubuntu ./ InRelease
Hit:21 http://ppa.launchpad.net/audio-recorder/ppa/ubuntu xenial InRelease
Hit:24 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu xenial InRelease
Get:25 http://download.virtualbox.org/virtualbox/debian xenial/contrib i386 Packages [1,467 B]
Hit:12 http://screenshots.getdeb.net xenial-getdeb InRelease
Hit:26 http://ppa.launchpad.net/fingerprint/fingerprint-gui/ubuntu xenial InRelease
Get:27 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [259 kB]
Hit:22 http://toolbelt.heroku.com/ubuntu ./ Release
Hit:30 http://ppa.launchpad.net/libreoffice/libreoffice-5-1/ubuntu xenial InRelease
Hit:31 http://ppa.launchpad.net/maarten-baert/simplescreenrecorder/ubuntu xenial InRelease
Get:32 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [256 kB]
Get:33 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [172 kB]
Get:34 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [169 kB]
Hit:35 http://ppa.launchpad.net/qos/pulseaudio-dlna/ubuntu xenial InRelease
Hit:36 http://ppa.launchpad.net/qos/pulseaudio-dlna/ubuntu wily InRelease
Hit:38 http://ppa.launchpad.net/simon-cadman/niftyrepo/ubuntu wily InRelease
Hit:39 http://ppa.launchpad.net/ubuntu-desktop/ubuntu-make/ubuntu xenial InRelease
Hit:40 http://ppa.launchpad.net/webupd8team/java/ubuntu xenial InRelease
Hit:41 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu xenial InRelease
Hit:42 http://ppa.launchpad.net/yubico/stable/ubuntu xenial InRelease
Hit:43 http://ppa.launchpad.net/apachelogger/s3fs-fuse/ubuntu trusty Release
Fetched 1,057 kB in 3s (330 kB/s)
Reading package lists... Done
W: http://www.openprinting.org/download/printdriver/debian/dists/lsb3.2/Release.gpg: Signature by key F8897B6F00075648E248B7EC24CBF5474CFD1E2F uses weak digest algorithm (SHA1)
W: http://ppa.launchpad.net/apachelogger/s3fs-fuse/ubuntu/dists/trusty/Release.gpg: Signature by key AEFEA337B2F7FE9222289A46ADAA0E064427DF3B uses weak digest algorithm (SHA1)
$ sudo apt-get install virtualbox-5.1 dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
dkms is already the newest version (2.2.0.3-2ubuntu11).
dkms set to manually installed.
The following packages were automatically installed and are no longer required:
kbuild libgsoap8 libvncserver1 module-assistant virtualbox-source
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
libsdl-ttf2.0-0 virtualbox-5.1
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 62.8 MB of archives.
After this operation, 154 MB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 libsdl-ttf2.0-0 amd64 2.0.11-3 [15.0 kB]
Get:2 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64 virtualbox-5.1 amd64 5.1.0-108711~Ubuntu~xenial [62.8 MB]
Fetched 62.8 MB in 28s (2,171 kB/s)
Preconfiguring packages ...
Selecting previously unselected package libsdl-ttf2.0-0:amd64.
(Reading database ... 259474 files and directories currently installed.)
Preparing to unpack .../libsdl-ttf2.0-0_2.0.11-3_amd64.deb ...
Unpacking libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Selecting previously unselected package virtualbox-5.1.
Preparing to unpack .../virtualbox-5.1_5.1.0-108711~Ubuntu~xenial_amd64.deb ...
Unpacking virtualbox-5.1 (5.1.0-108711~Ubuntu~xenial) ...
Processing triggers for systemd (229-4ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Setting up libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Setting up virtualbox-5.1 (5.1.0-108711~Ubuntu~xenial) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
apt-get install linux-headers-4.2.0-35-generic
(The last command may fail if your system is not fully updated.)
apt-get install linux-headers-generic
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
Processing triggers for libc-bin (2.23-0ubuntu3) ...
$ sudo apt-get install linux-headers-4.2.0-35-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers-4.2.0-35-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'linux-headers-4.2.0-35-generic' has no installation candidate
$ sudo apt-get install linux-headers-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-generic is already the newest version (4.4.0.28.30).
linux-headers-generic set to manually installed.
The following packages were automatically installed and are no longer required:
kbuild libgsoap8 libvncserver1 module-assistant virtualbox-source
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
$ sudo /sbin/vboxconfig
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
apt-get install linux-headers-4.2.0-35-generic
(The last command may fail if your system is not fully updated.)
apt-get install linux-headers-generic
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
apt-get install linux-headers-4.2.0-35-generic
(The last command may fail if your system is not fully updated.)
apt-get install linux-headers-generic
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
$ uname -a
Linux maya 4.2.0-35-generic #40-Ubuntu SMP Tue Mar 15 22:15:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
It looks to me like you OS is out of sync in apt. One install attempt tries to install headers that are missing and another tries to install one that is already installed but not the one that you are using. I would clean apt and then run an apt-get update && apt-get dist-upgrade to get this mess cleaned up. Then try again.
Note: it would probably help you in the future to remove old kernels and headers that you no longer need.
Note2: It also might be easier for you to use the wild-card to make sure you are always installing the proper headers -$(uname -r)
$ sudo /sbin/vboxconfig
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
apt-get install linux-headers-4.2.0-35-generic
(The last command may fail if your system is not fully updated.)
apt-get install linux-headers-generic
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
apt-get install linux-headers-4.2.0-35-generic
(The last command may fail if your system is not fully updated.)
apt-get install linux-headers-generic
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
$ sudo apt-get install linux-headers-4.2.0-35-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers-4.2.0-35-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'linux-headers-4.2.0-35-generic' has no installation candidate
On Ubuntu hosts it is real easy to address this. After kernel upgrade if you get the DBus message kernel module not found blah (not the exact message but you know what it means). All you have to do is issue a one-liner:
sudo dpkg-reconfigure virtualbox-5.1
Once you do you will get the setup message informing you it needs to create a system users group. Just hit enter. It will then drop back to the terminal and you will see the text line that reads System Group already exists skipping... With a blank line below that. The rebuild of the modules is hidden behind this blank line. Wait for an interactive prompt to return and you should be good to go.
If Using any other Linux Host OS or if you just like to see more info on screen you can also just use the following:
This works the same as the older /etc/init.d/vboxdrv setup they have just changed the name in newer versions.
As of 5.1 Virtualbox has done away with virtualbox-dkms so even if it allows you to install it (if you have 5.1 usually it tells you it will not) it will have no affect on 5.1. I read that and saw it in an article on Softpedia, but I can not post it here as I am new and there are odd forum rules.
I always find it amusing how a simple problem gets such a convoluted and detailed solution provided when in the end it was something much more simple to begin with. These are the same techs that go replacing computer towers they think are dead without checking to see if the electrical plug is loose and just needs to be re-inserted . Instead of working a problem from the top down I try the bottom up as 95% of everything I fix is usually just something very simple that goes missed.
Last edited by Pariah on 29. Jun 2017, 16:03, edited 1 time in total.
I don't believe VirtualBox has a module called "virtualbox-dkms". Repo forks do but not the official version from VirtualBox.org. Host systems ( most ) still have the original dkms available for install that will keep the external modules updated when a new kernel is installed but you must install it manually.
They did in versions BEFORE 5.1. as of version 5.1 Oracle states they found some other way to keep the kernel modules up-to-date (obviously not fully working as we would not be having this missing modules on upgrades thread).
The difference between dkms and virtualbox-dkms is DKMS is the system framework that is made available system wide to update kernel mods on upgrade. While the Virtualbox-DKMS provided the VIRTUALBOX files DKMS needs to build those virtualbox kernel modules [again PRE 5.1].
I hope that helps clear things up.
I still can not post links, but if you use Google and search: virtualbox no longer needs virtualbox-dkms
The second link down is titled: VirtualBox 5.1 Will No Longer Rely on DKMS for Kernel Module and is the article I was referring to above.
Yes I know the difference and if you want the kernel modules to update when you change the kernel you need dkms, not virtualbox-dkms. IIRC the virtualbox-dkms was for the guest and not the host, which is what the topic is about. dkms still does what it is intended to do and that is to keep the headers updated when you install a new kernel, and recompile the external modules when the update occurs.
. Instead of working a problem from the top down I try the bottom up as 95% of everything I fix is usually just something very simple that goes missed.