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:
When PXE booting, the firmware tries to fetch the kernel from tftp://0.0.0.0 rather than the IP address of the DHCP server.

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:
Boot a VM via PXE through a bridged interface:

  
Actual results:
DHCP (net0 52:54:00:56:4e:1f)................ ok
net0: 10.20.250.99/255.255.0.0 gw 10.2.0.1
Booting from filename "linux-install/pxelinux.0"
tftp://0.0.0.0/linux-install/pxelinux.0........ Connection timed out (0x4c106035)
Could not load tftp://0.0.0.0/linux-install/pxelinux.0: Connection timed out (0x4c106035)


Expected results:
Manually taking over the boot process:
gPXE> dhcp net0
DHCP (net0 52:54:00:56:4e:1f).... ok
gPXE> kernel tftp://10.20.10.1/linux-install/pxelinux.0
tftp://10.20.10.1/linux-install/pxelinux.0.. ok
gPXE>

Additional info:
PXE booting bare metal machines on the same network works fine.

I believe this is a duplicate of bug:
https://bugzilla.redhat.com/show_bug.cgi?id=586324

Setting DELAY=0 in the ifcfg config file solves the problem.

Can we close the bug?

I don't think this can be closed until either DELAY=0 is the default (possibly dangerous for non-VM related bridging) or it is well documented that DELAY=0 should be set in the bridge ifcfg file.

(In reply to comment #4)
> I don't think this can be closed until either DELAY=0 is the default (possibly
> dangerous for non-VM related bridging) or it is well documented that DELAY=0
> should be set in the bridge ifcfg file.

It is documented in the documentation guide on 10.2

At the very least this is a dupe of 632712

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