This seems like a problem with kernel/initrd to me. Could you please verify that you are booting with correct vmlinuz initrd and stage2 image from the same ISO build?

Hi,Not very sure if I understand correctly,here is the console output from the *successful* Ampere installation with the same beaker repo,
https://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2020/04/41843/4184384/8113116/console.log

Did this work with Fedora-32-20200404.n.0(kernel-5.6.0-300.fc32)? I noticed a passing test result in the Fedora wiki.

I think you need iommu.passthrough=1 and arm-smmu.disable_bypass=n on those machines.

(In reply to Paul Whalen from comment #3)
> Did this work with Fedora-32-20200404.n.0(kernel-5.6.0-300.fc32)? I noticed
> a passing test result in the Fedora wiki.

Nope,the passing test result is for Ampere(HR350A 7X35CTO1WW),didn't get a Gigabyte server to test Fedora-32-20200404.n.0(kernel-5.6.0-300.fc32).

(In reply to Mark Salter from comment #4)
> I think you need iommu.passthrough=1 and arm-smmu.disable_bypass=n on those
> machines.

Thanks for your information,after adding that line, f32 can be installed successfully on the Gigabyte server,but the installed system stucks there after reboot:
https://beaker.engineering.redhat.com/recipes/8120356/logs/console.log (https://beaker.engineering.redhat.com/recipes/8120356#installation)
Assuming that 'iommu.passthrough=1 arm-smmu.disable_bypass=n' isn't in /etc/default/grub (though it has been added successfully to /etc/default/grub on f31 installation),
I put the following to kickstart %post,
sed -i -e 's/^GRUB_CMDLINE_LINUX=\"/GRUB_CMDLINE_LINUX=\"iommu.passthrough=1 arm-smmu.disable_bypass=n/'  /etc/default/grub
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

But doesn't work，http://lab-02.rhts.eng.bos.redhat.com/beaker/logs/recipes/8120+/8120784/console.log(https://beaker.engineering.redhat.com/recipes/8120784#installation）

FYI,F31 can be installed and rebooted successfully on Gigabyte (R120-T34) http://lab-02.rhts.eng.bos.redhat.com/beaker/logs/recipes/8120+/8120457/console.log

I just found out that :
1. beaker adds "iommu.passthrough=1 arm-smmu.disable_bypass=n" automatically to f31 installation on Gigabyte and installations on Ampere(HR350A 7X35CTO1WW)
2.Cavium(ThunderX2 Sabre) works well without that line:http://lab-02.rhts.eng.bos.redhat.com/beaker/logs/recipes/8120+/8120665/console.log

Hi,sorry for the wrong put,I forgot add a ' 'to the sed command.but I still feel a little confused,rhel8 works well on Gigabyte server without“iommu.passthrough=1 arm-smmu.disable_bypass=n”

Er,now I know the reason:adding "iommu.passthrough=1 arm-smmu.disable_bypass=n" is a workaround for an issue introduced in kernel 5.2,while RHEL8 has kernel4.18.
And the reason why Cavium(ThunderX2 Sabre) doesn't need that workaround is it takes SMMUv3 
Anyway,this is an issue of Arm,not NVme.Just to make sure,I've also checked an aarch64 server without NVMe,also affected by this issue.

Based on comment 8 and comment 7 can we close this bug or is there something else needs to be done from the Anaconda side?

This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.