This has worked fine so far with Virtualbox 4.3.x, but I’m am unable to upgrade to Virtualbox 5.0 because it demands a newer device-mapper.
I have been told that Virtualbox Kernel Stable Standard is built against openSUSE Factory, which contains the newer device-mapper.
I could however get newer device-mapper manually from Factory and upgrade, but I am not sure of the consequences if I do so. I do not want to experiments such on my work laptop.
The reason I am using the latest stable kernel is because it has worked better on my Fujitsu Celsius H730 than the 3.16 kernel that followed with openSUSE 13.2.
Why can’t we get a Kernel Stable repository built for the latest stable openSUSE?
Yes, it will, but you’d need to rebuild the kernel module (with “sudo /etc/init.d/vboxdrv setup”) after every kernel update.
Another option would be to only take the host-kmp package from Virtualization/Kernel_stable_standard, and the other virtualbox packages from the standard 13.2 Virtualization repo.
Your problem is caused by the fact that Virtualization/Kernel_stable_standard is actually built against Factory because of the Kernel.
On 10/15/2015 11:16 AM, wolfi323 wrote:
>
> DJViking;2732405 Wrote:
>> I think I will try to get Virtualbox from Virtualbox repository. Perhaps
>> that will solve the problem of running against the latest kernel.
>> http://download.virtualbox.org/virtualbox/rpm/opensuse/13.2/
>
> Yes, it will, but you’d need to rebuild the kernel module (with “sudo
> /etc/init.d/vboxdrv setup”) after every kernel update.
>
Be careful as this option no longer exists with the latest version of VB.
–
Ken
linux since 1994
S.U.s.E./openSUSE since 1996
Does it not?
And how do you build the kernel module now then?
I’m not using Oracle’s VirtualBox package, and never did, so I can’t tell.
But this might be related to the switch to a native systemd service in Oracle’s version.
PS: I just browsed Oracle’s source code repo, and vboxdrv is still only available as sysvinit script AFAICS, which does still support the “setup” option.
Ah, ok.
The init script is shipped as /usr/lib/virtualbox/vboxdrv.sh, but not installed if the postinstall script detects systemd.
In that case, it creates a systemd unit that just runs /usr/lib/virtualbox/vboxdrv.sh instead.
That (Oracle’s) RPM package is a mess btw IMHO, and buggy as well. (It writes files to the system in the postinstall section without specifying that they are part of the package, uninstalling doesn’t even work as a function related to DKMS is called without specifying the required parameter, which then aborts with an error message…)
The init script is shipped as /usr/lib/virtualbox/vboxdrv.sh, but not installed if the postinstall script detects systemd.
In that case, it creates a systemd unit that just runs /usr/lib/virtualbox/vboxdrv.sh instead.
Yes, but you can not execute the setup, also not with the service:
service vboxdrv
Usage: /sbin/service vboxdrv {start|stop|reload|restart|try-restart|force-reload|status}
That made me a little hesitant about installing the Oracle RPM. Still have not many options.
I could however try the other option you mentioned: to only take the host-kmp package from Virtualization/Kernel_stable_standard and the other virtualbox packages from the standard 13.2 Virtualization repo.