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):
Steps to Reproduce:
Boot a VM via PXE through a bridged interface:
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)
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
PXE booting bare metal machines on the same network works fine.
I believe this is a duplicate of bug:
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 ***