AFAICS, the “virtualbox” RPM drops links in ‘/usr/lib/systemd/system/multi-user.target.wants/’ to start the VirtualBox “vboxdrv” (VirtualBox Linux kernel module), and “vboxautostart-service” (starts Virtual Machines at system boot), and “vboxweb-service” (for remote control of the Virtual Machines), services without any further action required by System Administrators.
The systemd “systemctl” status indicates that, the Unit Files are disabled.
Is there any particular reason for this feature of the VirtualBox RPM?
It is how Oracle wants VirtualBox to install - we make it run in OBS so that zypper can install it. Us maintainers do not change anything other than what OBS needs to create the required zypper files. You can build it yourself from the Oracle VirtualBox website - it is not easy to do. Oracle does provide 15.3 (also 15.4 compatible) VirtualBox rpm for OpenSUSE. It requires secure boot to be turned off or for you to sign the rpm yourself.
You still have to get the extension pack from Oracle VirtualBox if you want certain features like cut and paste to/from host.
I’ll make a mental note to remove the links whenever VirtualBox is patched or updated.
I currently have no need for the VirtualBox autostart and web services.
Thanks.
[HR][/HR]I only noticed this because, the web service which got installed at some point in time due to a dependency, has to be configured for it to start successfully – with the default configuration it fails to start during the system boot and, as a result the systemd status is “degraded” …