RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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):
qemu-kvm-0.12.1.2-2.90.el6.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Create an empty VM, set RHEL6 as the VM type
2. Try to PXE boot via a bridged interface
  
Actual results:
For virtion:
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
gPXE>


Expected results:
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

  ifconfig -a
  brctl show
  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. ***