Why does the system require a reboot to use the newly installed kernel?
Environment
- Red Hat Enterprise Linux 10
- Red Hat Enterprise Linux 9
- Red Hat Enterprise Linux 8
- Red Hat Enterprise Linux 7
Issue
- Why isn't the newly installed kernel being used?
- Why does the system require a reboot to use the newly installed kernel?
Resolution
- After installing a new kernel, it is set as the default kernel, but a reboot is required to load it.
- To reboot the system, run the
rebootcommand with root privilege. - Services provided by the server will be interrupted by the reboot.
Root Cause
- The kernel is loaded into memory during the boot process and cannot be replaced while the system is running.
- The new kernel requires the bootloader (e.g., GRUB) to load it, which only happens during system startup.
Diagnostic Steps
- Verify the installed kernels:
- Verify which kernel is currently loaded:
- Verify which kernel is set as the default:
- Change the default kernel to the one of the installed kernel:
SBR
Product(s)
Components
Category
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.