On Wed, 2017-03-08 at 18:57 +0100, Laszlo Ersek wrote: > On 03/08/17 18:12, Daniel P. Berrange wrote: > > The scenario I was actually thinking of was direct kernel boot, > > rather than non-AAVMF impls of UEFI. > > > > IOW, where you just pass -kernel/-initrd/-dtb to QEMU and no firmware > > file. In that case, we should report an error if <acpi/> is requested > > in the XML IIUC. > > Direct kernel boot without UEFI firmware should indeed conflict with > <acpi/>, yes; there's no firmware to install the tables for the kernel. > > Direct kernel boot with UEFI firmware should permit <acpi/>. The > firmware starts, does its thing (including installation of ACPI tables), > then grabs the kernel from fw_cfg, and launches it. The kernel will see > the tables. Gotcha. The non-RFC version of the series, which I just posted to the list, should handle those configurations as well. -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
