A microvm guest booted with -kernel and -initrd and exactly 2 GiB of RAM
can fail to boot, as the initrd ends up on top of the ACPI tables and
other SeaBIOS data. With PCIe enabled, Linux then reports
"AE_NO_ACPI_TABLES" and finds no PCI devices, and kernels that probe
EDD hang. 2047 or 2049 MiB work fine. We hit this with Proxmox VE,
where 2 GiB is the default memory size. Patch 2 explains how microvm's
missing firmware data reservation and a heuristic in linuxboot_dma.bin
combine to cause this.

Patch 1 moves PC_FW_DATA to x86.h so that microvm can use it, patch 2
uses it.

Tested all combinations of TCG and KVM, the Debian 13 and Proxmox VE
kernels, Debian's and a minimal initrd, PCIe on and off, and 1024,
2047, 2048, 2049, 3072 and 4096 MiB of RAM, plus qboot with 2048 MiB.
Every boot found intact ACPI tables, started the initrd and – if the
kernel had the driver – found its virtio-blk disk.

Thomas Lamprecht (2):
  hw/i386: move PC_FW_DATA to x86.h as X86_FW_DATA
  hw/i386/microvm: reserve the firmware data area when loading Linux

 hw/i386/microvm.c     |  2 +-
 hw/i386/pc.c          | 14 ++------------
 include/hw/i386/x86.h | 10 ++++++++++
 3 files changed, 13 insertions(+), 13 deletions(-)


base-commit: f71afb409a87c4ecd0f9d63a5963eb645dfab780
-- 
2.47.3



Reply via email to