Cannot boot from EFI image on aarch64
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I am unable to boot from a EFI disk image on aarch64 qemu.
I have qemu built and installed from sources on a jetson-nano
qemu-system-aarch64 -version
QEMU emulator version 5.2.50 (v5.2.0-
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
KVM and and virtio are enabled in host kernel.
Now I want to boot a ChromiumOS image. I have the image downloaded from here:
https:/
The image looks fine:
rreddy78@
Disk chromiumos_
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C5B6CA94-
Device Start End Sectors Size Type
chromiumos_
chromiumos_
chromiumos_
chromiumos_
chromiumos_
chromiumos_
chromiumos_
chromiumos_
chromiumos_
chromiumos_
chromiumos_
chromiumos_
Partition table entries are not in disk order.
Now I try booting like this:
qemu-system-aarch64 -M virt -m 2048 -smp 2 -cpu host -enable-kvm \
-device usb-ehci -device usb-kbd -device usb-mouse -usb -serial stdio \
-device virtio-
-device virtio-
-drive if=none,
-netdev user,id=mynet \
-device virtio-
-bios edk2-aarch64-
But I am unable to boot.
Memory Type Information settings change.
[Bds]Booting UEFI Misc Device
BlockSize : 262144
LastBlock : FF
[Bds] Expand VenHw(93E34C7E-
BdsDxe: failed to load Boot0001 "UEFI Misc Device" from VenHw(93E34C7E-
and
[Bds] Expand VenHw(837DCA9E-
BdsDxe: failed to load Boot0002 "UEFI Misc Device 2" from VenHw(837DCA9E-
Changed in qemu: | |
status: | New → Invalid |
When i try to do it manually using the instructions provided here:
https:/ /mricher. fr/post/ boot-from- an-efi- shell/
I see that
Mapping table :HD0m:; BLK4:
VenHw( 837DCA9E- E874-4D82- B29A-23FE0E23D1 E2,003E000A0000 0000)/HD( 12,GPT, 49037CF8- B2EF-5B4B- 8CCE-EF5803A9E8 B3,0x3D000, 0x10000)
VenHw( 93E34C7E- B5
FS0: Alias(s)
BLK13: Alias(s):
BLK4 is not having any EFI file.