-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kdump should auto-add required modules if they are missing from host initrd #11
Comments
Hi, Coiby filed an RH internal jira issue to dracut, dracut team suggest to use --force-add to override the config file |
Hello @daveyoung, sorry for the delayed response I did the following testing today, i was not able to set-up a NFS server for testing so I can only attest what on FCOS, with the default config the NFS module is not loaded in kdump initramfs (as expected):
With the following
I can see the module loaded:
However, using
During the kdump initramfs build dracut fails :
So detecting the |
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11
Issue for |
Please add |
@pvalena See attached log file. It's the output of With
|
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
Hmm, you're right, looking at the code, it looks like the omit_dracutmodules has precedence. I'll look into possible solutions. |
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
The Fedora/RHEL bootc base images have dracut drop-ins which set `dracutmodules+=`. However that seems override explicit module inclusion on the command line, which is a dracut bug: rhkdump#11 Work around this by making our own copy of the global config, and omitting config drop-ins which trigger this behavior. I think longer term, this project should probably own its own global dracut config, actually. But that's a much larger set of work. Signed-off-by: Colin Walters <walters@verbum.org>
Related #29 |
The Fedora/RHEL bootc base images have dracut drop-ins which set `dracutmodules+=`. However that seems override explicit module inclusion on the command line, which is a dracut bug: rhkdump#11 Work around this by making our own copy of the global config, and omitting config drop-ins which trigger this behavior. I think longer term, this project should probably own its own global dracut config, actually. But that's a much larger set of work. omit_dracutmodules= is also problematic, so skip that too. Signed-off-by: Colin Walters <walters@verbum.org>
When generating kdump's initrd, we want to keep [omit_]dracutmodules empty and let kdump to handle the modules. And we don't want to affect the first kernel's initrd, so we cannot place our conf file to /etc/dracut.conf.d or /usr/lib/dracut/dracut.conf.d. This patch adds a new option to allow user to add an extra configuration directory to use *.conf files from. After that, kdump will use --extra-confdir /usr/lib/kdump/dracut.conf.d to apply its own dracut conf. See also: rhkdump/kdump-utils#11 rhkdump/kdump-utils#31 Suggested-by: Dave Young <dyoung@redhat.com> Signed-off-by: Lichen Liu <lichliu@redhat.com>
When generating kdump's initrd, we want to keep [omit_]dracutmodules empty and let kdump to handle the modules. And we don't want to affect the first kernel's initrd, so we cannot place our conf file to /etc/dracut.conf.d or /usr/lib/dracut/dracut.conf.d. This patch adds a new option to allow user to add an extra configuration directory to use *.conf files from. After that, kdump will use --extra-confdir /usr/lib/kdump/dracut.conf.d to apply its own dracut conf. See also: rhkdump/kdump-utils#11 rhkdump/kdump-utils#31 Suggested-by: Dave Young <dyoung@redhat.com> Signed-off-by: Lichen Liu <lichliu@redhat.com>
When generating kdump's initrd, we want to keep [omit_]dracutmodules empty and let kdump to handle the modules. And we don't want to affect the first kernel's initrd, so we cannot place our conf file to /etc/dracut.conf.d or /usr/lib/dracut/dracut.conf.d. This patch adds a new option to allow user to add an extra configuration directory to use *.conf files from. After that, kdump will use --extra-confdir /usr/lib/kdump/dracut.conf.d to apply its own dracut conf. See also: rhkdump/kdump-utils#11 rhkdump/kdump-utils#31 Suggested-by: Dave Young <dyoung@redhat.com> Signed-off-by: Lichen Liu <lichliu@redhat.com>
When generating kdump's initrd, we want to keep [omit_]dracutmodules empty and let kdump to handle the modules. And we don't want to affect the first kernel's initrd, so we cannot place our conf file to /etc/dracut.conf.d or /usr/lib/dracut/dracut.conf.d. This patch adds a new option to allow user to add an extra configuration directory to use *.conf files from. After that, kdump will use --extra-confdir /usr/lib/kdump/dracut.conf.d to apply its own dracut conf. See also: rhkdump/kdump-utils#11 rhkdump/kdump-utils#31 Suggested-by: Dave Young <dyoung@redhat.com> Signed-off-by: Lichen Liu <lichliu@redhat.com>
On RHCOS, the nfs module is explicitly excluded from the initramfs: https://github.com/coreos/fedora-coreos-config/blob/de0416b8820cffa2ea3b7dbd9e95a9cc0ad9a42b/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7 Thus, setting an NFS target destination in kdump.conf will not work because the kdump initramfs will not have the NFS module. Add instruction on how to add the module to enable the functionality. This may not be necessary if kdump auto-detect the required modules: See rhkdump/kdump-utils#11 Co-authored-by: Jesse Dohmann <jdohmann@redhat.com>
In Fedora CoreOS, we exclude nfs from the initramfs as booting from NFS is not supported : https://github.com/coreos/fedora-coreos-config/blob/testing-devel/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf#L7
However, dumping with kdump to a target destination should work obviously. Currently, this requires the users to add
extra_modules nfs
to/etc/kdump.conf
.Could the module be added automatically when the target is a NFS destination ?
ref: coreos/fedora-coreos-tracker#1729
The text was updated successfully, but these errors were encountered: