installer.py uses the wrong lorax template for the AArch64 architecture.

[jperrin]

I'm working to get CentOS-7 AArch64 builds of Atomic working. Everything works, with the exception of the grub config generated by the lorax bits in installer.py. It appears to use the grub2-efi template rather than the AArch64 template. This results in an unbootable system. With a corrected grub config, the system boots and runs atomic quite well.

[cgwalters]

This should likely be filed against rhinstaller/lorax or rhinstaller/anaconda - I don't see anything -toolbox specific here, we're just wrap lorax, right?

[jperrin]

I don't think this is a lorax issue, as it ships with a functional aarch64
template for the base distro. In this instance it seems the issue is with
the lorax template created inside the installer.py. since the lorax
template generated by rpm-ostree-toolbox doesn't include the aarch64 lorax
config, the resulting image is incorrect.

On Sep 27, 2016 14:01, "Colin Walters" notifications@github.com wrote:

This should likely be filed against rhinstaller/lorax or
rhinstaller/anaconda - I don't see anything -toolbox specific here, we're
just wrap lorax, right?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#102 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH8hAJVjAzyD_E8zE3LV5qWbQBP7GlfIks5quYQrgaJpZM4KHAhz
.

[cgwalters]

I think I need a shell 💻 🐚 on the system to debug this.

[jberkus]

How can we resolve this? I have an ARM64 Box loaded to me by ARM, and they would really like to see Atomic for ARM64 working.

[cgwalters]

I need more information - like build logs, and exactly what needed to be changed.

Also, presumably this is not an issue in current Fedora with pungi. So another path is to use Pungi for CentOS builds as well.

[jberkus]

@jperrin can you help?

[pcdubs]

This is still an issue in Fedora Rawhide, and reproducible using the latest iso to install (Fedora-Rawhide-20170718.n.0). The grub.cfg on the iso is correct, but the resulting installed system uses 'linuxefi/initrdefi' entries in grub.cfg, rather than aarch64 specific 'linux/initrd'.
The error is:
error: can't find command linuxefi'. error: can't find command initrdefi'.

Editing the grub.cfg and correcting to 'linux/initrd' the system boots as expected.

[cgwalters]

Ah. This sounds related to ostreedev/ostree#716

[cgwalters]

PR in ostreedev/ostree#1021 - if someone with an aarch64 machine could try it that'd be great, or just another set of eyeballs on it.