2017-10-16, 14:20
Hello,
since I am not getting any response in the Citrix forum I wanted to ask here too.
I have quite some problems with booting over PXE on my VM hosted on an XenServer 7.2 (all updates installed). From the screenshot shown here I saw that IPXE is used.
To notice: If I boot from a VMWare VM from the same WDS with the same configuration, it works flawlessly.
During the boot I get all Information about the PXE Server via DHCP which works fine but when I start to boot the Image via "chain \boot\x64\pxeboot.n12" I get "TFTP download failed. Press any key to reboot".
I tried with a WDS running on Windows 2008 R2 and Windows Server 2016, same behaviour. I already configured WDS as shown in http://ipxe.org/appnote/chainload_wds.
I tested the TFTP Server functionality with the tftp-client pumpkin and was able to download the pxeboot.n12 succesfully. In the logs of the WDS are entrys which say that the tftp download from my VM actually worked regardless the error message the VM shows.
Any suggestions? If any more information is needed feel free to ask.
KR,
Niklas
since I am not getting any response in the Citrix forum I wanted to ask here too.
I have quite some problems with booting over PXE on my VM hosted on an XenServer 7.2 (all updates installed). From the screenshot shown here I saw that IPXE is used.
To notice: If I boot from a VMWare VM from the same WDS with the same configuration, it works flawlessly.
During the boot I get all Information about the PXE Server via DHCP which works fine but when I start to boot the Image via "chain \boot\x64\pxeboot.n12" I get "TFTP download failed. Press any key to reboot".
I tried with a WDS running on Windows 2008 R2 and Windows Server 2016, same behaviour. I already configured WDS as shown in http://ipxe.org/appnote/chainload_wds.
I tested the TFTP Server functionality with the tftp-client pumpkin and was able to download the pxeboot.n12 succesfully. In the logs of the WDS are entrys which say that the tftp download from my VM actually worked regardless the error message the VM shows.
Any suggestions? If any more information is needed feel free to ask.
KR,
Niklas