Red Hat Bugzilla – Bug 1305339
[RFE] - Allow addition of boot kernel params arguments
Last modified: 2016-07-05 03:47:07 EDT
Description of problem:
[RFE] - Add boot kernel params arguments and an option to enable them via TUI
Today the raw arguments are not exposed in the TUI anywhere, and can be appended via the syslinux menu as a work around.
It will be good to expose boot kernel params, such as 'intel_iommu=on' in the TUI in order to use SR-IOV feature for example on 3.6 and an option to enable them via the TUI.
see also related bug 1301104
We'll be supporting grubby for custom kernel arguments as described here:
QE will verify this bug according to _comment 2_ with grubby tool to persist changes to the grub.
Fabian, shouldn't this be targetted to 3.6 actually? We do need kernel arguments for VFIO passthrough and since this is mostly just documentation and testing it shouldn't be a big deal to support it on 7.2, right?
We have a documented way of how to add kernel arguments to vintage RHEV-H:
To me this looks sufficient.
It is sufficient indeed. Ok, so in 3.6 it's the "old" manual way described there, in 4.0 it's the grubby way
Thank you for clarification
Created attachment 1150752 [details]
Test the grubby way to add boot kernel arguments with ovirt-node-ng-installer-ovirt-4.0-2016042500.iso, the issue is verified successfully.
1. Install ovirt-node 4.0 in a machine with kickstart file
2. Login, then input CLI according to https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-Making_Persistent_Changes_to_a_GRUB_2_Menu_Using_the_grubby_Tool.html
grubby --remove-args="arg1 arg2" --args="argA argB" --update-kernel /boot/kernel-name
grubby --info /boot/kernel-name
3. reboot to check the arguments are effected.
The added arguments are effected by using grubby way.
So this bug is verified now, change the bug status to VERIFIED.
oVirt 4.0.0 has been released, closing current release.