Package: qemu-efi-aarch64
Version: 2025.02-8
Severity: normal

Dear Maintainer,

I'm using AAVMF for booting the arm64 images on QEMU, However I'm facing below 
issue,

UEFI firmware (version 2025.02-8 built at 02:18:11 on May 13 2025)
BdsDxe: loading Boot0001 "UEFI QEMU QEMU HARDDISK " from 
PciRoot(0x0)/Pci(0x1,0x0)/Scsi(0x0,0x0)
BdsDxe: starting Boot0001 "UEFI QEMU QEMU HARDDISK " from 
PciRoot(0x0)/Pci(0x1,0x0)/Scsi(0x0,0x0)
EFI Boot Guard v0.19
Boot medium: PciRoot(0)/Pci(0x1,0x0)/Scsi(0,0)
Found 3 handles for file IO

Volume 0: (On boot medium) 
PciRoot(0)/Pci(0x1,0x0)/Scsi(0,0)/HD(1,GPT,4D76DB0B-E899-41B8-9A7F-55037757AC51),
 LABEL=EFI, CLABEL=(null)
Volume 1: (On boot medium) 
PciRoot(0)/Pci(0x1,0x0)/Scsi(0,0)/HD(2,GPT,88FB226D-ED8F-43A1-B432-664AA7758071),
 LABEL=BOOT0, CLABEL=BOOT0
Volume 2: (On boot medium) 
PciRoot(0)/Pci(0x1,0x0)/Scsi(0,0)/HD(3,GPT,50191EE5-9914-4B20-ACE5-62FBE9595F72),
 LABEL=BOOT1, CLABEL=BOOT1
Loading configuration...
Config file found on volume 1.
Config file found on volume 2.
Booting with environments from boot medium only.
2 config partitions detected.
Config Revision: 1:
ustate: 0
kernel: C:BOOT0:unified-linux.efi
args:
timeout: 0 seconds
Full path for kernel is: 
PciRoot(0)/Pci(0x1,0x0)/Scsi(0,0)/HD(2,GPT,88FB226D-ED8F-43A1-B432-664AA7758071)/unified-linux.efi
LoaderDevicePartUUID=4D76DB0B-E899-41B8-9A7F-55037757AC51
Starting C:BOOT0:unified-linux.efi with watchdog set to 0 seconds ...
Unified kernel stub (EFI Boot Guard v0.19)

Synchronous Exception at 0x000000007DE0F334

Synchronous Exception at 0x000000007DE0F334


QEMU command:

qemu-system-aarch64 \
        -machine virt \
        -cpu cortex-a53 \
        -m 1G \
        -device virtio-scsi-pci \
        -device scsi-hd,drive=hd0 \
        -blockdev driver=file,node-name=hd0,filename=<image-file> \
        -device e1000,netdev=net0 \
        -netdev 
user,hostfwd=tcp:127.0.0.1:5555-:22,id=net0,hostfwd=tcp:127.0.0.1:2159-:2159 \
        -drive 
if=pflash,format=raw,unit=0,readonly=on,file=/usr/share/AAVMF/AAVMF_CODE.fd \
        -nographic -serial mon:stdio

Note: The kernel is unified kernel image(UKI) and also I used efibootguard[1] 
for preparing UKI and booting the image as well.
Also, I won't see the above issue if I use the bookworm's qemu-efi-aarch64 
(2022.11-6+deb12u2) package.

[1] https://packages.debian.org/trixie/efibootguard

Thanks & Regards
Shivanand K

Reply via email to