From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
Cc: Dhaval Giani <dhaval.giani@gmail.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Kernel Compile Issue
Date: Sat, 26 Jun 2021 02:39:39 -0400 [thread overview]
Message-ID: <29442.1624689579@turing-police> (raw)
In-Reply-To: <CAFSeFg92z26U3ig3DDbeXE=4_j8_faf1Tp7tOkrTGY9u7Aj7Yw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1304 bytes --]
On Fri, 25 Jun 2021 16:05:45 -0400, Aruna Hewapathirane said:
> Jun 25 10:46:42 debian systemd-modules-load[201]: Failed to find module 'vmhgfs'
> Jun 25 10:46:42 debian systemd[1]: Failed to start Load Kernel Modules.
> Jun 25 10:46:42 debian systemd[1]: Unit systemd-modules-load.service entered failed state.
>
> Does that make sense to you or anyone ?
For reasons understandable only to systemd, it tried to modprobe vmhgfs and
didn't find it in the initramfs. Does this configuration actually *need* a
vmware shared folder in order to boot? If so, you'll need to tell your dracut/
mkinitramfs/whatever command to include it. If not, you'll need to tell it to
not look for it.
(Particularly annoying - dracut will include that systemd unit even if you
have a kernel that doesn't need any modules to boot because all the requisites
are built-in, you said --no-kernel to not include kernel modules in the
initramfs, and you gave it -o "kernel-modules kernel-modules-extra kernel-network-modules"
to omit those dracut modules from the run. I submitted a patch that was
rejected, because apparently *some* places build an initramfs with 'dracut
--no-kernel' and then append another cpio image that contains kernel modules,
and the patch would break that. This is why we can't have nice things.)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-06-26 6:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 2:48 Kernel Compile Issue Aruna Hewapathirane
2021-06-24 10:21 ` Thomas Bracht Laumann Jespersen
2021-06-24 13:35 ` Aruna Hewapathirane
2021-06-24 16:13 ` Cindy Sue Causey
2021-06-24 17:56 ` Aruna Hewapathirane
2021-06-24 17:29 ` Thomas Bracht Laumann Jespersen
2021-06-24 18:19 ` Aruna Hewapathirane
2021-06-24 23:09 ` Valdis Klētnieks
2021-06-24 23:36 ` Aruna Hewapathirane
2021-06-25 0:51 ` Valdis Klētnieks
2021-06-25 20:05 ` Aruna Hewapathirane
2021-06-26 6:39 ` Valdis Klētnieks [this message]
2021-06-28 11:58 ` Aruna Hewapathirane
2021-06-29 9:25 ` Thomas Bracht Laumann Jespersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29442.1624689579@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=aruna.hewapathirane@gmail.com \
--cc=dhaval.giani@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox