After partial update, vbox now says "kernel driver not installed" running VMs
Posted: 1. May 2016, 17:58
I've been running VMs on my CentOS laptop with VirtualBox for quite a while. I had version 5.x installed, which was working. I saw a yum update come through a few days ago, but it seems like it didn't work. I think the last time a yum update for it came through, I had to do something manually to get it working, but I don't remember what that was.
When I run any of my VMs now, I get the following:
I tried running that suggested command line, but there is no "rcvboxdrv" in "/sbin".
It may be completely unrelated, but my yum database is also confused. Although the current output from "yum update" doesn't include any mention of virtualbox, but as I mentioned earlier, I saw the update come through a few days ago, and I remember the last time virtualbox updated with yum, it didn't update correctly. In any case, here's the current output from yum:
When I run any of my VMs now, I get the following:
Code: Select all
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 reinstall the kernel module by executing
'/sbin/rcvboxdrv setup'
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. It may be completely unrelated, but my yum database is also confused. Although the current output from "yum update" doesn't include any mention of virtualbox, but as I mentioned earlier, I saw the update come through a few days ago, and I remember the last time virtualbox updated with yum, it didn't update correctly. In any case, here's the current output from yum:
Code: Select all
Loaded plugins: fastestmirror, langpacks, verify
adobe-linux-x86_64 | 951 B 00:00
base | 3.6 kB 00:00
epel/x86_64/metalink | 12 kB 00:00
epel | 4.3 kB 00:00
extras | 3.4 kB 00:00
google-chrome | 951 B 00:00
google-musicmanager | 951 B 00:00
google-talkplugin | 951 B 00:00
nux-dextop | 2.9 kB 00:00
rpmfusion-free-updates | 2.7 kB 00:00
updates | 3.4 kB 00:00
virtualbox | 951 B 00:00
(1/2): epel/x86_64/updateinfo | 544 kB 00:00
(2/2): epel/x86_64/primary_db | 4.1 MB 00:01
Loading mirror speeds from cached hostfile
* base: centos.eecs.wsu.edu
* epel: fedora-epel.mirror.lstn.net
* extras: repo1.dal.innoscale.net
* nux-dextop: mirror.li.nux.ro
* rpmfusion-free-updates: mirror.us.leaseweb.net
* updates: centos.mirrors.tds.net
Resolving Dependencies
--> Running transaction check
---> Package nss-softokn-freebl.i686 0:3.16.2.3-13.el7_1 will be updated
---> Package nss-softokn-freebl.i686 0:3.16.2.3-14.2.el7_2 will be an update
---> Package python-ecdsa.noarch 0:0.11-3.el7.centos will be obsoleted
---> Package python2-ecdsa.noarch 0:0.13-4.el7 will be obsoleting
---> Package tzdata.noarch 0:2016c-1.el7 will be updated
---> Package tzdata.noarch 0:2016d-1.el7 will be an update
---> Package tzdata-java.noarch 0:2016c-1.el7 will be updated
---> Package tzdata-java.noarch 0:2016d-1.el7 will be an update
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for nss-softokn-freebl which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of nss-softokn-freebl of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude nss-softokn-freebl.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of nss-softokn-freebl installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of nss-softokn-freebl installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: nss-softokn-freebl-3.16.2.3-14.2.el7_2.i686 != nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64