Description of problem:
If the VM NIC is virtio based, PXE boot fails. e1000 works OK, though.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create an empty VM, set RHEL6 as the VM type
2. Try to PXE boot via a bridged interface
gPXE> dhcp net0
DHCP (net0 52:54:00:56:4e:1f)................ Connection timed out (0x4c106035)
Could not configure net0: Connection timed out (0x4c106035)
However, setting it to e1000:
gPXE> dhcp net0
DHCP (net0 52:54:00:56:4e:1f)................ ok
Should work for both virtio and emulated NICs.
Is this bug related to bug 632716?
I don't think they are related per se. This is about DHCP failing. https://bugzilla.redhat.com/show_bug.cgi?id=632716 is about the tftp boot failing. This is lower level than that.
(In reply to comment #3)
> I don't think they are related per se. This is about DHCP failing.
> https://bugzilla.redhat.com/show_bug.cgi?id=632716 is about the tftp boot
> failing. This is lower level than that.
Ah, I see now. This is due to the bridge delay. Glauber, Dan, any ideas how to resolve this?
There's not enough information here really.
Please provide the full libvirt XML for the guest, and the corresponding /var/log/libvirt/qemu/$GUEST.log file
Also provide info on the host networking setup from
brctl showstp $BRIDGENAME
sysctl -a | grep ip_forward
iptables -L -n -v
iptables -t nat -L -n -v
Finally what libvirt RPM version is present.
Is this a duplicate of bug #586324?
Yes, it looks like it is!
Setting DELAY=0 in the ifcfg-br0 config file solves the problem.
Closed as a dup per previous comments.
*** This bug has been marked as a duplicate of bug 586324 ***
Oops other bug is a Fedora bug. Will leave this RHEL bug assigned.
*** Bug 632716 has been marked as a duplicate of this bug. ***