Package: efibootguard
Version: 0.22-1 and others
Severity: important
Dear Maintainer,
Hope you are doing well.
I'm using efibootguard (sid version) for booting the image on the QEMU arm64
target.
However I'm unable to boot the image and facing below issue.
Boot logs,
```
U-Boot 2023.01 (Mar 11 2026 - 18:51:49 +0900)
DRAM: 1 GiB
Core: 47 devices, 13 uclasses, devicetree: board
Flash: 64 MiB
Loading Environment from Flash... *** Warning - bad CRC, using default
environment
In: pl011@9000000
Out: pl011@9000000
Err: pl011@9000000
Net: e1000: 52:54:00:12:34:56
eth0: e1000#0
Hit any key to stop autoboot: 0
fatal: no kernel available
Command 'load' failed: Error 1
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
scanning bus for devices...
Device 0: unknown device
Device 0: QEMU VirtIO Block Device
Type: Hard Disk
Capacity: 16384.0 MB = 16.0 GB (33554432 x 512)
... is now current device
Scanning virtio 0:1...
load - load binary file from a filesystem
Usage:
load <interface> [<dev[:part]> [<addr> [<filename> [bytes [pos]]]]]
- Load binary file 'filename' from partition 'part' on device
type 'interface' instance 'dev' to address 'addr' in memory.
'bytes' gives the size to load in bytes.
If 'bytes' is 0 or omitted, the file is read until the end.
'pos' gives the file byte position to start reading from.
If 'pos' is 0 or omitted, the file is read from the start.
** Unable to read file ubootefi.var **
Failed to load EFI variables
Unable to find TPMv2 device
Missing RNG device for EFI_RNG_PROTOCOL
BootOrder not defined
EFI boot manager: Cannot load any image
Found EFI removable media binary efi/boot/bootaa64.efi
67643 bytes read in 39 ms (1.7 MiB/s)
Booting /efi\boot\bootaa64.efi
"Synchronous Abort" handler, esr 0x8a000000
elr: ffffffff80108343 lr : fffffffffde856f0 (reloc)
elr: 0000000000005343 lr : 000000007dd826f0
x0 : 0000000000005343 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 000000007edbb048
x4 : 0000000000007dfd x5 : 0000000007dfd000
x6 : 0000000000000007 x7 : 0000000000000009
x8 : 0000000000000002 x9 : 0000000000000004
x10: 0000000000000000 x11: 000000007dda5220
x12: 000000007dd92ea8 x13: 000000007dd8c4c0
x14: 000000007fefd000 x15: 000000007edbb020
x16: 000000007ff39d8c x17: 0000000000000000
x18: 0000000000000000 x19: 0000000000000000
x20: 000000007dd8cd70 x21: 000000007eef2270
x22: 000000007fefdb48 x23: 0000000000000002
x24: 000000007ffe5174 x25: 0000000000000000
x26: 0000000000000000 x27: 0000000000000000
x28: 000000007eef2110 x29: 000000007edbb080
Code: 9401ea98 a9425bf5 2a1303e0 a94153f3 (a94363f7)
UEFI image [0x000000007dd7c000:0x000000007dd935ed] '/efi\boot\bootaa64.efi'
Resetting CPU ...
resetting ...
```
The below command is used to boot the image,
```
qemu-system-aarch64 -machine virt -cpu max \
-m 1G -device virtio-blk-device,drive=disk \
-drive file=test.img,discard=unmap,if=none,id=disk,format=raw \
-device e1000,netdev=net0 -netdev
user,hostfwd=tcp:127.0.0.1:5555-:22,id=net0,hostfwd=tcp:127.0.0.1:2159-:2159 \
-bios u-boot.bin -nographic -serial mon:stdio
```
NOTE: This issue doesn't occur in the trixie efibootguard version, I've
confirmed this by downgrading the version(0.19-1) and the image boot works fine.
Could you please check the issue in Sid version and fix it?
Thanks & Regards
Shivanand K
