Unable to boot Fog from PXE
-
Thanks for the quick reply.
I tried to check the error but its so fast switching the screen , that i am able to see it.
-
@swaroop because you’re on centos 7, is selinux running? What about a firewall?
-
Both selinux and firewall is disable .
-
so you never see the iPXE part, just PXE then system booting?
-
Hi
Now i tried with virtual box server and i found that after getting the IP from DHCP Sever , it shows an error " DCHP failed hit “s” for the ipxe shell.
-
@swaroop The failed part is because it’s hitting the menu, but not exiting to boot to the first device yet.
Is it more likely your server timeout for pxe is just too short?
-
@Tom-Elliott No
-
@swaroop What is the PXE Menu timeout set to?
-
@Tom-Elliott i didn’t set it till now. can you please help to do that.
-
@swaroop Help do what?
-
-
@swaroop FOG Configuration Page->iPXE Boot Menu->Menu Timeout (in seconds):*
-
@Tom-Elliott Thanks …Now i am getting the below error.
image url) -
@swaroop https://forums.fogproject.org/topic/4862/ipxe-error-no-configuration-methods-succeeded/2
Can you ensure the network cable is good please? Either that or, if this is a VM make sure it’s not a natted connection, but a bridged one.
-
??? I know its late but, why am I seeing two different ipxe kernels running?
I looks like one ipxe kernel is chain loading to undionly.kpxe. And its the second kernel that is not picking up a dhcp address. Are we loading and older pxelinux.0 that is chainloading to a fog version of unidonly.kpxe? It makes me think that there is some old dhcp settings with a DHCP Proxy somewhere.
-
@george1421 Just my guess, this particular VM is virtual box.
-
@george1421 said:
I know its late but, why am I seeing two different ipxe kernels running?
Yes, Tom is right I think. Virtualbox is definitely using iPXE as PXE ROM. That’s why you see iPXE chainloading iPXE…
@swaroop Interesting that the first iPXE is able to get an IP via DHCP but the second is not. Can you please enable network tracing for this VM and upload the PCAP file to the forum here.
-
@Tom-Elliott Thanks a lot … it worked …
: -
@swaroop What exactly did you change? Please let us know so other users will find this when running into the same problem!!
-
@Sebastian-Roth as Tom guide me to remove that NATTED connection and only keep the Bridged connection in the Virtual Box and it worked .
