View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000269 | AlmaLinux-8 | systemd | public | 2022-06-22 06:08 | 2022-06-22 19:46 |
| Reporter | bogen85 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | aarch64 | OS | Almalinux | OS Version | 8 |
| Summary | 0000269: bootctl (systemd-boot) inconsistency | ||||
| Description | This could be a RHEL issue? AlmaLinux 8 has bootctl on aarch64, AlmaLinux 9 does not. AlmaLinux 9 might not have it due to this: 2021-10-12 - systemd maintenance team <systemd-maint@redhat.com> - 249-8 - boot: don't build bootctl when -Dgnu-efi=false is set (#2003130) Both have bootctl on x86_64. Anyways, this is twofold: 1) AlmaLinux 9 is missing bootctl on aarch64 2) AlmaLinux 8 bootctl installs an efi loader that crashes parallels on the Apple M1. | ||||
| Steps To Reproduce | On an Apple M1 macbook with the parallels $ prlctl --version prlctl version 17.1.4 (51567) Create partition at least 64MiB as type EF00 format it as fat32: mkfs.vfat -F32 -n EFI-BOOT /dev/sdXY mount it on /boot: mount /dev/sdXY /boot install systemd-boot efi loader: bootctl install reboot results (on aarch64) on Fedora 34: systemd-boot menu is present, can go into firmware on Fedora 35: systemd-boot menu is present, can go into firmware on Fedora 36: systemd-boot menu is present, can go into firmware AlmaLinux 8: parallels crashes and wants to send a bug report AlmaLinux 9: could not test as bootctl is missing results (on x86_64) on Fedora 35: systemd-boot menu is present, can go into firmware on Fedora 36: systemd-boot menu is present, can go into firmware AlmaLinux 8: systemd-boot menu is present, can go into firmware AlmaLinux 9: systemd-boot menu is present, can go into firmware | ||||
| Tags | No tags attached. | ||||
| abrt_hash | |||||
| URL | |||||
|
|
ArchLinux aarch64 on the Apple M1 macbook in parallels passes the above test. $ bootctl --version systemd 251 (251.2-1-arch) |
|
|
on each of the above tests I did sync and unmount /boot before rebooting. |
|
|
secure boot is not enabled for this |
|
|
fedora 34 bootctl (systemd) version 248 (v248.10-1.fc34) fedora 35 bootctl (systemd) version 249 (v249.12-5.fc35) fedora 36 bootctl (systemd) version 250 (v250.7-1.fc36) almalinux 8 bootctl (systemd) version 239 (v239-58.el8) --------- For Fedora 35-36 I used https://getfedora.org/en/workstation/download/ for each release For AlmaLinux (x86_64 and aarch64) I used arch-chroot from arch-install-scripts on the Fedora 36 livecd and the 8 or 9 AlmaLinux default rootfs from https://us.lxd.images.canonical.com/images/almalinux/ (refreshed and upgraded before proceeding, but those are already up to date when downloaded fresh) |
|
|
oh, I see bootctl is on AlmaLinux 9 aarch64 $ dnf provides bootctl Last metadata expiration check: 18:19:30 ago on Tue 21 Jun 2022 02:20:16 PM CDT. systemd-boot-250.3-1.el9.aarch64 : Simple UEFI boot manager to execute configured EFI images Repo : epel Matched from: Filename : /usr/bin/bootctl I will try it. |
|
|
On AlmaLinux 9 x86_64 and aarch64: $ dnf provides bootctl systemd-boot-250.3-1.el9.x86_64 : Simple UEFI boot manager to execute configured EFI images Repo : @System Matched from: Filename : /usr/bin/bootctl systemd-boot-250.3-1.el9.x86_64 : Simple UEFI boot manager to execute configured EFI images Repo : epel Matched from: Filename : /usr/bin/bootctl All my AlmaLinux installs (8 and 9) on X86_64 use systemd-boot. They work fine. ----------- bootctl on AlmaLinux9 aarch64 works fine. |
|
|
So, the only inconsistency is that the systemd-boot on AlmaLinux 8 is older (239) than the bootctl on all the other releases I tried (248, 249, 250) and while 239 works on x86_64, it does not work on Apple aarch64 M1 in parallels. systemd-boot 248, 249, 250 all work on x86_64 (non parallels, not on an Apple machine) and on Apple aarch64 M1 (parallels) |
|
|
My AlmaLinux 8 and 9 installs on x86_64 are all custom and semi-automated via scripts. I guess I missed noting the bootctl coming from EPEL 9 for AlmaLinux 9 as EPEL was already enabled before that, and when bootctl was missing I must have done a "dnf provides boot" and adding systemd-boot to an earlier package list. Oh well. So the only issue here is systemd-boot not working with AlmaLinux 8 on aarch64 Apple M1 in parallels, but working everywhere else in the above scenarios. |
|
|
Looks like centos-8-stream bootctl is the same version as that in AlmaLinux 8. I will try with centos-8-stream as well... [root@rootfs-centos-8-stream ~]# bootctl --version systemd 239 (239-58.el8) |
|
|
Also crashes with centos-8 stream the same way it does with AlmaLinux 8 bootctl --version systemd 239 (239-58.el8) So this is issue is not specific to AlmaLinux. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-06-22 06:08 | bogen85 | New Issue | |
| 2022-06-22 06:11 | bogen85 | Note Added: 0000602 | |
| 2022-06-22 06:20 | bogen85 | Note Added: 0000603 | |
| 2022-06-22 12:33 | bogen85 | Note Added: 0000604 | |
| 2022-06-22 13:31 | bogen85 | Note Added: 0000605 | |
| 2022-06-22 13:44 | bogen85 | Note Added: 0000606 | |
| 2022-06-22 13:58 | bogen85 | Note Added: 0000607 | |
| 2022-06-22 14:03 | bogen85 | Note Added: 0000608 | |
| 2022-06-22 14:27 | bogen85 | Note Added: 0000609 | |
| 2022-06-22 15:14 | bogen85 | Note Added: 0000610 | |
| 2022-06-22 19:46 | bogen85 | Note Added: 0000611 |
