Closed merlinscholz closed 1 year ago
Is this specific to archlinux?
So far I've tried Fedora, Alma, Ubuntu, Debian and Rocky, the issue only appeared in Arch. I'll update when I find another problematic OS.
The only relevant detail that makes Arch stand out is that they - as only OS - do not use Grub by default in their cloud images, but rather boot the EFI-compatible kernel directly via EFISTUB
I suppose this issue is dup of #858. Author of arch-aarch64 image has described the root cause.
IMHO the reason of such issue is archlinux and archlinux-arm are two separated project. Currently archlinux-arm doesn't provide OS image, so some contributors stand out and build one(work appreciated).
It's not easy for an individual contributor to actively maintain a project. I personally switched to ubuntu instead.
Description
Hello, when creating a Lima machine via...
limactl start --name=default template://archlinux
...on an aarch64 host, the boot process is extremely slow. Inspecting the boot log reveals that QEMU is trying to boot from PXE (both IPv4 and IPv6), and HTTP (again IPv4 and IPv6) after that. Since none of those options will work, there are 4 additional timeouts to wait for before booting the actual VM.
Furthermore, a 5 second delay from
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
during the UEFI boot is being added.Are those intended as some kind of fallback options or is this due to a missing QEMU boot configuration? In the boot logs there's also some info on a missing "UEFI Misc device" with a seemingly unique ID, maybe the whole PXE/HTTP stuff is being tried because that device cannot be found properly?
serial.log
:After that, the expected Linux boot begins.
limactl info
: