• We did not send an email asking for donations - please read this post.

Unknown kernel command line parameters "BOOT_IMAGE=/vmlinuz-5.18.11-1.el7.elrepo.x86_64", will be passed to user space

sandeepvreddy

New Member
Joined
Jul 19, 2022
Messages
2
Reaction score
0
Credits
20
Hi,

On centos 7 after upgrading the kernel to version 5.18.11 I observed the below message in /var/log/messages

kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-5.18.11-1.el7.elrepo.x86_64 root=/dev/mapper/cl-root ro biosdevname=0 net.ifnames=0 crashkernel=auto rd.lvm.lv=cl/root rd.lvm.lv=cl/swap
Unknown kernel command line parameters "BOOT_IMAGE=/vmlinuz-5.18.11-1.el7.elrepo.x86_64", will be passed to user space.


I couldn't get the root cause for this. Any suggestion on this.

Thanks.
 
Last edited:


osprey

Active Member
Joined
Apr 15, 2022
Messages
238
Reaction score
137
Credits
2,183
For starters, you could have a look at the consistency of kernels. The one that booted is output here:
Code:
cat /proc/cmdline
The kernels on the system are usually in /boot:
Code:
ls -al /boot
The ones configured to boot are usually here:
Code:
grep linux /boot/grub/grub.cfg

If they aren't in those locations, you can seek them out in any case to check.
 
OP
S

sandeepvreddy

New Member
Joined
Jul 19, 2022
Messages
2
Reaction score
0
Credits
20
For starters, you could have a look at the consistency of kernels. The one that booted is output here:
Code:
cat /proc/cmdline
The kernels on the system are usually in /boot:
Code:
ls -al /boot
The ones configured to boot are usually here:
Code:
grep linux /boot/grub/grub.cfg

If they aren't in those locations, you can seek them out in any case to check.
The files are at the expected locations. Not sure what exactly caused the above issue. Any other suggestions on this.
 

osprey

Active Member
Joined
Apr 15, 2022
Messages
238
Reaction score
137
Credits
2,183
The kernel message "unknown kernel command line parameters" could be tested by removing one parameter at a time from your kernel line and booting to see which one, or more, the kernel is referring to by noting it's messages. Presumably, from the kernel report, one or more of those parameters is not being implemented in any case. It's a bit of "mucking around" but this approach is what comes to mind at the moment.
 

kvdb

New Member
Joined
Oct 9, 2022
Messages
2
Reaction score
0
Credits
15
I have the same issue with vanilla kernels on Debian. My guess is that distro kernels have some distro specific stuff compiled in that makes them do 'get' the kernel lines in grub. Grub uses templates for that and those are probably modified by distros as well, which might cause the issue when you boot an upstream kernel.
So - if my understanding is correct - the solution would be in modifying the grub templates. (Because this issue seems quite benign (at least in my case) I have not gotten around doing that yet.)
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Linux.org Hosting Donations
Consider making a donation

Members online


Top