osbuild when building images for S390x, such as the 8.4 guest images, follows the kernel-install(8) specification and sets the kernel command line via "/etc/kernel/cmdline". This is also already respected respected on platforms that use grub, via `20-grub.install`. But when using grub2-mkconfig, the file is not read, leading to a loss of kernel command line options. If grub2-mkconfig was to first read, `/etc/kernel/cmdline`, before sourcing `/etc/default/grub`, the new way and the old way could be supported at the same time.
and the grubby tool also needs to learn about /etc/kernel/cmdline
What about having grub2-mkconfig *also* write to /etc/kernel/cmdline when building the kernel opts? I'd expect this to then be used by /usr/lib/kernel/install.d/20-grub.install instead of using /proc/cmdline which may contain non-persistent options. Example with this scenario: 1. Boot with "rd.debug" 2. Update the kernel This will create a BLS entry containing "rd.debug" which is non-sense, due to not relying on content of /etc/kernel/cmdline but /proc/cmdline
(In reply to Renaud Métrich from comment #7) > What about having grub2-mkconfig *also* write to /etc/kernel/cmdline when > building the kernel opts? Yes, agreed. It should do both. Same for grubby as mentioned in Comment 6.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.