Is there a way to get iPXE to explicitly release a DHCP lease?
↧
Explicit DHCP release in iPXE?
↧
Booting CentOS 7 via iPXE on UEFI (HP G9)
Hi All,
I'm trying to boot CentOS 7 using the images in the images/pxeboot directory. The hardware is HP DL380 G9 in native (UEFI) mode. The kernel boots but always panics as follows:
[ 4.138406] List of all partitions:
[ 4.155273] No filesystem could mount root, tried:
[ 4.178291] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 4.218363] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 3.10.0-229.14.1.el7.x86_64 #1
[ 4.238617] usb 3-1: New USB device found, idVendor=03f0, idProduct=7029
[ 4.238620] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.238622] usb 3-1: Product: Virtual Keyboard
[ 4.238623] usb 3-1: Manufacturer: BMC
[ 4.245099] input: BMC Virtual Keyboard as /devices/pci0000:00/0000:00:1c.2/0000:01:00.4/usb3/3-1/3-1:1.0/input/input1
[ 4.245234] hid-generic 0003:03F0:7029.0001: input,hidraw0: USB HID v1.01 Keyboard [BMC Virtual Keyboard ] on usb-0000:01:00.4-1/input0
[ 4.248961] input: BMC Virtual Keyboard as /devices/pci0000:00/0000:00:1c.2/0000:01:00.4/usb3/3-1/3-1:1.1/input/input2
[ 4.249135] hid-generic 0003:03F0:7029.0002: input,hidraw1: USB HID v1.01 Mouse [BMC Virtual Keyboard ] on usb-0000:01:00.4-1/input1
[ 4.402238] usb 4-3: new high-speed USB device number 2 using xhci_hcd
[ 4.566421] usb 4-3: New USB device found, idVendor=0424, idProduct=2660
[ 4.566423] usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.566691] hub 4-3:1.0: USB hub found
[ 4.566715] hub 4-3:1.0: 2 ports detected
[ 4.723865] Hardware name: HP ProLiant DL380 Gen9, BIOS P89 05/06/2015
[ 4.755295] ffffffff81813288 0000000087d94de8 ffff881fd320bd60 ffffffff81604516
[ 4.790669] ffff881fd320bde0 ffffffff815fddba ffffffff00000010 ffff881fd320bdf0
[ 4.826215] ffff881fd320bd90 0000000087d94de8 0000000087d94de8 ffff881fd320be00
[ 4.862665] Call Trace:
[ 4.874754] [<ffffffff81604516>] dump_stack+0x19/0x1b
[ 4.900648] [<ffffffff815fddba>] panic+0xd8/0x1e7
[ 4.923954] [<ffffffff81a455fa>] mount_block_root+0x2a1/0x2b0
[ 4.952414] [<ffffffff81a4565c>] mount_root+0x53/0x56
[ 4.976825] [<ffffffff81a4579b>] prepare_namespace+0x13c/0x174
[ 5.005060] [<ffffffff81a45268>] kernel_init_freeable+0x1f0/0x217
[ 5.036263] [<ffffffff81a449db>] ? initcall_blacklist+0xb0/0xb0
[ 5.064963] [<ffffffff815f2ad0>] ? rest_init+0x80/0x80
[ 5.089948] [<ffffffff815f2ade>] kernel_init+0xe/0xf0
[ 5.114528] [<ffffffff816142d8>] ret_from_fork+0x58/0x90
[ 5.141171] [<ffffffff815f2ad0>] ? rest_init+0x80/0x80
This seems identical to the bug described here https://bugs.centos.org/print_bug_page.php?bug_id=8295 but switching to one of the fixed kernels makes no difference.
Has anyone seen this? For reference, here's the relevant bit of my iPXE config:
kernel http://blah.blah/allen/vmlinuz ro initrd=initrd.img console=ttyS1,115200n8
initrd http://blah.blah/allen/initrd.img
Thanks,
Allen
I'm trying to boot CentOS 7 using the images in the images/pxeboot directory. The hardware is HP DL380 G9 in native (UEFI) mode. The kernel boots but always panics as follows:
[ 4.138406] List of all partitions:
[ 4.155273] No filesystem could mount root, tried:
[ 4.178291] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 4.218363] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 3.10.0-229.14.1.el7.x86_64 #1
[ 4.238617] usb 3-1: New USB device found, idVendor=03f0, idProduct=7029
[ 4.238620] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.238622] usb 3-1: Product: Virtual Keyboard
[ 4.238623] usb 3-1: Manufacturer: BMC
[ 4.245099] input: BMC Virtual Keyboard as /devices/pci0000:00/0000:00:1c.2/0000:01:00.4/usb3/3-1/3-1:1.0/input/input1
[ 4.245234] hid-generic 0003:03F0:7029.0001: input,hidraw0: USB HID v1.01 Keyboard [BMC Virtual Keyboard ] on usb-0000:01:00.4-1/input0
[ 4.248961] input: BMC Virtual Keyboard as /devices/pci0000:00/0000:00:1c.2/0000:01:00.4/usb3/3-1/3-1:1.1/input/input2
[ 4.249135] hid-generic 0003:03F0:7029.0002: input,hidraw1: USB HID v1.01 Mouse [BMC Virtual Keyboard ] on usb-0000:01:00.4-1/input1
[ 4.402238] usb 4-3: new high-speed USB device number 2 using xhci_hcd
[ 4.566421] usb 4-3: New USB device found, idVendor=0424, idProduct=2660
[ 4.566423] usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.566691] hub 4-3:1.0: USB hub found
[ 4.566715] hub 4-3:1.0: 2 ports detected
[ 4.723865] Hardware name: HP ProLiant DL380 Gen9, BIOS P89 05/06/2015
[ 4.755295] ffffffff81813288 0000000087d94de8 ffff881fd320bd60 ffffffff81604516
[ 4.790669] ffff881fd320bde0 ffffffff815fddba ffffffff00000010 ffff881fd320bdf0
[ 4.826215] ffff881fd320bd90 0000000087d94de8 0000000087d94de8 ffff881fd320be00
[ 4.862665] Call Trace:
[ 4.874754] [<ffffffff81604516>] dump_stack+0x19/0x1b
[ 4.900648] [<ffffffff815fddba>] panic+0xd8/0x1e7
[ 4.923954] [<ffffffff81a455fa>] mount_block_root+0x2a1/0x2b0
[ 4.952414] [<ffffffff81a4565c>] mount_root+0x53/0x56
[ 4.976825] [<ffffffff81a4579b>] prepare_namespace+0x13c/0x174
[ 5.005060] [<ffffffff81a45268>] kernel_init_freeable+0x1f0/0x217
[ 5.036263] [<ffffffff81a449db>] ? initcall_blacklist+0xb0/0xb0
[ 5.064963] [<ffffffff815f2ad0>] ? rest_init+0x80/0x80
[ 5.089948] [<ffffffff815f2ade>] kernel_init+0xe/0xf0
[ 5.114528] [<ffffffff816142d8>] ret_from_fork+0x58/0x90
[ 5.141171] [<ffffffff815f2ad0>] ? rest_init+0x80/0x80
This seems identical to the bug described here https://bugs.centos.org/print_bug_page.php?bug_id=8295 but switching to one of the fixed kernels makes no difference.
Has anyone seen this? For reference, here's the relevant bit of my iPXE config:
kernel http://blah.blah/allen/vmlinuz ro initrd=initrd.img console=ttyS1,115200n8
initrd http://blah.blah/allen/initrd.img
Thanks,
Allen
↧
↧
wimboot UEFI boot fails
Hi,
I have an MDT generated WinPE boot image that works with iPXE when BIOS PXE booting, but fails in UEFI mode with error "A required device isn't connected or can't be accessed".
Wimboot is the latest version (2.5.0), and I can't see anything wrong with the "wimboot pause" output.
Seems I can't attach files, so screenshots and BCD dump are at: http://mikat.iki.fi/tmp/wimboot-uefi/
I have an MDT generated WinPE boot image that works with iPXE when BIOS PXE booting, but fails in UEFI mode with error "A required device isn't connected or can't be accessed".
Wimboot is the latest version (2.5.0), and I can't see anything wrong with the "wimboot pause" output.
Seems I can't attach files, so screenshots and BCD dump are at: http://mikat.iki.fi/tmp/wimboot-uefi/
↧
No progress bar when encapsulating boot.wim
Hi
I am using PXELINUX 6.03 with wimboot 2.4.1 and I am loading my image with this commands from pxelinux.cfg\default:
com32 linux.c32
append wimboot initrdfile=bootmgr.exe,boot/BCD,boot/boot.sdi,boot/boot.wim
When loading this option, I do not see any progress in percentage when wimboot is encapsulating the big boot.wim file. It just says "OK" after a minute.
How can I display a progress in percentage or a progress bar?
I am using PXELINUX 6.03 with wimboot 2.4.1 and I am loading my image with this commands from pxelinux.cfg\default:
com32 linux.c32
append wimboot initrdfile=bootmgr.exe,boot/BCD,boot/boot.sdi,boot/boot.wim
When loading this option, I do not see any progress in percentage when wimboot is encapsulating the big boot.wim file. It just says "OK" after a minute.
How can I display a progress in percentage or a progress bar?
↧
DLPXE
hi
i am trying to build an efi boot file for displaylink network card using DLPXE repository.
however if i try make bin/ipxe.efi ,snp.efi,.... etc i get make: *** No rule to make target `bin/ncm.efi'. Stop.
What am i doing wrong and how can i build that efi file?
i am trying to build an efi boot file for displaylink network card using DLPXE repository.
however if i try make bin/ipxe.efi ,snp.efi,.... etc i get make: *** No rule to make target `bin/ncm.efi'. Stop.
What am i doing wrong and how can i build that efi file?
↧
↧
Anyone iPXE booting Windows10 ?
Over here, doesn't work:
WinPE environment sees iSCSI target to install to. Install goes fine....until install needs to reboot. On reboot, iPXE part of booting goes fine, windows boot loader is started....but runs into an inaccesible boot device.
afaik, during boot process the system loads registry settings and boot-time drivers, and then re-mounts C:\ drive using disk driver and settings from registry. I assume that's the failing stage, resulting in an inaccessible both device.
Tried both W10Pro and W10Ent, same result.
W8.1 Windows server 2012R2 and even server2016 Preview3 all iPXE boot fine.
Hints & tips welcome
WinPE environment sees iSCSI target to install to. Install goes fine....until install needs to reboot. On reboot, iPXE part of booting goes fine, windows boot loader is started....but runs into an inaccesible boot device.
afaik, during boot process the system loads registry settings and boot-time drivers, and then re-mounts C:\ drive using disk driver and settings from registry. I assume that's the failing stage, resulting in an inaccessible both device.
Tried both W10Pro and W10Ent, same result.
W8.1 Windows server 2012R2 and even server2016 Preview3 all iPXE boot fine.
Hints & tips welcome
↧
embedded chain times out but interactive chain works
Hi All,
I came across a strange behavior as in embedded "chain command timesout but
interactive/manual chain command works.
Below is my embedded script during compiling my bin/ipxe.iso.
set net4/ip a.b.c.d
set net4/netmask 255.255.255.0
set net4/gateway a.b.c.1
set net4/dns 10.0.0.1
set net4/domain mycompany.com
ifopen net4
chain http://boot.ipxe.org/demo/boot.php || shell
The iso will put in the shell after timing out.
If I give the same "chain" command, it just work.
I will be doing more forensic investigation but if you know something from top of your head, please let me know.
Thanks,
I came across a strange behavior as in embedded "chain command timesout but
interactive/manual chain command works.
Below is my embedded script during compiling my bin/ipxe.iso.
set net4/ip a.b.c.d
set net4/netmask 255.255.255.0
set net4/gateway a.b.c.1
set net4/dns 10.0.0.1
set net4/domain mycompany.com
ifopen net4
chain http://boot.ipxe.org/demo/boot.php || shell
The iso will put in the shell after timing out.
If I give the same "chain" command, it just work.
I will be doing more forensic investigation but if you know something from top of your head, please let me know.
Thanks,
↧
INACCESSIBLE_BOOT_DEVICE
INACCESSIBLE_BOOT_DEVICE after the first reboot win7/8/10
There is a home network with tp-link a router, the server on base дебиан
Described below actions were done on the i5 computer with realtek Gb by the adapter on old intell atom netbook
The task - will arrive Barebone intell pentium based TVBOX soon, I want to load it on ISCSI
I created on debian server (10.1.1.2) iSCSI disk
iqn.2014-09.HomeServer:storage
Option 1.
I connected ISCSI a disk to personal computer Windows, with the help of UltraISO Windows 7/8/10 on this disk unpacked an image and the BOOTICEx64 program prescribed it MBR
On the site https://rom-o-matic.eu/I made an USB image with a script
#!ipxe
dhcp
set netX/gateway 10.1.1.2
sanboot iscsi:10.1.1.2::::iqn.2015-09.HomeServer:storage
Installation when asked to choose language and keyboard layout went, pressed Shift+F10, further in the opened window gathered Drvload x:\drvlan.inf (a way to drivers of the network interface card).
Then I wrote Wpeutil InitializeNetwork.
Then the installer saw a disk and copying of files began
After the first reset Windows thinks 3 minutes and stops with a mistake INACCESSIBLE_BOOT_DEVICE
Option 2.
I downloaded Windows Assessment and Deployment Toolkit (ADK) for win 7/8/10, I pulled out from it WinPE, I put it on http://10.1.1.2, also there I put the last wimboot
I created USB with a script
#!ipxe
dhcp
set netX/gateway 10.1.1.2
chain http://10.1.1.2/boot.ipxe
----boot.ipxe----
#!ipxe
set netX/gateway 10.1.1.2
sanhook iscsi:10.1.1.2::::iqn.2015-09.HomeServer:storage
kernel wimboot
initrd amd64/media/Boot/BCD BCD
initrd amd64/media/Boot/boot.sdi boot.sdi
initrd amd64/media/sources/boot.wim boot.wim
boot
WinPE was loaded, I try to give command
net use \\10.1.1.2\install - error, though the network is also passes a ping
I unpacked iso image Windows on USB, connected to winPE and wrote
cd g:
setup.exe
Installation, but after the first loading again went INACCESSIBLE_BOOT_DEVICE
I tried such to do on two PC about Windows 7/8/10 - the result is identical
Where I make a mistake?
There is a home network with tp-link a router, the server on base дебиан
Described below actions were done on the i5 computer with realtek Gb by the adapter on old intell atom netbook
The task - will arrive Barebone intell pentium based TVBOX soon, I want to load it on ISCSI
I created on debian server (10.1.1.2) iSCSI disk
iqn.2014-09.HomeServer:storage
Option 1.
I connected ISCSI a disk to personal computer Windows, with the help of UltraISO Windows 7/8/10 on this disk unpacked an image and the BOOTICEx64 program prescribed it MBR
On the site https://rom-o-matic.eu/I made an USB image with a script
#!ipxe
dhcp
set netX/gateway 10.1.1.2
sanboot iscsi:10.1.1.2::::iqn.2015-09.HomeServer:storage
Installation when asked to choose language and keyboard layout went, pressed Shift+F10, further in the opened window gathered Drvload x:\drvlan.inf (a way to drivers of the network interface card).
Then I wrote Wpeutil InitializeNetwork.
Then the installer saw a disk and copying of files began
After the first reset Windows thinks 3 minutes and stops with a mistake INACCESSIBLE_BOOT_DEVICE
Option 2.
I downloaded Windows Assessment and Deployment Toolkit (ADK) for win 7/8/10, I pulled out from it WinPE, I put it on http://10.1.1.2, also there I put the last wimboot
I created USB with a script
#!ipxe
dhcp
set netX/gateway 10.1.1.2
chain http://10.1.1.2/boot.ipxe
----boot.ipxe----
#!ipxe
set netX/gateway 10.1.1.2
sanhook iscsi:10.1.1.2::::iqn.2015-09.HomeServer:storage
kernel wimboot
initrd amd64/media/Boot/BCD BCD
initrd amd64/media/Boot/boot.sdi boot.sdi
initrd amd64/media/sources/boot.wim boot.wim
boot
WinPE was loaded, I try to give command
net use \\10.1.1.2\install - error, though the network is also passes a ping
I unpacked iso image Windows on USB, connected to winPE and wrote
cd g:
setup.exe
Installation, but after the first loading again went INACCESSIBLE_BOOT_DEVICE
I tried such to do on two PC about Windows 7/8/10 - the result is identical
Where I make a mistake?
↧
No progress (percentage) when encapsulating
Hi
I am using PXELINUX 6.03 with wimboot 2.4.1 and I am loading my image with this commands from pxelinux.cfg\default:
com32 linux.c32
append wimboot initrdfile=bootmgr.exe,boot/BCD,boot/boot.sdi,boot/boot.wim
When loading this option, I do not see any progress in percentage when wimboot is encapsulating the big boot.wim file. It just says "OK" after a minute.
How can I display a progress in percentage or a progress bar?
I am using PXELINUX 6.03 with wimboot 2.4.1 and I am loading my image with this commands from pxelinux.cfg\default:
com32 linux.c32
append wimboot initrdfile=bootmgr.exe,boot/BCD,boot/boot.sdi,boot/boot.wim
When loading this option, I do not see any progress in percentage when wimboot is encapsulating the big boot.wim file. It just says "OK" after a minute.
How can I display a progress in percentage or a progress bar?
↧
↧
Loading iPXE from RPL
I'm trying to boot linux, using an old ISA NIC.
Until now, my iPXE setup works with various PCI NICs, mostly Realtek RTL8139s and 3Com 3c905s, either with from their original bootrom or with gPXE/iPXE added to the BIOS ROM.
Chainloading from the original PXE ROM to iPXE and then to Linux, DOS or memtest86 works without any problem.
Now, I replaced the PCI NIC with a NE2000 compatible ISA card (Dlink DE-224 with DE22X4 16KiB bootrom).
Unluckily, the only bootrom available only support RPL and the addressable ROM is too small for etherboot/gPXE/iPXE anyways.
But I discovered rpld, so I installed it on a random machine connected to the same network.
I never managed to boot a recent gPXE or an iPXE image (either rom or pxe images fails to boot or displays "pxe->eb: no pxe stack found!").
Rpld's load/execute addresses are not very clearly explained, but that's only a part of the problem (and doesn't depends on iPXE).
Anyways, I managed to boot an old etherboot 5.4.3 image (works the same way with rom as well as zrom images) from RPL, assuming load=0x1000 and execute=0x1006 (it also works the same way with load=0x2000 and execute=0x2006), following this post.
The RPL ROM loads this etherboot image, then chainloads to iPXE, which displays the menu, load the images and tries to boot from them.
The main problem is to have the PC rebooting as soon as it tries to boot from either memtest, Linux kernel/initrd, DOS floppy image or even memtest86 iso.
Until now, my iPXE setup works with various PCI NICs, mostly Realtek RTL8139s and 3Com 3c905s, either with from their original bootrom or with gPXE/iPXE added to the BIOS ROM.
Chainloading from the original PXE ROM to iPXE and then to Linux, DOS or memtest86 works without any problem.
Now, I replaced the PCI NIC with a NE2000 compatible ISA card (Dlink DE-224 with DE22X4 16KiB bootrom).
Unluckily, the only bootrom available only support RPL and the addressable ROM is too small for etherboot/gPXE/iPXE anyways.
But I discovered rpld, so I installed it on a random machine connected to the same network.
I never managed to boot a recent gPXE or an iPXE image (either rom or pxe images fails to boot or displays "pxe->eb: no pxe stack found!").
Rpld's load/execute addresses are not very clearly explained, but that's only a part of the problem (and doesn't depends on iPXE).
Anyways, I managed to boot an old etherboot 5.4.3 image (works the same way with rom as well as zrom images) from RPL, assuming load=0x1000 and execute=0x1006 (it also works the same way with load=0x2000 and execute=0x2006), following this post.
The RPL ROM loads this etherboot image, then chainloads to iPXE, which displays the menu, load the images and tries to boot from them.
The main problem is to have the PC rebooting as soon as it tries to boot from either memtest, Linux kernel/initrd, DOS floppy image or even memtest86 iso.
↧
multiple initrd/imgfetch in UEFI mode
Hi,
I'm trying to upload multiple files from my iPXE script to get them during initrd.
It works fine in legacy mode, but I not in UEFI mode.
The file test.txt is correctly loaded (I have done an imgstat after the load) but can not be found under /tmp (neither anywhere) during the initrd phase. It works fine in legacy mode ...
Any advices ?
Note: It took me time to find that the kernel option initrd=<file> is compulsory in UEFI mode (not in legacy)
Thanks,
Simon.
I'm trying to upload multiple files from my iPXE script to get them during initrd.
It works fine in legacy mode, but I not in UEFI mode.
Code:
#!ipxe
kernel http://my.web.server/boot/vmlinuz initrd=initrd.img
initrd http://my.web.server/boot/initrd.img
initrd http://my.web.server/boot/test.txt /tmp/test.txt
bootThe file test.txt is correctly loaded (I have done an imgstat after the load) but can not be found under /tmp (neither anywhere) during the initrd phase. It works fine in legacy mode ...
Any advices ?
Note: It took me time to find that the kernel option initrd=<file> is compulsory in UEFI mode (not in legacy)
Thanks,
Simon.
↧
RNDIS Support
I ran a full efi compile of the ipxe source and booted to the resulting executable in EFI. From the iPXE command line I was hoping to see via 'ifstat' that the RNDIS (lan-over-usb) device was detected by ipxe, but was disappointed to not see it. I would like to configure the MAC address for that device. The RNDIS device is provided by a Lenovo x3550M5 server. I see hints of RNDIS support in the source, am I compiling it incorrectly or would a device driver need to be written in ipxe to see it? Thanks!
↧
submit http request
HI all,
any chance to submit just a http URL to upload a status Information to our deployment server?
I tryied to use chain ... but this leads to a Crash.
I realy Need to call one URL with paramters. Thats all. ipxe can ignore the result.
Andreas
any chance to submit just a http URL to upload a status Information to our deployment server?
I tryied to use chain ... but this leads to a Crash.
I realy Need to call one URL with paramters. Thats all. ipxe can ignore the result.
Andreas
↧
↧
No DHCP
Can iPXE be used without DHCP, is it easy to set the IP, is it possible to automate setting the IP?
↧
iPXE.efi and wimboot Secure Boot Signing Status
Hello,
First of all thanks for this software, it works amazing and I am hoping to use it to finally have support and performance with WDS/MDT/SCCM commensurate with other network booting systems like Apple NetBoot.
I see from this article:
UEFI Secure Boot signing using a DigiCert eToken
And from these threads:
UEFI SecureBoot support
wimboot not loading
EFI BC build [Solved: secure boot]
Booting CentOS6.5 kernel failed with UEFI mode
That secure boot still does not have full support. This is the last piece we need to use iPXE more since we have lots of systems that ship with SecureBoot on by default now and we need 'out-of-box' support for SecureBoot as its not feasible for us to modify every system to disable it.
Is there anything a simple fan of this project can do to help this process? Is there any plans to pressure Microsoft more, or any testing ipxe.efi files we can beta test? My organization may be able to use contacts within MS to get this process to the right person's eyes, if this is purely a political / support issue from their EFI signing process.
Thanks again so much for the work you've done here, its really amazing how much better this process works than the antiquated TFTP-only process that WDS uses out of box.
First of all thanks for this software, it works amazing and I am hoping to use it to finally have support and performance with WDS/MDT/SCCM commensurate with other network booting systems like Apple NetBoot.
I see from this article:
UEFI Secure Boot signing using a DigiCert eToken
And from these threads:
UEFI SecureBoot support
wimboot not loading
EFI BC build [Solved: secure boot]
Booting CentOS6.5 kernel failed with UEFI mode
That secure boot still does not have full support. This is the last piece we need to use iPXE more since we have lots of systems that ship with SecureBoot on by default now and we need 'out-of-box' support for SecureBoot as its not feasible for us to modify every system to disable it.
Is there anything a simple fan of this project can do to help this process? Is there any plans to pressure Microsoft more, or any testing ipxe.efi files we can beta test? My organization may be able to use contacts within MS to get this process to the right person's eyes, if this is purely a political / support issue from their EFI signing process.
Thanks again so much for the work you've done here, its really amazing how much better this process works than the antiquated TFTP-only process that WDS uses out of box.
↧
Wimboot stops booting from UEFI Syslinux
Hi there
Wonder if you could help me. I have wimboot working under bios mode, but would like to get this working under uefi. It get as far as "Encapsulating LitetouchPE_x64.wim" but does nothing from there.
my config under syslinux 6.03 is as follows
com32 linux.c32
append wimboot initrdfile=bootmgr.efi,boot/BCD,boot.sdi,LitetouchPE_x64.win
I'm using the latest wimboot 2.5.1 and I’ve added the rawbcd and gui options as well.
If there is any more info you require or I’ve left it out please ask me.
many thanks
Shrubies.
Wonder if you could help me. I have wimboot working under bios mode, but would like to get this working under uefi. It get as far as "Encapsulating LitetouchPE_x64.wim" but does nothing from there.
my config under syslinux 6.03 is as follows
com32 linux.c32
append wimboot initrdfile=bootmgr.efi,boot/BCD,boot.sdi,LitetouchPE_x64.win
I'm using the latest wimboot 2.5.1 and I’ve added the rawbcd and gui options as well.
If there is any more info you require or I’ve left it out please ask me.
many thanks
Shrubies.
↧
iPXE support for SUSE OS
Hi There,
I have setup a iPXE server in which I am planning to install all linux flavors. I have automated the installation process using kickstart files for linux. When it comes to SUSE i am not able to find out how to provide the kickstart file.
I have tried the below formats ipxe script.
initrd http://172.20.10.5/cobbler/ks_mirror/SLE...der/initrd
chain http://172.20.10.5/cobbler/ks_mirror/SLE...ader/linux initrd=initrd ks=http://172.20.10.5/ks_mirror/SLES12GMx64/autoinst.xml network ksdevice=${netX/mac}
boot
However it is not detecting the kickstart file. I have tried replacing the ks with autoyast but no luck. Please let me know if anyone having the working syntax for providing kickstart in through iPXE script.
Thank you,
Donofap
I have setup a iPXE server in which I am planning to install all linux flavors. I have automated the installation process using kickstart files for linux. When it comes to SUSE i am not able to find out how to provide the kickstart file.
I have tried the below formats ipxe script.
initrd http://172.20.10.5/cobbler/ks_mirror/SLE...der/initrd
chain http://172.20.10.5/cobbler/ks_mirror/SLE...ader/linux initrd=initrd ks=http://172.20.10.5/ks_mirror/SLES12GMx64/autoinst.xml network ksdevice=${netX/mac}
boot
However it is not detecting the kickstart file. I have tried replacing the ks with autoyast but no luck. Please let me know if anyone having the working syntax for providing kickstart in through iPXE script.
Thank you,
Donofap
↧
↧
Recent Build HTTP Oddness
Hello!
I want to start with the devs here are great and do great work!
I did a new build today, after not doing one for a few months, and at first I was having a lot of issues getting http://ipxe.org/420c6001 errors. Then I switched to using Tomcat (which does have keep alive and chunking) as the backend HTTP server. Now it's working again but A TON slower than in the past. A 200mb image takes about 4 minutes to load. I am doing a wimboot, it get to the actual wim file really fast, then instantly goes to 100%, then down to 99%, stays there for the 4 minutes, then boots fine.
Any thoughts?
Dan
I want to start with the devs here are great and do great work!
I did a new build today, after not doing one for a few months, and at first I was having a lot of issues getting http://ipxe.org/420c6001 errors. Then I switched to using Tomcat (which does have keep alive and chunking) as the backend HTTP server. Now it's working again but A TON slower than in the past. A 200mb image takes about 4 minutes to load. I am doing a wimboot, it get to the actual wim file really fast, then instantly goes to 100%, then down to 99%, stays there for the 4 minutes, then boots fine.
Any thoughts?
Dan
↧
Few scripting questions
I'm trying to enumerate interfaces from within iPXE. I figured I could loop through each one doing "dhcp net${i}", then looking for info on the NIC like "${netX/dhcp-server}" and finally closing the interface with "ifclose net${i}".
I would like to skip over the interface that iPXE used when initially booting. The problem is I'm not seeing a way to get the name or even index of the current interface. Something like "${netX/ip}" except "${netX/index}" which returns "net0" for example.
Anything like this available that I'm just not seeing?
Second problem is there is the possibility that in our setup iPXE might be waiting around on a menu screen and intermittently checking an HTTP server for any boot instructions. Since iPXE doesn't have anything built into renew it's DHCP address before it's lease expires I figured I could do "dhcp net0" (also needs the index above) which seems to renew it just fine.
The problem with this is after doing that it seems to break being able to do relative paths in scripts. The reason we need to renew is I don't want the DHCP server to hand out another lease with the same IP.
Some psuedo code of what a script might look like for the interface enumeration http://pastebin.com/TRnAMkR5.
I would like to skip over the interface that iPXE used when initially booting. The problem is I'm not seeing a way to get the name or even index of the current interface. Something like "${netX/ip}" except "${netX/index}" which returns "net0" for example.
Anything like this available that I'm just not seeing?
Second problem is there is the possibility that in our setup iPXE might be waiting around on a menu screen and intermittently checking an HTTP server for any boot instructions. Since iPXE doesn't have anything built into renew it's DHCP address before it's lease expires I figured I could do "dhcp net0" (also needs the index above) which seems to renew it just fine.
The problem with this is after doing that it seems to break being able to do relative paths in scripts. The reason we need to renew is I don't want the DHCP server to hand out another lease with the same IP.
Some psuedo code of what a script might look like for the interface enumeration http://pastebin.com/TRnAMkR5.
↧
pxelinux chain to iPXE no more network devices
Hello.
I try to boot windows setups using wimboot. For a long time I use pxelinux, so I use iPXE to load wimboot and other files like this:
label Microsoft Windows 7 Setup
menu label Microsoft Windows 7 Setup
kernel ipxe.krn
APPEND dhcp && kernel http://server.com/wds/x86/wimboot && initrd http://server.com/wds/x86/bcd BCD && initrd http://server.com/wds/x86/boot.sdi boot.sdi && initrd http://server.com/wds/x86/boot-win7_2k8_x86.wim boot.wim && boot
This works in VirtualBox environment. Worked at modern cimputer. But does not work on an 5y old computer. After pxelinux loads and starts ipxe.krn, there is nothing happens and it try to find other booting defices.
I've remode append command. After loading ipxe.krn I press Ctrl+B to see some info. And I get: no more network devices.
How to resolve this problem?
Another question. pxelinux have an option to skip loading menus and other if Scroll Lock is not activated, or Ctrl is not pressed. Is such a option for iPXE?
I try to boot windows setups using wimboot. For a long time I use pxelinux, so I use iPXE to load wimboot and other files like this:
label Microsoft Windows 7 Setup
menu label Microsoft Windows 7 Setup
kernel ipxe.krn
APPEND dhcp && kernel http://server.com/wds/x86/wimboot && initrd http://server.com/wds/x86/bcd BCD && initrd http://server.com/wds/x86/boot.sdi boot.sdi && initrd http://server.com/wds/x86/boot-win7_2k8_x86.wim boot.wim && boot
This works in VirtualBox environment. Worked at modern cimputer. But does not work on an 5y old computer. After pxelinux loads and starts ipxe.krn, there is nothing happens and it try to find other booting defices.
I've remode append command. After loading ipxe.krn I press Ctrl+B to see some info. And I get: no more network devices.
How to resolve this problem?
Another question. pxelinux have an option to skip loading menus and other if Scroll Lock is not activated, or Ctrl is not pressed. Is such a option for iPXE?
↧