Unrecognised argument "BOOT_IMAGE=windowsOS/wimboot"

[Ritzo]

I try to install windows with wimboot via ipxe and a tftp menu.

I got the following messages incl. error
Loading windowsOS/wimboot ... ready.
wimboot v2.5.2 -- Windows Imaging Format bootloader -- http://ipxe.org/wimboot

Command line: "url=http://<webserver>/tftpboot/windowsOS/boot-ipxe BOOT_IMAGE=windowsOS/wimboot "
Unrecongnised argument "BOOT_IMAGE=windowsOS/wimboot"
Press a key to reboot

tftp-menu
label ctidevw10001
menu label 2016 ipxe wimboot2.5
kernel windowsOS/wimboot
append url=http://<webserver>/tftpboot/windowsOS/boot.ipxe

label ctidevw10011
menu label 2016 ipxe wimboot2.5 linux
LINUX windowsOS/wimboot
append url=http://<webserver>/tftpboot/windowsOS/boot.ipxe

label ctidevw10001
menu label 2016 ipxe wimboot2.5 http
kernel http://<webserver>:/tftpboot/windowsOS/wimboot
append url=http://ctsprdsup001.core.weblocal/tftpboot/windowsOS/boot.ipxe

I did some grep in the windowsOS and wimboot folder and in the txt.cfg-File with the tftp-bootmenu and search for "BOOT_IMAGE"-parameter and I can't find this parameter.

I search and tried serveral advices from other website without success.

Question:
- How do I have to define the tftp-menu, to get wimboot working?
- Where does this Parameter "BOOT_IMAGE" come from.

OS
- Ubuntu xenial with tftpd-hpa, dhcp, ..

Other Linux-systems I can install with the tftp successfully.

Thanks for your advice in advance
Ritzo

[NiKiZe]

It looks like you are using pxelinux

please boot ipxe.pxe first, you can find it at http://boot.ipxe.org/ipxe.pxe
or you could replace pxelinux.0 with http://boot.ipxe.org/undionly.kpxe

after this however you will need to recreate your menu in the ipxe scripting language.

And finally to use wimboot you can see some examples at http://ipxe.org/wimboot but before that we need to get ipxe running

there is no "tftp-menu", with pxelinux you have the pxelinux config file, which has the default.* (sorry forgot exact filename) fallback.

with ipxe you can call the file whatever you want and then point ipxe to that file with some "dhcp magic"

BOOT_IMAGE is some special name that something might use, but it is not used by ipxe or wimboot.


To get your ipxe.pxe (or undionly.kpxe might be better in your case) I would recommend starting with: http://ipxe.org/howto/chainloading#break...hcp_server

[Ritzo]

(2016-11-15 00:11)NiKiZe Wrote:  It looks like you are using pxelinux

please boot ipxe.pxe first, you can find it at http://boot.ipxe.org/ipxe.pxe
or you could replace pxelinux.0 with http://boot.ipxe.org/undionly.kpxe

after this however you will need to recreate your menu in the ipxe scripting language.

And finally to use wimboot you can see some examples at http://ipxe.org/wimboot but before that we need to get ipxe running

there is no "tftp-menu", with pxelinux you have the pxelinux config file, which has the default.* (sorry forgot exact filename) fallback.

with ipxe you can call the file whatever you want and then point ipxe to that file with some "dhcp magic"

BOOT_IMAGE is some special name that something might use, but it is not used by ipxe or wimboot.


To get your ipxe.pxe (or undionly.kpxe might be better in your case) I would recommend starting with: http://ipxe.org/howto/chainloading#break...hcp_server

Thanks a lot for your response. I will try this.