-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AARCH64 images for RHEL family #269
Comments
rhel9.pkr.hcl
PACKER_LOG=1 make ISO=/root/snap/firefox/common/Downloads/rhel-9.4-aarch64-dvd.iso
|
Manage to build the image with lots of modifications but post processing is now failing
KS script
fail log
need some help here |
This issue is stale because it has been open for 30 days with no activity. |
I'm running into the same issue with Rocky 9. @noama-nv, did you find a way to solve it? |
@noama-nv , I was able to build a Rocky 9 arm64 image with the changes on this diff: You just have to add changes for the efi partition eveywhere in the build process, which extends the work a bit more than expected. I hope this will help. However, as you know, this is still a work-in-progress due to the issue described here: Rocky 9 aarch64 deployment fails because of “grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot.” |
seems like you advance more then me, ill look into your changes and try it also i was not able to even build the image the finalize stage was failing |
This issue is stale because it has been open for 30 days with no activity. |
I used the changes in the diff above and was able to get RHEL 9.5 and Rocky 9 to build successfully. I'm currently looking into the issue from the discourse discussion as I hit the same grub2-efi error. The function below found in def gen_uefi_install_commands(grub_name, grub_target, grub_cmd, update_nvram, |
Hi,
im struggling building/adding support for AARCH64 images for RHEL family
I have access to ARM server and RHEL cloud/iso images
looking for some guidance/tips
The text was updated successfully, but these errors were encountered: