I am not able to install a fresh Fedora 34 on a qemu running on a P9 powerpc. Error reported is: error: ../../grub-core/loader/powerpc/ieee1275/linux.c:249:couldn't claim memory. I tried with Fedora-Server-dvd-ppc64le-34-20210310.n.0.iso but it seems is was already there for older iso. How reproducible: On a powerpc P9, run the following qemu command. /usr/bin/qemu-system-ppc64 -vga std -m 4096 -netdev user,id=qanet0 -device virtio-net,netdev=qanet0,mac=52:54:00:12:34:56 -device virtio-scsi-pci,id=scsi0 -device virtio-blk,drive=hd1,serial=1 -drive file=hd1.qcow2,cache=unsafe,if=none,id=hd1,format=qcow2 -drive media=cdrom,if=none,id=cd0,format=raw,file=Fedora-Server-dvd-ppc64le-34-20210310.n.0.iso -device scsi-cd,drive=cd0,bus=scsi0.0 -smp 1 -enable-kvm -no-shutdown -S -nographic -nodefaults -monitor stdio -serial pty -boot d at boot grub menu, select: Install Fedora 34 (64-bit kernel) Actual results: error: ../../grub-core/loader/powerpc/ieee1275/linux.c:249:couldn't claim memory. error: ../../grub-core/loader/powerpc/ieee1275/linux.c:347:you need to load the kernel first. Press any key to continue... Expected results: Fedora installation complete installed packages on host: kernel.ppc64le 5.10.11-100.fc32 qemu.ppc64le 2:4.2.1-1.fc32 Note that it is working fine on a P8 powerpc host with same kernel and qemu version.
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.