On Tue, Jul 24, 2018 at 3:49 AM Ed Greshko <ed.gres...@greshko.com> wrote:
> On 07/23/18 17:04, Sudhir Khanger wrote: > > Okay update time. Irrespective of where I install VirtualBox from if a > new kernel > > is installed then I have to manually create a new initramfs > > otherwise systemd-modules-load.service fails at the boot. > > > > When it comes to VirtualBox from Oracle I find that statement "odd" to say > the least. > > When I install the VirtualBox from Oracle it installs > /lib/systemd/system/vboxdrv.service. When the system starts if there is > no driver > matching the running kernel it will be built and then loaded. > > This results in.... > > [egreshko@meimei ~]$ systemd-analyze blame > 52.215s vboxdrv.service > > And in the journal.... > > Jul 22 17:00:54 meimei.greshko.com vboxdrv.sh[728]: vboxdrv.sh: Starting > VirtualBox > services. > Jul 22 17:00:54 meimei.greshko.com vboxdrv.sh[887]: Starting VirtualBox > services. > Jul 22 17:00:54 meimei.greshko.com vboxdrv.sh[728]: vboxdrv.sh: Building > VirtualBox > kernel modules. > Jul 22 17:00:54 meimei.greshko.com vboxdrv.sh[892]: Building VirtualBox > kernel modules. > Jul 22 17:01:45 meimei.greshko.com vboxdrv.sh[6011]: VirtualBox kernel > modules built. > Jul 22 17:01:45 meimei.greshko.com kernel: vboxdrv: Found 4 processor > cores > Jul 22 17:01:46 meimei.greshko.com kernel: vboxdrv: TSC mode is > Invariant, tentative > frequency 2660206031 Hz > Jul 22 17:01:46 meimei.greshko.com kernel: vboxdrv: Successfully loaded > version > 5.2.16 (interface 0x00290001) > Jul 22 17:01:46 meimei.greshko.com vboxdrv.sh[6052]: VirtualBox services > started. > Jul 22 17:01:46 meimei.greshko.com audit[1]: SERVICE_START pid=1 uid=0 > auid=4294967 > 295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=vboxdrv > comm="systemd > " exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > > > [egreshko@meimei ~]$ lsmod | grep vbox > vboxpci 28672 0 > vboxnetadp 28672 0 > vboxnetflt 32768 1 > vboxdrv 491520 4 vboxpci,vboxnetadp,vboxnetflt > > [egreshko@meimei ~]$ uname -r > 4.17.7-200.fc28.x86_64 > > And, as you can see, the built driver was created at boot time.... > > [egreshko@meimei ~]$ ll > /usr/lib/modules/4.17.7-200.fc28.x86_64/misc/vboxdrv.ko > -rw-r--r--. 1 root root 14121784 Jul 22 17:01 > /usr/lib/modules/4.17.7-200.fc28.x86_64/misc/vboxdrv.ko > > -- > Conjecture is just a conclusion based on incomplete information. It isn't > a fact. > > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/6D2D664T5LTUDRN6GGJ4EMGVQRJCMCYT/ > systemd-modules-load.service fails at boot and then it probably builds the modules. After the system boots, systemd-modules-load.service has active status and not failed. But the only way to get rid of Failed to start Load Kernel Modules is by rebuilding initramfs via command dracut -v -f. This error crops up everytime you install a new kernel irrespective of VirtualBox's installation source. -- Regards, Sudhir Khanger, sudhirkhanger.com.
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/X4VOAJ5NM3HIQCETJMEBET2EKI44HYEQ/
