On 01/22/2014 12:45 PM, Daniel P. Berrange wrote:
On Wed, Jan 22, 2014 at 01:33:18AM +0100, Laszlo Ersek wrote:
Recently,
commit 96fddee322c7d39a57cfdc5e7be71326d597d30a Author: Laine Stump <laine@laine.org> Date: Mon Dec 2 14:07:12 2013 +0200
qemu: add "-boot strict" to commandline whenever possible
introduced a regression for OVMF guests. The symptoms and causes are described in patch 3/4, and in
https://bugzilla.redhat.com/show_bug.cgi?id=1056258
Let's allow users to opt-out of "-boot strict=on" while preserving it as default. I don't really get from that bug description why this can't be made to work as desired in OVMF. It seems like its is just a bug in the OVMF impl that it doesn't work.
I was on the verge of making that same comment in question form. From the information in the patches and the BZ, it sounds like either "--boot strict" is implemented incorrectly for OVMF, or OVMF doesn't do the proper thing with the "HALT". What does OVMF do with bootable devices that aren't given a specific boot order? For seabios, those devices are all on the boot list following those with specific orders; this is what necessitates --boot strict. The behavior of the option should be consistent regardless of BIOS choice.