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
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.
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
(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.
So this is a duplicate of bug #586324 - DHCP fails for bridges with long forward delay
that's correct. I'll make this bug a duplicate.
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 ***