Bug 638735

Summary: unable to pxe boot a virtual machine without hitting ctrl-b
Product: [Fedora] Fedora Reporter: Michael Gregg <mgregg>
Component: qemuAssignee: Justin M. Forbes <jforbes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: amit.shah, berrange, dwmw2, ehabkost, francois, gcosta, itamar, jaswinder, jforbes, knoel, markmc, mhlavink, ondrejj, psj, scottt.tw, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-04 21:53:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Michael Gregg 2010-09-29 19:17:26 UTC
Description of problem:
When trying to pxe boot a vm, dhcp times out if I do not hit ctrl-b to break the boot sequence. 
This issue seems to be reported in: 
https://bugzilla.redhat.com/show_bug.cgi?id=472236

Version-Release number of selected component (if applicable):
qemu-0.12.5-1.fc13.x86_64
virt-manager-0.8.5-1.fc13.noarch

How reproducible:
most boots

Steps to Reproduce:
1. start virtual machine
2. when you are prompted to press CTRL-B do it
3. try to get dhcp address running this command: dhcp net0
4. repeat step 3 until you do not get address (reply "ok")
5. boot using command: autoboot
  
Actual results:
dhcp fails on most boots

Comment 1 Jan ONDREJ 2010-09-30 04:46:12 UTC
Same problem here.

I have an better workaround. Instead of typing so many characters, try to select from virt-manager menu Send Key -> Ctrl Alt Delete.

You can do this aprox. 2-3 seconds after guest was started, do not need to wait for DHCP timeout.

I think component should be changed to gpxe, because it looks that gpxe DHCP timeout should be increased by 3 seconds to fix this problem.

Comment 2 Michael Gregg 2010-10-05 22:53:51 UTC
I discovered that if I lower the bridge forward delay to 5 sec, pxe booting starts working again.

Set it with:
brctl setfd br0 5

Comment 3 Jan ONDREJ 2010-10-06 06:21:40 UTC
(In reply to comment #2)
> I discovered that if I lower the bridge forward delay to 5 sec, pxe booting
> starts working again.
> 
> Set it with:
> brctl setfd br0 5

I can confirm this on my system.

Comment 4 Paul Jenner 2011-03-04 21:26:09 UTC
So this is a duplicate of bug #586324 - DHCP fails for bridges with long forward delay

Comment 5 Michael Gregg 2011-03-04 21:51:41 UTC
that's correct. I'll make this bug a duplicate.

Comment 6 Michael Gregg 2011-03-04 21:53:30 UTC
Again, for clarification, the work-around seems to be running:

brctl setfd <bridge device> 3 

This bug now marked as duplicate of #586324

*** This bug has been marked as a duplicate of bug 586324 ***