Virtual Box problems. Leap 42.2

I have tried both the openSuse leap and Oracle versions, but get the following error message when I try to run an Virtualbox session.

"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"

However running this as "sudo /sbin/rcvboxdrv setup does not do anything. Can anyone help me to get VB running. I seem to recall reading somewhere that there are problems running VB with Leap 42.2

If you run the Oracle Version, only that Version should be installed, no other package with virtualbox or vbox in the Name…

Than the command will work (if you have installed kernel-default-devel, mak and gcc).

If you installed the openSUSE Version, the host-kmp must match to your running Kernel Version…

But I think, this belongs to the Virtualization Subforum.

no problems with virtual box on my computer…
just install from the official opensuse repos then add current user to group vbox users then install dkms - Dynamic Kernel Module Support Framework
restart computer and it should work fine

just install from the official opensuse repos then add current user to group vbox users then install dkms

dkms is not necessary, you can use it, if you install the Version from the Oracle Side/Repo.
openSUSE has the kernel-Modules inside the Repo.

i know that kernel-Modules is in the official opensuse repo, so what do you mean

then install dkms

dkms is not necessary when you install the Virtualbox from the openSUSE Repo.

Thanks this works.Vbox now up and ;)working.

And in addition to that, dkms is also not of any help for the packages from Oracle.

Running


rpm -qlv VirtualBox-5.1 |grep dkms

gives no output as (since 5.0 or 5.1) the packages from Oracle do not ship a dkms.conf file, and as long as you don’t write one yourself (which is not that hard), dkms is useless even for those packages.

(Although I don’t know if there might be a dkms.conf inside the distor independent tar balls provided by Oracle, but who would use them on a RPM-based distro anyway.)

AK

are you sure it works without dkms ??
did you install and use it yourself on leap42.2 system ??

if yes then what is the correct way to install VirtualBox?
just install it and all its dependencies restart the computer and it should work?? what am i missing because each time i install vb it doesn’t work without dkms??

Virtualbox from Oracle is working here without dkms:

zypper se -si dkms vbox virtualbox
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S | Name           | Typ   | Version                     | Arch   | Repository
--+----------------+-------+-----------------------------+--------+-----------
i | VirtualBox-5.1 | Paket | 5.1.18_114002_openSUSE132-1 | x86_64 | Virtualbox

Important:
No virtualbox Package from opensuse should be installed.
And adding the User to the vboxusers Group

groups
users cdrom vboxusers davfs2

The virtualbox from Oracle is also working with Kernel 4.10

uname -a
Linux linux64 4.10.8-2.gea9dcd4-default #1 SMP PREEMPT Fri Mar 31 17:16:00 UTC 2017 (ea9dcd4) x86_64 x86_64 x86_64 GNU/Linux

Every Kernel Update you have to build the Virtualbox Modules new, I have build a Script to run this easily by typeing vboxsetup as root.
Its a Minute to wait and Virtualbox is working…

if yes then what is the correct way to install VirtualBox?

Add the Oracle Repo.

zypper ar -f http://download.virtualbox.org/virtualbox/rpm/opensuse/42.1/ Virtualbox

Thats also the Repo for 42.2…
Install Virtualbox:

zypper in VirtualBox-5.1

The “magic” seems to be inside


/usr/lib/virtualbox/vboxdrv.sh

which contains a function that automatically rebuilds modules if not present for running kernel (or at least it should do that).

//Edit: After having a second look at the script it looks like it does not automatically run that part when booting, so yes, you would have to do that manually after a kernel update or use the approach Sauerland described.

I am using VirtualBox with dkms and my self-written dkms.conf, but for other reasons than this auto-recompile (I even decativate the auto-setup for dkms), so I don’t know how well that script works.

So I can not say if VirtualBox works “automagically” with that script, my point was that with recent versions of VirtualBox from Oracle repo, dkms can not do anything useful as the most important part (= a dkms.conf file) is missing.

AK