Hi, > > > # - specify a firmware and pass a hint to the kernel to boot > > > # - direct kernel image boot > > > > That is a technical detail which doesn't make much of a difference > > from the end user perspective. And often people talk about "direct > > kernel boot" without drawing a line between these two cases, because the > > user-visible behavior is pretty much identical: You pass a kernel to > > qemu via '-kernel', and it gets booted ... > > As an end user I find them majorly different -- I usually > don't want the firmware, because it takes forever to boot > if you do that.
Not sure what exactly you are doing, but for me edk2 is done in less than a second (unless I turn on firmware debug logging), and that on a rpi4 host which isn't exactly fast hardware. I wouldn't call that "forever". > This is probably partly an x86 vs Arm difference: for x86 there > is always some kind of BIOS booted, but for Arm there > by default is not, and direct kernel boot is much more > common. Yes, on x86 you need something (be it ovmf or seabios or qboot) which places smbios and acpi tables properly in guest memory. On arm the linux kernel is happy with the device tree, so it is possible to skip the firmware part (unless you want run the guest in acpi=on mode). take care, Gerd
