This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2144473 - http boot on aarch64 fails if client has >3G RAM
Summary: http boot on aarch64 fails if client has >3G RAM
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: grub2
Version: 8.7
Hardware: aarch64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-21 12:00 UTC by Marta Lewandowska
Modified: 2023-09-16 17:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-16 17:08:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
tcpdump (318.43 KB, text/plain)
2022-11-21 12:00 UTC, Marta Lewandowska 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4338 0 None Migrated None 2023-09-16 17:08:48 UTC
Red Hat Issue Tracker RHELPLAN-140015 0 None None None 2022-11-21 12:06:25 UTC

Description Marta Lewandowska 2022-11-21 12:00:52 UTC 
Created attachment 1926073 [details]
tcpdump

Created attachment 1926073 [details]
tcpdump

Description of problem:
http boot-- serving shim/grub/kernel over http-- (ipv4 or ipv6) fails on aarch64 if the VM guest has >3G RAM

Version-Release number of selected component (if applicable):
Happens on all grubs that have been tested: ...8.5, 8.6, 8.7, 9.0, 9.1

How reproducible:
100%

Steps to Reproduce:
1. Create dhcp & http server serving shim and/or grub + kernel, initramfs
(see https://docs.engineering.redhat.com/pages/viewpage.action?pageId=151047351 for manual directions)
2. Create client VM (with more than 3072M RAM) on same network which boots over NIC
3. Attempt to install RHEL on client from http server

Actual results:
>>Start HTTP Boot over IPv4....
  Station IP address is 192.168.124.145

  URI: http://192.168.124.2/grubaa64.efi
  File Size: 2384328 Bytes
  Downloading...100%BdsDxe: loading Boot0005 "UEFI HTTPv4 (MAC:525400616165)" fr
om PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(525400616165,0x1)/IPv4(0.0.0.0,0x0
,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)/Uri()
BdsDxe: starting Boot0005 "UEFI HTTPv4 (MAC:525400616165)" from PciRoot(0x0)/Pci
(0x1,0x0)/Pci(0x0,0x0)/MAC(525400616165,0x1)/IPv4(0.0.0.0,0x0,DHCP,0.0.0.0,0.0.0
.0,0.0.0.0)/Uri()
AllocatePoolPages: failed to allocate 8388609 pages
AllocatePool: failed to allocate 34359738432 bytes
error: ../../grub-core/net/efi/http.c:254:Fail to send a request! status=0x9
.
HttpCreateConnection: Tcp4->Connect() = Invalid Parameter
Tcp4 Connection fail - 2
error: ../../grub-core/net/efi/http.c:254:Fail to send a request! status=0x2
.
HttpCreateConnection: Tcp4->Connect() = Invalid Parameter
Tcp4 Connection fail - 2
error: ../../grub-core/net/efi/http.c:254:Fail to send a request! status=0x2
.
HttpCreateConnection: Tcp4->Connect() = Invalid Parameter
Tcp4 Connection fail - 2
error: ../../grub-core/net/efi/http.c:254:Fail to send a request! status=0x2
.
HttpCreateConnection: Tcp4->Connect() = Invalid Parameter
Tcp4 Connection fail - 2
error: ../../grub-core/net/efi/http.c:254:Fail to send a request! status=0x2
.
HttpCreateConnection: Tcp4->Connect() = Invalid Parameter
Tcp4 Connection fail - 2
error: ../../grub-core/net/efi/http.c:254:Fail to send a request! status=0x2
.

.
.
.

      Minimal BASH-like line editing is supported. For the first word,    
      TAB lists possible command completions. Anywhere else TAB lists     
      possible device or file completions.                                


grub> 

(this machine had 4G RAM, giving the VM more RAM results in grub trying to allocate more pages / bytes)

Expected results:
Memory gets allocated and installer starts

Additional info:
tcpdump during relevant negotiation attached
Comment 1 RHEL Program Management 2023-09-16 17:07:34 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2 RHEL Program Management 2023-09-16 17:08:55 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.