mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-25 07:05:28 +00:00
96fddee322
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. |
||
|---|---|---|
| .. | ||
| caps_1.2.2-1.caps | ||
| caps_1.2.2-1.replies | ||
| caps_1.3.1-1.caps | ||
| caps_1.3.1-1.replies | ||
| caps_1.4.2-1.caps | ||
| caps_1.4.2-1.replies | ||
| caps_1.5.3-1.caps | ||
| caps_1.5.3-1.replies | ||
| caps_1.6.0-1.caps | ||
| caps_1.6.0-1.replies | ||
| caps_1.6.50-1.caps | ||
| caps_1.6.50-1.replies | ||