[ipxe-devel] Help with iPXE, wimboot and PXELinux
Christian Iwata Nilsson
nikize at gmail.com
Sat Jul 2 17:53:56 UTC 2022
On Sat, 2 Jul 2022, 04:39 Alex Leo, <sir.alexandre.leo at gmail.com> wrote:
> Hey everyone,
>
> Tried asking on forums but registration is closed, hopefully you're guys
> ok with asking the question here.
> I'm attempting to boot Windows PE environment using wimboot and iPXE
> I'm currently loading iPXE through PXELinux using the following in default.
> The iPXE_Test loads up correctly and dumps me into Linux.
> iPXE_Windows_http however hangs after
> http://192.168.10.123/windows/win2019/boot.ipxe ... ok
> with a blinking cursor.
>
> I have the following in the boot.ipxe
> #!ipxe
>
> kernel wimboot
> initrd boot/bcd BCD
> initrd boot/boot.sdi boot.sdi
> initrd sources/boot.wim boot.wim
> boot
>
> #default PXELinux.cfg
> label iPXE_TEST
> menu label iPXE_TEST
> kernel iPXE/ipxe.lkrn
> APPEND dhcp && chain http://boot.ipxe.org/demo/boot.php
>
> label iPXE_Windows_http
> menu label iPXE_Windows_http
> kernel iPXE/ipxe.lkrn
> APPEND dhcp && chain
> http://192.168.10.123/windows/win2019/boot.ipxe
>
>
> Anyone have ideas why it won't boot? I have wimboot in same directory as
> boot.ipxe
>
> Alex
>
If you read the pined topics in the forum it explains the state.
>
Since you have ipxe.lkrn we know you are using pcbios.
Have you tried to use only ipxe to rule out or confirm that this issue is
pxelinux related? (For example by using ipxe.usb on flash drive)
You could also try to manually do imgfetch on boot.ipxe and then run
imgstat and verify that it is detected as script. It is important that
#!ipxe is the first bytes of the script, and that there is no BOM sequence
or similar.
>
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo/ipxe-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20220702/a74d7a4e/attachment.htm>
More information about the ipxe-devel
mailing list