On 08/05/18 11:22, Sudhir Khanger wrote:
Is that the case with both Oracle and RPMFusion's VirtualBox or
of only former?
I don't normally use the RPMFusion packages. I don't recall why that is. Must
have
had a bad experience at some point. So, today I did install it on a
laptop and found....
When it comes to the drivers they do things differently.
The Oracle method is as I've outlined previously.
As for RPMFusion it utilizes the "akmod" facility to build and install the
modules
when the kernel is updated. This is assuming you've installed
akmod-VirtualBox from RPMfusion.
The akmods facility creates the file /etc/kernel/postinst.d/akmodsposttrans which
checks for the existence of the driver for the newly installed kernel.
It then fires off the process to create the new drivers and this results in the
following in /var/cache/akmods/akmods.log.
2018/08/05 12:56:46 akmods: Building and installing VirtualBox-kmod
2018/08/05 12:56:46 akmods: Building RPM using the command '/sbin/akmodsbuild
--target x86_64 --kernels 4.17.11-200.fc28.x86_64
/usr/src/akmods/VirtualBox-kmod.latest'
2018/08/05 12:57:50 akmods: Installing newly built rpms
2018/08/05 12:57:50 akmods: DNF detected
2018/08/05 12:58:06 akmods: Successful.
This results in the creation and installation of
kmod-VirtualBox-4.17.11-200.fc28.x86_64-5.2.16-1.fc28.x86_64.rpm which contains
(abbreviated)
[root@acer VirtualBox]# rpm2cpio
kmod-VirtualBox-4.17.11-200.fc28.x86_64-5.2.16-1.fc28.x86_64.rpm | cpio -it
./usr/lib/modules/4.17.11-200.fc28.x86_64/extra
./usr/lib/modules/4.17.11-200.fc28.x86_64/extra/VirtualBox
./usr/lib/modules/4.17.11-200.fc28.x86_64/extra/VirtualBox/vboxdrv.ko
./usr/lib/modules/4.17.11-200.fc28.x86_64/extra/VirtualBox/vboxnetadp.ko
./usr/lib/modules/4.17.11-200.fc28.x86_64/extra/VirtualBox/vboxnetflt.ko
./usr/lib/modules/4.17.11-200.fc28.x86_64/extra/VirtualBox/vboxpci.ko
./usr/lib/modules/4.17.11-200.fc28.x86_64/extra/VirtualBox/vboxsf.ko
It also does create the file /lib/modules-load.d/VirtualBox.conf which is one of the
triggers for systemd-modules-load so you will get this on reboot.
[egreshko@acer ~]$ systemctl status systemd-modules-load
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; v>
Active: active (exited) since Sun 2018-08-05 13:08:31 CST; 1min 13s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 541 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, statu>
Main PID: 541 (code=exited, status=0/SUCCESS)
Aug 05 13:08:31
acer.greshko.com systemd-modules-load[541]: Inserted module
'vboxd>
Aug 05 13:08:31
acer.greshko.com systemd-modules-load[541]: Inserted module
'vboxn>
Aug 05 13:08:31
acer.greshko.com systemd-modules-load[541]: Inserted module
'vboxn>
Aug 05 13:08:31
acer.greshko.com systemd-modules-load[541]: Inserted module
'vboxp>
Aug 05 13:08:31
acer.greshko.com systemd[1]: Started Load Kernel Modules.
But, you've said you get a systemd-modules-load failure when the Oracle packages are
installed. I've shown that can't be the case with Oracle.
When comes to RPMFusion the following are now installed on my system.
VirtualBox-server-5.2.16-1.fc28.x86_64
VirtualBox-kmodsrc-5.2.16-1.fc28.noarch
kmod-VirtualBox-4.17.9-200.fc28.x86_64-5.2.16-1.fc28.x86_64
kmod-VirtualBox-4.17.11-200.fc28.x86_64-5.2.16-1.fc28.x86_64
akmod-VirtualBox-5.2.16-1.fc28.x86_64
Assuming you've the same installed you can check the /var/cache/akmods/akmods.log for
any errors during the creation of the rpm.
Also make sure that you have akmods.service enabled.
FYI I have dropped a message for the Bumblebee packager. Let's see if he has some
thoughts.
https://github.com/Bumblebee-Project/Bumblebee/issues/153#issuecomment-41...
FWIW, on the next kernel update you can temporarily remove the bbswitch.conf file
before reboot and see if the error still occurs.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.