Bug 769529

Summary: RHEL6.x UEFI PXE boot gets stuck at grub command line
Product: Red Hat Enterprise Linux 6 Reporter: mhosamani <manjuhosamani1985>
Component: anacondaAssignee: Peter Jones <pjones>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.2CC: dabecka, mkovarik, silverhammermba
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-09 08:32:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
PXE server configuaration and tcpdump traces
none
PXE server configuration
none
tcpdump capture on PXE server interface connecting to PXE clinet interface
none
wireshark trace on PXE server interface none

Description mhosamani 2011-12-21 08:28:09 UTC
Created attachment 548995 [details]
PXE server configuaration and tcpdump traces

While performing UEFI PXE boot for RHEL6.x (RHEL6.1/2) the PXE client is able to download bootx64.efi image successfully. However PXE client never requested for configuration file BOOTX64.conf from PXE server and hence unable to load vmlinuz and initrd images. PXE client gets stuck in the grub command line and won't proceed beyond that. This issue can be produced with Emulex oneconnect CNA's and intel X520 CNA.


Steps to Reproduce:
1. Setup PXE server as mentioned in the attached file
2. Boot from PXE client to PXE server
3. PXE clinet will get IP address assigned by DHCP server running in PXE server mechine and get the bootx64.efi image file
4. PXE client gets stuck at grub command line and never be able to proceed beyond that.
  
Actual results:
PXE clinet gets the DHCP adrress and bootx64.efi file gets transfeered via TFTP server, however PXE clinet never requested for configuaration file BOOTX64.conf which specifies the location of initrd and vmlinuz images.

Expected results:
PXE client should request configuartion file BOOTX64.conf from PXE server and after that vmlinz and initrd images should be loaded and installation process should begin

Additional info:
attached zip file contains two files in it.
1.	Steps that we did to configure the UEFI PXE server (RHEL6.X-UEFI_Config)
2.	Wireshark trace taken on the PXE server interface while client was booting to the PXE server (PXE_Traces_RHEL6.1)

Comment 2 Chris Lumens 2011-12-21 17:42:31 UTC
Please attach log files to this bug as individual, text attachments.  Doing otherwise prevents us from being able to search through bugs in the future.

Comment 3 mhosamani 2011-12-22 03:35:50 UTC
Created attachment 549119 [details]
PXE server configuration

Comment 4 mhosamani 2011-12-22 03:37:20 UTC
Created attachment 549120 [details]
tcpdump capture on PXE server interface connecting to PXE clinet interface

Comment 5 mhosamani 2011-12-22 03:41:43 UTC
requested logfiles attached.

Comment 6 mhosamani 2012-01-05 07:14:38 UTC
Could you please assign this CR to someone ?

Comment 7 mhosamani 2012-01-06 10:59:23 UTC
Created attachment 551125 [details]
wireshark trace on PXE server interface

Comment 8 Michal Kovarik 2012-01-09 08:32:04 UTC

*** This bug has been marked as a duplicate of bug 670266 ***

Comment 9 Max 2012-02-13 15:53:47 UTC
bug 670266 is not accessible. What was the resolution, if any, for this bug?

Comment 10 Christian Becker 2012-05-07 17:12:50 UTC
This bug is also relevant for me. We´re using IBM System X 3650 M3 and 3690 X5, and we´re unable to pxe boot our servers using UEFI. Can someone provide any details about the referenced bug, since it´s not visible.

Comment 11 Michal Kovarik 2012-05-09 07:05:39 UTC
This bug should be fixed in grub-0.97-77.el6 which should be released in RHEL6.3