Description of problem: There is a bug [1] (VM will reboot if no boot failed). As said in [2], we need to add a new boot parameter and put it into romfile for seabios to use, it's used to configure the delay time. This work should start on upstream. [1] Bug 831273 - RFE: reboot VM if no bootable device found [2] https://bugzilla.redhat.com/show_bug.cgi?id=831273#c18
patch posted to upstream: http://patchwork.ozlabs.org/patch/182306/ example: -boot reboot-timeout=10000 With this option, guest will wait for a given time if not find bootabled device, then reboot. If reboot-timeout is '-1', guest will not reboot, qemu passes '-1' to bios by default.
Hi Eric, If customer wants to use this 'feature'[1], do we need to change libvirt/virt-manager/etc to use this qemu parameter? [1] Bug 831273 - RFE: reboot VM if no bootable device found Thanks, Amos
(In reply to comment #2) > Hi Eric, > > If customer wants to use this 'feature'[1], do we need to change > libvirt/virt-manager/etc to use this qemu parameter? Yes; libvirt probably needs to enhance XML to support this; I cloned bug 855237 to track it. (You can use the unsupported <qemu:commandline> XML to trigger it in the meantime while waiting for official libvirt support.)
verify this issue with qemu-kvm-0.12.1.2-2.329 and seabios-0.6.1.2-25 testing three scenarios: 1. <=1 seconds boot guest with -boot reboot-timeout=1000 No boottable device. Retrying in (0)1 seconds. 2. >65seconds boot guest with -boot reboot-timeout=1000000 No boottable device. Retrying in 65 seconds. 3. default value boot guest with -boot reboot-timeout=-1 guest not reboot,and always show "No bootable device. since qemu max support reboot-timeout effective value is 65 second(work as design). so base on this result above, this bug is fixed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0527.html