On Wed, Nov 27, 2013 at 02:37:02PM +0200, Laine Stump wrote: > Awhile back a bug was filed against libvirt about the inability to > completely exclude a disk from the boot order: > > https://bugzilla.redhat.com/show_bug.cgi?id=888635 > > In short, you can't have a domain that used PXE to boot, but also has an > un-bootable disk device *even if that disk isn't listed in the boot > order*, because if PXE times out (e.g. due to the bridge forwarding > delay), the BIOS will move on to the next target, which will 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 intervenes. > > It was obviously beyond the ability of libvirt to fix this (although it > can be worked around by creating a very small disk image with a > bootloader that merely instructs the system to reboot, and placing > *that* disk in the boot order just after the PXE device), so the BZ was > closed as CANTFIX. I'm fairly sure that the current behaviour we have is a regression vs the original libvirt QEMU driver prior to use of seabios. IOW, I think we should unconditionally be enabling strict=on to fix the flaw. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list