sinnykumari added a new comment to an issue you are following:
``
Update:
I have succeeded in creating FAH CloudImage on aarch64 using imagefactory on local
machine. Image gets generated successfully when we use reqpart in fedora-atomic kickstart
file.
There are two issues while booting generated cloudImage on aarch64:
1. "can't find command linuxefi, can't find command initrdefi" .
Modifying kernel boot parameter from linuxefi to linux and initrdefi to initrd fixes this
problem. This problem has been fixed here
https://github.com/ostreedev/ostree/pull/1021
.
sweet - are we testing this with rawhide or f26?
In rawhide
After changes made as stated in 1st issue, booting gets stuck with
following messages:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
It seems to be a problem with console option passed in fedora-atomic kickstart file at
https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_20 . It seems, arm
devices uses console=ttyAMA0. Either adding console=ttyAMA0 in line#20 or removing
console=tty1 console=ttyS0,115200n8 fixes the problem.
I wish i would have known you were debugging this :) - I hit this same problem a few
months ago:
https://twitter.com/dustymabe/status/867225301985755137. I guess we need to
find a way to specify that to just the aarch64 images.
Yeah! I started debugging around 2 weeks back on aarch64, just after getting ppc64le
issues sorted out (mentioned in the main ticket)
With above two problem fixed, aarch64 image boots successfully.
🎉 have we tried with any other architectures?
In what context? If you mean building and booting FAH cloudImage (qcow2) in rawhide, then
x86_64 already exist in nightly compose. Other than that, I have tried on ppc64le locally
and it should work once initial issues mentioned in this ticket get resolved.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/299