Bonjour,
At every boot I can see this message: system-load-modules fails to load vboxpci, vboxnetadp, vboxnetflt, vboxdrv but when system is up, lsmod shows these modules as loaded!
What's this?
Regards
Allegedly, on or about 18 March 2018, François Patte sent:
At every boot I can see this message: system-load-modules fails to load vboxpci, vboxnetadp, vboxnetflt, vboxdrv but when system is up, lsmod shows these modules as loaded!
Perhaps the first attempt fails, but a subsequent one succeeds?
On 03/18/18 19:38, François Patte wrote:
At every boot I can see this message: system-load-modules fails to load vboxpci, vboxnetadp, vboxnetflt, vboxdrv but when system is up, lsmod shows these modules as loaded!
Could you examine your logs and post the actual messages? And, are you using VirtualBox from rpmfusion or directly from Oracle?
Le 18/03/2018 à 13:31, Ed Greshko a écrit :
On 03/18/18 19:38, François Patte wrote:
At every boot I can see this message: system-load-modules fails to load vboxpci, vboxnetadp, vboxnetflt, vboxdrv but when system is up, lsmod shows these modules as loaded!
Could you examine your logs and post the actual messages?
In fact, it seems to randomly depend on the boot, for instance:
yesterday at 22h34:
------------------------------------------------------> mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAI mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Unit entered failed state. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: Starting Load Kernel Modules... mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAI mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Unit entered failed state. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: Starting Load Kernel Modules... mars 17 22:34:00 dipankar systemd-modules-load[1135]: Failed to lookup alias 'vboxdrv': Function not implemented mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAI mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Unit entered failed state. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: Starting Load Kernel Modules... mars 17 22:34:00 dipankar systemd-modules-load[1154]: Failed to lookup alias 'vboxdrv': Function not implemented mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAI mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Unit entered failed state. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: Starting Load Kernel Modules... mars 17 22:34:00 dipankar systemd-modules-load[1161]: Failed to lookup alias 'vboxdrv': Function not implemented mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAI mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Unit entered failed state. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Start request repeated too quickly. mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Start request repeated too quickly. mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. <---------------------------------------------------------------
Then, 4 minutes later:
----------------------------------------------------------------> mars 17 22:38:07 dipankar systemd-modules-load[817]: Inserted module 'vboxdrv' mars 17 22:38:07 dipankar systemd-modules-load[817]: Inserted module 'vboxnetflt' mars 17 22:38:07 dipankar systemd-modules-load[817]: Inserted module 'vboxnetadp' mars 17 22:38:07 dipankar systemd-modules-load[817]: Inserted module 'vboxpci' mars 17 22:38:07 dipankar systemd[1]: Started Load Kernel Modules. mars 17 23:33:57 dipankar systemd[1]: Stopped Load Kernel Modules. <--------------------------------------------------------------
And, are you using VirtualBox from rpmfusion or directly from Oracle?
rpmfusion
On 03/18/18 21:29, François Patte wrote:
Le 18/03/2018 à 13:31, Ed Greshko a écrit :
On 03/18/18 19:38, François Patte wrote:
At every boot I can see this message: system-load-modules fails to load vboxpci, vboxnetadp, vboxnetflt, vboxdrv but when system is up, lsmod shows these modules as loaded!
Could you examine your logs and post the actual messages?
In fact, it seems to randomly depend on the boot, for instance:
yesterday at 22h34:
------------------------------------------------------> mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAI mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Unit entered failed state. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: Starting Load Kernel Modules... mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAI mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Unit entered failed state. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: Starting Load Kernel Modules... mars 17 22:34:00 dipankar systemd-modules-load[1135]: Failed to lookup alias 'vboxdrv': Function not implemented mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAI mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Unit entered failed state. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: Starting Load Kernel Modules... mars 17 22:34:00 dipankar systemd-modules-load[1154]: Failed to lookup alias 'vboxdrv': Function not implemented mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAI mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Unit entered failed state. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: Starting Load Kernel Modules... mars 17 22:34:00 dipankar systemd-modules-load[1161]: Failed to lookup alias 'vboxdrv': Function not implemented mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAI mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Unit entered failed state. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Start request repeated too quickly. mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Start request repeated too quickly. mars 17 22:34:00 dipankar systemd[1]: Failed to start Load Kernel Modules. mars 17 22:34:00 dipankar systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. <---------------------------------------------------------------
Then, 4 minutes later:
----------------------------------------------------------------> mars 17 22:38:07 dipankar systemd-modules-load[817]: Inserted module 'vboxdrv' mars 17 22:38:07 dipankar systemd-modules-load[817]: Inserted module 'vboxnetflt' mars 17 22:38:07 dipankar systemd-modules-load[817]: Inserted module 'vboxnetadp' mars 17 22:38:07 dipankar systemd-modules-load[817]: Inserted module 'vboxpci' mars 17 22:38:07 dipankar systemd[1]: Started Load Kernel Modules. mars 17 23:33:57 dipankar systemd[1]: Stopped Load Kernel Modules. <--------------------------------------------------------------
And, are you using VirtualBox from rpmfusion or directly from Oracle?
rpmfusion
Are you rebooting due to a kernel update? And, do you have akmod-VirtualBox installed?
If the above it true, then you're rebooting too soon after the update process and the akmod process hasn't finished building the kernel modules. So, on reboot the module load will initially fail. Then akmod will build the modules and load them.
Do you have a /var/cache/akmods/akmods.log? If so, does it have entries at the times noted in your logs?
Le 18/03/2018 à 14:44, Ed Greshko a écrit :
On 03/18/18 21:29, François Patte wrote:
Le 18/03/2018 à 13:31, Ed Greshko a écrit :
On 03/18/18 19:38, François Patte wrote
Are you rebooting due to a kernel update? And, do you have akmod-VirtualBox installed?
If the above it true, then you're rebooting too soon after the update process and the akmod process hasn't finished building the kernel modules. So, on reboot the module load will initially fail. Then akmod will build the modules and load them.
That was a good idea: yes sometimes I update my machine before stopping it. Yesterday, as there were a new kernel, I updated the system and waited until the whole process finished (using top to watch this update process) and today, in the boot logs, I get:
mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find module 'vboxdrv' mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find module 'vboxnetflt' mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find module 'vboxnetadp' mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find module 'vboxpci' mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module 'vboxdrv' mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module 'vboxnetflt' mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module 'vboxnetadp' mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module 'vboxpci' mars 19 09:17:32 dipankar audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Only 2 seconds between the time modules are not found and the time these modules are inserted...
Strange!
Do you have a /var/cache/akmods/akmods.log? If so, does it have entries at the times noted in your logs?
modules were successfully built and installed yesterday evening:
2018/03/18 23:03:41 akmods: Building and installing VirtualBox-kmod 2018/03/18 23:03:41 akmods: Building RPM using the command '/sbin/akmodsbuild --target x86_64 --kernels 4.15.9-300.fc27.x86_64 /usr/src/akmods/VirtualBox-kmod.latest' 2018/03/18 23:04:06 akmods: Installing newly built rpms 2018/03/18 23:04:06 akmods: DNF detected 2018/03/18 23:04:14 akmods: Successful.
On 03/19/18 17:00, François Patte wrote:
That was a good idea: yes sometimes I update my machine before stopping it. Yesterday, as there were a new kernel, I updated the system and waited until the whole process finished (using top to watch this update process) and today, in the boot logs, I get:
mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find module 'vboxdrv' mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find module 'vboxnetflt' mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find module 'vboxnetadp' mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find module 'vboxpci' mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module 'vboxdrv' mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module 'vboxnetflt' mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module 'vboxnetadp' mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module 'vboxpci' mars 19 09:17:32 dipankar audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Only 2 seconds between the time modules are not found and the time these modules are inserted...
Strange!
Too bad the log isn't very detailed.
It sounds as if systemd-modules-load is looking first in one place for the modules and not finding them. Then, moving on to a second location and finding them. What are the contents of /etc/modules-load.d/*.conf and /usr/lib/modules-load.d/*.conf ?
-
Ed Greshko -
François Patte -
Tim