Re: [Xen-devel] UEFI Boot Order Not Respected

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

On Wed, Mar 13, 2019 at 03:31:08PM -0600, Tomasz Tuzel wrote:
> Hi everyone,

Hi,

> We've been running into an issue with boot ordering when using OVMF
> (specifically, with PXE booting). In particular, the issue is the "-boot
> order=ABC" seems to have variable behavior depending on what it receives.
> This is only an issue with UEFI; legacy handles this condition correctly.
> Here's a table documenting several combinations in the HVM guest
> configuration:
[snip]
> My running suspicion
> is that the fw_cfg file is being incorrectly configured. However, I do not

Well, fw_cfg isn't configured at all when running Xen, so I don't think
-boot order=X can work.

I guess, to make -boot order works, we would need to enable fw_cfg in
QEMU and only provide the boot order, then check that OVMF can read it.

With Xen, fw_cfg is used in one case, it's when "direct kernel boot" is
used on HVM, with the legacy BIOS. So I guess that could work as well
for boot order, and hopefully without breacking SeaBIOS.

> see what is typically cited as a problem in the QEMU invocation that is
> being tested on our end, namely the conflicting usage of "-boot order=ABC"
> and "-device XYZ,bootindex=N". I don't really see any chatter about this on
> any of the mailing lists that I've dug through, but it was just last week
> that a fix was posted for the issue in which the hvmloader firmware leaves
> address decoding enabled for enumerated PCI devices. Thus, I'm wondering if
> this has simply not shown up on anyone's radar yet. Is this is a known
> issue?

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel