RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 628487 [details]
wrong_grub_interface

Description of problem:
Install guest RHEL7 with kernel-3.6.0-0.28.el7(x86_64) on ESXi5.1,after finished installation,reboot with a keystroke to edit the grub,then with a wrong grub interface(details in attachment),cannot edit the guest kernel.

Version-Release number of selected component (if applicable):
ESXi:ESXi5.1.0
ESXi guest:RHEL7 with kernel-3.6.0-0.28.el7(x86_64)

How reproducible:
100%

Steps to Reproduce:
1.Install the RHEL7 with kernel-3.6.0-0.28.el7(x86_64) on ESXi
2.Reboot the guest
3.by a kerstroke to trigger the grub edit

Actual results:
After a kerstroke,it will provide a wrong grub interface(details in attachment).


Expected results:
Can using the grub to edit the guest kernel.

Additional info:
On the version RHEL7 with kernel-3.3.0-0.20.el7 has no this issue.It might be a regression bug.

The issue is not any more blocker.As you can enter into the target esxi vm kde desktop by installing the package below when you manually install the rhel7:
<1>x window system
<2>kde desktop

But the grub still in wrong interface status.

Just confirmed that the grub menu shows up and could be edit when the RHEL7 guest booting up with the updated grub2 package.

ESXi: ESXi5.1.0
Guest: RHEL-7.0-20130120.0 (3.7.0-0.32.el7.x86_64)

The grub packages using for testing are:
grub2-2.00-15.el7.x86_64
grubby-8.22-1.el7.x86_64
grub2-tools-2.00-15.el7.x86_64

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.