Kernelopts not propagating to redhat/grubenv from grub2/grubenv

Solution Verified - Updated -

Issue

  • After converting an Azure Generation 1 (BIOS) VM image to Generation 2 (UEFI), updated kernel parameters (such as FIPS kernelopts) or default kernel selections made via grubby do not take effect upon reboot.
    • Checking /boot/grub2/grubenv reveals that it is a regular file instead of a symbolic link pointing to the EFI directory.
    • /boot/efi/EFI/redhat/grubenv is either missing or does not reflect updates made by grubby.

Environment

  • Red Hat Enterprise Linux 9
  • Red Hat Enterprise Linux 8
  • Microsoft Azure Gen1 to Gen2 VM migration/conversion
  • UEFI

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content