Comment # 5 on bug 943717 from Wolfgang Bauer

(In reply to Krasimir Ivanov from comment #4)
> The check shows as follows:
> # systemctl status vboxdrv
> vboxdrv.service - LSB: VirtualBox Linux module
>    Loaded: loaded (/etc/init.d/vboxdrv)
>    Active: inactive (dead)
> 
> Then I started it from the CLI and then try my virtual machines.
> It worked!

Ok, so apparently it's just not started during boot.
Is it marked as "enabled" in YaST?
If yes, please run "systemctl status vboxdrv" as root to find out what the
problem is.

My suspicion: vboxdrv has $syslog and $remote_fs as dependencies. If one fails
to start, vboxdrv is not started either. This can happen e.g. if you have a
network share in /etc/fstab that cannot be mounted AFAIK.

> Now in the Services Manager vboxdrv is marked as active.
> But I could not make there active the Voboxadd.

vboxadd are the guest additions. You cannot (and need not) start them on the
host.