Client Boot Error Msg " Error 0x040ee119"
-
-
DHCP seems to be ok
-
-
@adi Have you look at
@Uncle-Frank said:
There are other posts on the forums about this: https://forums.fogproject.org/topic/3918/please-help-fog-error-0x040ee119
Might be caused by your switch configuration: https://wiki.fogproject.org/wiki//index.php/IPXE#STP.2FPortfast.2FRSTP.2FMSTP_To_Enable_or_Disable.3F
-
Where is your FOG server running? How did you configure VirtualBox network interfaces (host only, bridged).
In the packet dump (log.pcap) I don’t see any DHCP packets! Maybe that is handled internally. But I see TFTP traffic and it seams to finish the download of undionly.kpxe without any issue.
Looking at your screenshots again I noticed a difference just now. See the different ‘Features’ and iPXE versions! The first screenshot shows iPXE which was probably loaded from the FOG server via TFTP (full feature set) but the second screenshot shows the iPXE included in virtualbox! The first iPXE (within virtualbox) is able to get an IP via DHCP (although I don’t see that traffic in your packet dump) but the second iPXE is unable to get an IP from the DHCP.
Here is a good forum post about FOG and Virtualbox: https://forums.fogproject.org/topic/5780/how-to-pxe-boot-a-virtualbox-or-qemu-kvm-box/5
-
This is so simple a problem, and actually well known about.
The issue is VirtualBox. It will only work on the initial load up of the System from a “cold” status. If you only restart the system, you will get this message because the VB resources aren’t releasing the NIC properly. It’s nothing I can fix. However, there is a way around it, but it is not a viable solution if your fog server is dealing with more than just VirtualBox hosts. The Fix, for Virtual Box at least, is to use the ipxe.pxe file rather than the undionly.kpxe file.
-
@adi Can you confirm things are working when “cold starting” the VM? Or using ipxe.pxe?
-
Tom Elliott said:
The issue is VirtualBox. It will only work on the initial load up of the System from a “cold” status. If you only restart the system, you will get this message because the VB resources aren’t releasing the NIC properly.
I’ve tried it and it works like a charm without any problem! FOG 1.2.0 and trunk, Virtualbox 5.0.0 in Windows 7, bridged network with any of the available network adapters (PCnet, Intel, virtio-net …), cold start as well as warm start! I just cannot find a way to reproduce.
My guess is that this issue got fixed within virtualbox at some point. Please check your version and maybe install a newer one. In case this is still not working for you I need to know your virtualbox version and network settings.
-
While it has been a while since I used VirtualBox, I believe you are correct. I was running 4.3.x of Virtual Box (I believe .10) before switching to VMWare on my test bed.
-
Hi
Just to give better picture here…Im running fog server on virtualbox which the virtualbox itself is inside the windows server 2012. the virtualbox was set bridged adapter.
Then I have separate existing DHCP server which pointing to fog server I had enable option 066 and 067.
For testing clients I use one virtualbox which received dhcp from existing dhcp server and one physical machine which is HPcompaq Elite 8300.
So both clients gave same output error…
According to uncle frank, he didnt see any dhcp on my log.pcap…I did check dhcp server many times and follow these link(https://wiki.fogproject.org/wiki/index.php/Modifying_existing_DHCP_server_to_work_with_FOG) still no luck.
-
Change your undionly.kpxe to .kkpxe in your DHCP file.
-
Could you please capture packets on your Windows DHCP server using wireshark and upload that file here too?
And again: Which version of Virtualbox do you use??
-
Why, may I ask, is this under Forum issues?
-
@Uncle-Frank
the client Virtualbox machine is 4.3.26 and virtualbox where fog server are install is 5.0.4…
Im not allow to install wireshark on our dhcp server… -
@adi said:
@Uncle-Frank
the client Virtualbox machine is 4.3.26 and virtualbox where fog server are install is 5.0.4…
Im not allow to install wireshark on our dhcp server…Setup an air-gapped network, and setup your own DHCP. Then run Wireshark.
Without being able to see the traffic, we can’t pin-point what’s going wrong.
I might add that Wireshark is a highly respected and widely used open source tool that countless network and system administrators rely on every day to help them do their jobs. While you should respect your authority figures, you should politely point out (somehow) that disallowing it is silly. It’s like throwing out the most valuable tool you have in your tool box.
- Wireshark is the de facto standard in network analyzer tools. With more than 500,000 downloads a month, the IT industry has embraced Wireshark as the go-to tool for network troubleshooting, optimization and security! Be at the front of the IT pack and show your true colors as a geek leader.
-
the client Virtualbox machine is 4.3.26 …
I’d think this is the issue. Install a newer version of virtualbox on the machine running the client and give it a try!
-
Marking this thread solved as I’ve tested netbooting virtualbox with version 5.0.0 and there seams to be no issue. Problem probably with older versions of virtualbox.
