Unable to boot Fog from PXE
-
@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 .
-
@Tom-Elliott said:
Is there an error message displayed before it continues to the system? Something like PXE-E32 or similar?
I get that error message, I’m running build number 6985, and I’m getting dhcp from fog
-
@jdmg94 did you try what the OP shows fixed this?
-
@Tom-Elliott I’m on fog’s autogenerated “dhcpd.conf” file, but I don’t really know what OP is reffering to
-
@jdmg94 what do you mean? See your details are sorely lacking. What version of fog? Is fog on a VM and if so what VM software is hosting it? Have you tried changing the network cable? Is the error the same as what the head of this post is referring to (unable to get Config Params or whatever)? What OS is fog running on? Is this all hosts getting this or just this one particular host? When did this start happening? What steps have you tried?
-
Hi Gents,
I am no expert, but hopefully my input can help a little.
First, quick MACLookUp on the MAC in the screenshot 080027 cadmus computer systems, looking for cadmus computer systems, VirtualBox came up. so that’s that. https://www.virtualbox.org/pipermail/vbox-dev/2011-August/010036.html
Just this past week i had an issue with our POS system that runs over PXE (Nothing to do with FOG).
Scenario
EXSi 5.5 Upt 2 host running Windows 7 guest and inside the guest VirtualBox. Inside VirtualBox a Virtual machine running our POS system (Point of Sale jst fyi
) that is called via PXE.The PXE call would time out, which i think is the problem you are having.
The way i was able to make it work was by ENABLING – PROMISCUOUS MODE – in the EXSi Host.
In Virtual box not sure how to enable, but a quick search tells me that all you have to do is change the NIC you are using the FOG with to Bridged Adapter instead of Internal Network which is most likely what you are using.
https://www.virtualbox.org/manual/ch06.htmlJust to try change your FOG server network adapter to Bridged Adapter (Literally will simulate you physical NIC ) to see what happens, it wont hurt !!!
Again way far from expert, but in my case using fog, since this beautiful software uses PXE and DHCP among a lot more things. I though to myself, just to be on the safe side i will keep my FOG server completely isolated from my actual network, because in my case i just use it to clone computers and more important i already have a DHCP and PXE service already running … that would be a call for problems to put my fog server on the same network !!!
Hope this helps a little, if not well i shared something !!!
Cheers mate !!!
