Be very careful about what filename you specify in dhcpd.conf if you get an error like this: NBP filesize is 0 Bytes PXE-E23:Client received TFTP error from server. If you specify "BOOTx64.efi" then the file had better not be called "BOOTx64.EFI" as it is case sensitive. It's really a case of th........

Just a quick note and warning is that if you are testing to see if EFIPXE booting works on a VM, MAKE SURE it actually works. For example Iinitially tested using my Distro's QEMU 2.5+dfsg-5ubuntu10.46 and ovmf BIOS firmware (OVMF supports EFI). However, I found on old versions of QEMU (like 2.5), EFIbooting with GRUB NEVER works so it may appear that you have made a mistake when everything is fine when you boot a physi........

The problem seems to be that whatever kernel and initrd you have is tied to an old version of CentOS 7 that is no longer in the current repos of most mirrors. If you were previously able to PXEboot and install CentOS and you are sure your network and tftp are good the problem is that you have an outdated kernel and initramfs that point to a defunct version.........

Just edit your tftp file for xinetd like this: *Change the IPto be the IPof the interface you want to listen on. To test if your tftp is available on a certain IP range use nc -u yourip 69 to see if you can still connect (/var/log/messages or /var/log/syslog) should show the connection if it is open. Oct 13 23:20:34 01 xinetd[26631]: Started working: 1 available servic........

In Centos 7 tftpd will not work with selinux. Clients will not be able to connect and this is all you'll see in the log (then nothing more): Sep 18 14:39:15 localhost xinetd[4327]: START: tftp pid=4331 from=192.168.1.65 On the client/computer side you will see this: TFTP. PXE-M0F: Exiting Intel Boot Agent Basically the client is being instantly connected and bloc........