Arm64 (armvirt64) uefi (efi) OpenWrt target

Sorry for wasting your time... And sorry for my poor English.
All I do in Ubuntu 20.04 TLS @ intel PC.
qemu-aarch64 version 4.2.1 (Debian 1:4.2-3ubuntu6.10)
I need to run Openwrt as ESXi-arm64 guest VM.
I trying to boot at: QEMU, ESXi, rpi4-UEFI.
And all this three times I get the same.

EFI stub: Booting Linux Kernel...
EFI stub: Generating empty DTB
EFI stub: Exiting boot services and installing virtual address map...

So, I think there no difference where to test (as I see yet).
If you send me a working initramfs image, I test it and tell you where it boots in my 3 cases.
This will clear the "bad-testing" thinking.

1 Like

this is totally vague and not an openwrt issue...

no information provided about all of the fundamental properties required at boot time... ( drives, filesystems, blobs, dts location etc. etc. )

i've provided a functional example on QEMU... if you are having issues with specific VENDOR hypervisor stacks ( and are not able to articulate or troubleshoot at the necessary levels ) then I suggest you take it up with their support channels...

Can you send me your working initramfs-image please, please, please? And if it boots it's an Openwrt issue. May be it will boots all three hosts. I believe ) Ii it boot even ones, I am going forward, if not - it's a stuck.



And now it boots fine and working in KVM !

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd070]
[    0.000000] Linux version 5.4.83 (ubuntu@fit) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r15241-3ab695368a)) #0 SMP Fri Dec 18 22:05:50 2020
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: EFI v2.70 by EDK II
[    0.000000] efi:  SMBIOS 3.0=0x7bef0000  MEMATTR=0x7aa05518  ACPI 2.0=0x78520000  MEMRESERVE=0x7850f018 
[    0.000000] ACPI: Early table checksum verification disabled
[    0.000000] ACPI: RSDP 0x0000000078520000 000024 (v02 BOCHS )
[    0.000000] ACPI: XSDT 0x0000000078510000 00004C (v01 BOCHS  BXPCFACP 00000001      01000013)
[    0.000000] ACPI: FACP 0x00000000784D0000 00010C (v05 BOCHS  BXPCFACP 00000001 BXPC 00000001)
[    0.000000] ACPI: DSDT 0x00000000784E0000 004842 (v02 BOCHS  BXPCDSDT 00000001 BXPC 00000001)
[    0.000000] ACPI: APIC 0x00000000784C0000 0000F4 (v03 BOCHS  BXPCAPIC 00000001 BXPC 00000001)
[    0.000000] ACPI: GTDT 0x00000000784B0000 000060 (v02 BOCHS  BXPCGTDT 00000001 BXPC 00000001)
[    0.000000] ACPI: MCFG 0x00000000784A0000 00003C (v01 BOCHS  BXPCMCFG 00000001 BXPC 00000001)
[    0.000000] ACPI: SPCR 0x0000000078490000 000050 (v02 BOCHS  BXPCSPCR 00000001 BXPC 00000001)
[    0.000000] ACPI: SPCR: console: pl011,mmio,0x9000000,9600
[    0.000000] psci: probing for conduit method from ACPI.
[    0.000000] psci: PSCIv0.2 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] percpu: Embedded 20 pages/cpu s44696 r8192 d29032 u81920
[    0.000000] Detected PIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 832075
[    0.000000] CPU features: detected: EL2 vector hardening
[    0.000000] ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware

but it NOT boots on ESXi or rpi4. :frowning:

Is it possible and a good idea to run Debian as a vm on RasberryPi4 Openwrt host? Is qemu in Openwrt working?


I've put this together and it's working on Pi 4 8GB (ESXi-Arm Fling), Includes EFI stub/GrubEFI Welcome to try it


It works!!! It's works so fine and fast so I am happy. Installed luci - It's flying! Kernel modules installs also fine! Network ping <1ms! It's a really working OpenWrt 19.07.5 release for arm64 ESXi ! Thanks statto99!
So, it would be nice to see a release like this in the download list (make it publicly available now and forever). It's very cool that some problems are being solved in real life!
It seems, it works faster than native on this rpi!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.