]> git.ipfire.org Git - thirdparty/libvirt.git/commit
qemu: add "-boot strict" to commandline whenever possible
authorLaine Stump <laine@laine.org>
Mon, 2 Dec 2013 12:07:12 +0000 (14:07 +0200)
committerLaine Stump <laine@laine.org>
Tue, 3 Dec 2013 09:58:26 +0000 (11:58 +0200)
commit96fddee322c7d39a57cfdc5e7be71326d597d30a
tree054b7da5434b19b3cbdb572428e6802811ece429
parent47b9aae0ae0652738d3a65d6cdd6b0bb16b3a2ec
qemu: add "-boot strict" to commandline whenever possible

This resolves:

  https://bugzilla.redhat.com/show_bug.cgi?id=888635

(which was already closed as CANTFIX because the qemu "-boot strict"
commandline option wasn't available at the time).

Problem: you couldn't have a domain that used PXE to boot, but also
had an un-bootable disk device *even if that disk wasn't listed in the
boot order*, because if PXE timed out (e.g. due to the bridge
forwarding delay), the BIOS would move on to the next target, which
would be the unbootable disk device (again - even though it wasn't
given a boot order), and get stuck at a "BOOT DISK FAILURE, PRESS ANY
KEY" message until a user intervened.

The solution available since sometime around QEMU 1.5, is to add
"-boot strict=on" to *every* qemu command. When this is done, if any
devices have a boot order specified, then QEMU will *only* attempt to
boot from those devices that have an explicit boot order, ignoring the
rest.
src/qemu/qemu_capabilities.c
src/qemu/qemu_capabilities.h
src/qemu/qemu_command.c
tests/qemucapabilitiesdata/caps_1.5.3-1.caps
tests/qemucapabilitiesdata/caps_1.6.0-1.caps
tests/qemucapabilitiesdata/caps_1.6.50-1.caps
tests/qemuxml2argvtest.c