virtualbox client can't netboot pxe-e74 Bad or missing PXE menu and/or prompt information
-
@MarcB would you mind posting the pcap file as an attachment I can’t load what was posted into wireshark to look at it. I’m not smart enough to read the pcap in text form.
-
This somehow sounds as if virtualbox client is not happy with option 43 being sent by dnsmasq in frame number 3. Quiet strange I find. Can you please post your dnsmasq config? Maybe try stripping options
pxe-serviceand/orpxe-promptfrom it - if set. -
@Sebastian-Roth said in virtualbox client can't netboot pxe-e74 Bad or missing PXE menu and/or prompt information:
This somehow sounds as if virtualbox client is not happy with option 43 being sent by dnsmasq in frame number 3. Quiet strange I find. Can you please post your dnsmasq config? Maybe try stripping options
pxe-serviceand/orpxe-promptfrom it - if set.I have 2 lines with that specify pxe-service options and tried commenting them both out. I also commented out pxe-prompt. None of these changes to my ltsp.conf file allowed the VM to netboot.
I’ll attach the ltsp.conf file here.0_1480949862710_ltsp.conf
Thanks for your help.
M
-
I had tried to display everything I saw when I opened it up in Wireshark, but maybe I missed something.
There’s some information in the pcap that I can’t seem to scrup. I found an app called tracewrangler that I’ll try to work with to prepare the pcap file.
Thanks again,
Marc
-
@MarcB If you could post the actual pcap file and I’ll take a look at it.
-
Here’s the anonymized pcap. Hopefully it still provides all the relevant information you need.0_1480964109034_output_anon.pcapng
-
@MarcB In that new pcap file I see “boot file name” being empty in all DHCP answers. Therefore the client does not know which file to load. In the config you posted I see:
... dhcp-boot=undionly.kpxe,,FOGserverIP ...Please change this to (make sure the IP is the correct one pointing to your FOG server):
... dhcp-boot=undionly.kpxe,10.202.47.230,10.202.47.230 ...I usually put the IP address twice, first as server name and the later one to point to the actual IP - see the man page for details about all the options.
-
VMs are still not able to continue the netboot process with the additional specification of the fog server IP. I just used the IP address twice, as this fog server is not available vi dns (so I didn’t use the name).
Thanks for the suggestions though.
I tried the simplified ltsp.conf file you referred me, but that also does not work.
Thanks again,
Marc -
@MarcB Please capture another pcap file with the updated config file.
I can say I just loaded virtual box + extension pack on my zorin (ubuntu based) laptop and I was able to pxe boot from my home fog server running dnsmasq. I just tried in bios (legacy) mode and it worked as it should. So I can say it does work.
-
Cool - I’m glad it’s working for you - there’s hope! What is your OS for FOG (and dnsmasq)? Are you using the simplified ltsp.conf file you posted previously?
Is your Virtualbox 5.1.10? Were there any options in VirtualBox you had so specify (that I might have missed)?
Here’s the logs from the fog server when the VM is netbooted:
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 available DHCP subnet: FOGServerIP/255.255.0.0
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 vendor class: PXEClient:Arch:00000:UNDI:002001
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 PXE(eth0) 08:00:27:7d:81:8f proxy
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 tags: eth0
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 bootfile name: undionly.kpxe
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 next server: FOGServerIP
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 broadcast response
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 sent size: 1 option: 53 message-type 2
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 sent size: 4 option: 54 server-identifier FOGServerIP
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 sent size: 17 option: 97 client-machine-id 00:48:15:92:73:ec:12:42:36:a8:2b:f0:4b:de…
Dec 7 10:54:41 FOGserver dnsmasq-dhcp[14381]: 712868239 sent size: 60 option: 43 vendor-encap 06:01:03:08:07:80:00:01:0a:69:00:2d:09:14…
Dec 7 10:54:49 FOGserver dnsmasq-dhcp[14381]: 712868239 available DHCP subnet: FOGServerIP/255.255.0.0
Dec 7 10:54:49 FOGserver dnsmasq-dhcp[14381]: 712868239 vendor class: PXEClient:Arch:00000:UNDI:002001 -
@MarcB can only quote from memory since I don’t have the setup at work.
But my fog server is 1.3.0RC16 running on a Raspberry Pi running raspbian [https://forums.fogproject.org/topic/8642/installing-a-bit-of-fog-pi-the-hackish-way]. Yes it is running dnsmasq but I compiled 2.76 to have uefi support [https://forums.fogproject.org/topic/8725/compiling-dnsmasq-2-76-if-you-need-uefi-support].
My ltsp.conf configuration is a bit more complex when you add in the uefi support, but the initial script is also listed in the tutorial https://forums.fogproject.org/topic/8726/advanced-dnsmasq-techniques
As for Virtualbox I installed 5.1.10 for Ubuntu 15.10 (“Wily”) x64 and the VirtualBox 5.1.10 Oracle VM VirtualBox Extension Pack. Then I changed the network adapter to bridged that was connected to my laptop’s wireless adapter and set the virtualbox network adapter to the intel (desktop) adapter. Then for the boot order I set the network adapter first in the list.
Your dnsmasq log file “looks” good. It says its sending bootfile and next server. But that isn’t what your pcap was showing.
