Bug 4100

I am unable to find clear explanations on severity levels, but as the package won't build at all, it probably should be major.

we have VirtualBox-5.0.24 in updates, since a few hours,  have you update it ? 
after update  please run akmods-shutdown (as root)

(In reply to comment #2)
> we have VirtualBox-5.0.24 in updates, since a few hours,  have you update it ? 
> after update  please run akmods-shutdown (as root)

After the update, the rpm is being built and installed correctly. I still have an issue with the kernel module loading, in that systemctl restart systemd-modules-load.service is failing, but if I modprobe vboxdrv, vboxnetflt, vboxnetadp and vboxpci then everything works. I don't know if this is a related issue or something else.

I have the same issue about loading virtualbox driver, without trouble if the loading is manual.

Can someone post result of, please : 

    systemctl status systemd-modules-load.service -l 

and after: 
    
    dmesg | tail -n 20 

Thanks.

[root@Ducky ~]#     systemctl status systemd-modules-load.service -l 
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since mer. 2016-07-06 09:55:22 CEST; 18min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
 Main PID: 994 (code=exited, status=1/FAILURE)

juil. 06 09:55:21 Ducky systemd[1]: Starting Load Kernel Modules...
juil. 06 09:55:21 Ducky systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
juil. 06 09:55:21 Ducky systemd[1]: Failed to start Load Kernel Modules.
juil. 06 09:55:21 Ducky systemd[1]: systemd-modules-load.service: Unit entered failed state.
juil. 06 09:55:21 Ducky systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
juil. 06 09:55:22 Ducky systemd[1]: Starting Load Kernel Modules...
juil. 06 09:55:22 Ducky systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
juil. 06 09:55:22 Ducky systemd[1]: Failed to start Load Kernel Modules.
juil. 06 09:55:22 Ducky systemd[1]: systemd-modules-load.service: Unit entered failed state.
juil. 06 09:55:22 Ducky systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.



[root@Ducky ~]#     dmesg | tail -n 20 
[   37.129259] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[   37.333236] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[   37.591761] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[   37.982844] Netfilter messages via NETLINK v0.30.
[   38.016821] ip_set: protocol 6
[   40.819349] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[   40.819380] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[   42.758370] tun: Universal TUN/TAP device driver, 1.6
[   42.758372] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   42.796599] virbr0: port 1(virbr0-nic) entered blocking state
[   42.796601] virbr0: port 1(virbr0-nic) entered disabled state
[   42.796655] device virbr0-nic entered promiscuous mode
[   43.163919] virbr0: port 1(virbr0-nic) entered blocking state
[   43.163921] virbr0: port 1(virbr0-nic) entered listening state
[   43.371468] virbr0: port 1(virbr0-nic) entered disabled state
[   43.764663] device virbr0-nic left promiscuous mode
[   43.764685] virbr0: port 1(virbr0-nic) entered disabled state
[   53.914431] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[   97.144580] fuse init (API version 7.24)
[  109.793580] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

 Build fail log  is from VirtualBox-kmod-5.0.16, now we got VirtualBox-kmod-5.0.24 and 5.0.26 in on updates-testing , so I deduce this bug is fix , thanks for reporting, closing the bug.

The original reported bug reported is indeed fixed in 5.0.24. I've opened bug 4147 about the module loading issue.