2012-07-10, 18:25
I have an EFI Virtual Machine that I can boot successfully to Ubuntu EFI build image.
I cannot however boot to an iPXE build.
I built using:
make bin-i386-efi/ipxe.efi
make bin-x86_64-efi/ipxe.efi
Is this the correct way to built the network boot image? I am using the undi style DHCP options:
subnet 192.168.99.0 netmask 255.255.255.0 {
range 192.168.99.100 192.168.99.200;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.99.255;
option routers 192.168.99.10;
#filename "pxelinux.0";
if exists user-class and option user-class = "iPXE" {
filename "razor.ipxe"; # we are in an iPXE kernel and load static script
} else {
filename "ipxe.efi"; # either i386 or x86_64 renamed
}
next-server 192.168.99.10;
}
Again, I confirmed using the Ubuntu grub EFI image and it works by changing the filename above.
I have also confirmed the TFTP options are set correctly (blksize, tsize)
I think I may be building the wrong iPXE EFI file.
I cannot however boot to an iPXE build.
I built using:
make bin-i386-efi/ipxe.efi
make bin-x86_64-efi/ipxe.efi
Is this the correct way to built the network boot image? I am using the undi style DHCP options:
subnet 192.168.99.0 netmask 255.255.255.0 {
range 192.168.99.100 192.168.99.200;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.99.255;
option routers 192.168.99.10;
#filename "pxelinux.0";
if exists user-class and option user-class = "iPXE" {
filename "razor.ipxe"; # we are in an iPXE kernel and load static script
} else {
filename "ipxe.efi"; # either i386 or x86_64 renamed
}
next-server 192.168.99.10;
}
Again, I confirmed using the Ubuntu grub EFI image and it works by changing the filename above.
I have also confirmed the TFTP options are set correctly (blksize, tsize)
I think I may be building the wrong iPXE EFI file.