Yes, you have to be member of vboxusers to be able to run it.
But the /usr/bin/VirtualBox script should actually show a warning dialog otherwise.
It seems this is part of the problem:
/usr/bin/VirtualBox: line 5: /usr/lib/virtualbox/VBoxUSB_DevRules: No such file or directory
It’s caused by this “code” that has been added recently to warn users that they have to modify some udev rules to get USB support (a lot of users “complained” that openSUSE’s packages do not support USB at all; they do, but it’s disabled by default because of security concerns)
if ! -f /etc/udev/rules.d/60-vboxdrv.rules ]; then
/usr/lib/virtualbox/VBoxUSB_DevRules && sudo touch /etc/udev/rules.d/60-vboxdrv.rules
Apparently /usr/lib/virtualbox/VBoxUSB_DevRules (which is supposed to show the warning dialog) is missing in the package.
Should be reported as bug. And I have no idea how that “sudo touch” is supposed to work at all anyway.
To fix it, just run “sudo touch /etc/udev/rules.d/60-vboxdrv.rules” or copy over /usr/lib/udev/rules.d/60-vboxdrv.rules to /etc/udev/rules.d/.
It works great here since even longer. And I always used the openSUSE packages, never had any problem…
For Leap (and every opensuse release back to 12.1) i had to install make, gcc, gcc-c++, kernel-source, kernel-syms
then i had to modprobe vboxdrv, vboxnetadp, and vboxnetflt
don’t forget to modify your startup scripts by adding the modules above to a new script in /etc/modules-load.d/ or you’ll need to load those three modules after every reboot for virtualbox to work.
None of this is necessary.
If the vboxdrv.service is enabled (it is by default), it will load the kernel modules on boot.
make, gcc, gcc-c++, kernel-source, kernel-syms are only needed to compile the kernel modules. But openSUSE’s packages come with them pre-compiled, that’s only needed if you install VirtualBox from virtualbox.org.
So you either confuse things here, or you maybe installed both versions (openSUSE’s and Oracle’s), which will give you problems sooner or later.