Description of problem: Almost impossible to get into safe mode or RHEL sea bios. For migration: You **need** to hit F8 during boot and go into safe mode to get drivers right, and remove associations to none existent nics otherwise you can not allocate IP number to new nic created by RHEL. Windows server 2003 and 2008 does this to prevent IP conflicts. However, by the time vnc or spice initializes it's too late to hit F8 windows is already booting. need to be able to add delay before hard disk boot. when searching access.redhat.com documentation for custom properties unable to find that option. Only able to start vm paused, but this is almost too fast to catch it as well, takes a few tries. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization 3.0 Microsoft Exchange server 2003 64 bit rhel-6.3-p2v.iso How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
any libivrt flag allowing to control the time the bios screen will be display?
AFAIK, that's not a value qemu permits to be controlled. Ademar, can you confirm?
You can use "-boot menu=on" to display a boot menu for 5 seconds (from SeaBIOS), or use a splash screen and define the timeout: # 10 secs splash screen qemu -boot menu=on,splash=/root/boot.bmp,splash-time=10000 (not tested)
Ok, thanks; there isn't libvirt support for that parameter, but it would be easy to add it.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
There are 2 issues here: 1. A P2V issue with Windows conversion and NICs. 2. A UI issue hitting F8 on RHEV Windows guests. The first already has a open bug. The second isn't related to P2V. I'm going to move this over to RHEV to track the second issue.
dave - any libvirt bug to track comment 3 to block this BZ?
(In reply to Itamar Heim from comment #8) > dave - any libvirt bug to track comment 3 to block this BZ? I've cloned it to 1021703.
looks we need bug 1047624 as well at the same time
Is this as simple as adding <bootmenu enable='yes'/> as a config option
(In reply to Michal Skrivanek from comment #10) > looks we need bug 1047624 as well at the same time agree - just read it - I think we can close duplicate.
I'd go with 5s when the menu is enabled. If one needs more time on initial boot there is the "Start in Paused mode" checkbox changing title to match the ovirt bug, keeping it to track the downstream feature
upstream code is merged
Verified in upstream. Inserting verification info (from bug 1047624 comment 5): > Verified in ovirt-engine-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch (beta2). > > Verification steps: > 1. Create a VM with Boot Options -> "Enable boot menu" checked. > 2. Start VM (to "catch" the default 5 seconds timeout, it helps to run the VM in paused mode). > 3. Open VM console right after the VM is started. > > Results: > After initial SeaBIOS and gPXE driver initialization, message "Press F12 for boot menu." appears. After pressing F12, boot device menu is displayed and waits for user input, see attached screenshot.
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. https://rhn.redhat.com/errata/RHSA-2015-0158.html