Bug 1937785
Summary: | Fedora install failed with qemu on a P9 PowerPC "couldn't claim memory" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Menanteau Guy <menantea> |
Component: | grub2 | Assignee: | Javier Martinez Canillas <fmartine> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 34 | CC: | bcotton, fmartine, lkundrak, normand, pjones, robatino |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
Whiteboard: | AcceptedFreezeException RejectedBlocker | ||
Fixed In Version: | grub2-2.04-36.fc34 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-06-11 00:24:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1829022 |
Description
Menanteau Guy
2021-03-11 14:49:46 UTC
This should be fixed by grub2-2.04-36 but due the Beta Freeze the version in the install media is still grub2-2.04-35. I'll requesting a Freeze Exception for this bug. Proposed as a Blocker for 34-beta by Fedora user javierm using the blocker tracking app because: Some ppc64le machines fail to boot due GRUB not being able to allocate memory. From today's Go/No-Go meeting: RejectedBlocker(Beta), AcceptedFE(Beta) - ppc64le is not a blocking architecture, but this is worth fixing if we can (In reply to Javier Martinez Canillas from comment #1) > This should be fixed by grub2-2.04-36 but due the Beta Freeze the version > in the install media is still grub2-2.04-35. > > I'll requesting a Freeze Exception for this bug. What is the relative change of grub2-2.04-36 that is supposed to solve this bug described as a P9 specific failure ? This should had been fixed by now, if the issue persists feel free to re-open. |