Can't boot to cloud VPS with iPXE

May 4, 2015, 5:54 pm

≫ Next: Ignoring DHCP settings

≪ Previous: ipxe in VM unable to communicate to host

$

0

0

Previously, I use Centos 6 x64 and it's still good but I don't know what happen when something happened and my VPS just stuck at iXPE screen:



I have try to autboot and boot or chain with the URL, but it's not working.



Anyone can help me with this ?

---

Ignoring DHCP settings

May 5, 2015, 6:53 pm

≫ Next: raspberry version?

≪ Previous: Can't boot to cloud VPS with iPXE

$

0

0

G'day

I'm trying to put together a system which will enable us to disregard the settings for next-server and filename in DHCP as having to change that setting (which we can do even though we don't 'own' the DHCP server) is adding additional levels of complexity to our process.

After booting from IPXE and hitting Ctrl-P, then running dhcp I get the settings one would expect.

Editing those settings (either via config or using set commands) when I run

chain tftp://servername/pxelinux.0

it just times out.

However - when I get the next-server and filename settings in DHCP set to match the settings of the server and pxelinux.0 it works.

It seems that the existing settings from the DHCP server are still interfering.

The thread at

http://forum.ipxe.org/showthread.php?mod...85#pid4285

seems to address the same issue ... however I wasn't able to follow the suggested solution.

Any ideas?

Scotty

raspberry version?

May 6, 2015, 8:29 am

≫ Next: Try to free Memory without Signature

≪ Previous: Ignoring DHCP settings

$

0

0

Hi, for what you know, could be possible compile ipxe on raspberry? it could be usefull to build a mini ipxe server with ipxe on Pi, like swiss knife for every System manager ;-)

Try to free Memory without Signature

May 6, 2015, 12:02 pm

≫ Next: ipxe wireless

≪ Previous: raspberry version?

$

0

0

On loading the ipxe rom I get:
"Try to free Memory without Signature"

This is a new PowerEdge M630 blade server that has the firmware fully updated.

I tried to pxe boot a custom built rom with all drivers and also undionly.

reference:
http://fogproject.org/forum/threads/dl38...ure.12877/

Any ideas of other things to try?
Thanks.

---

Bios reports:
10 Gb Ethernet BCM57810

ipxe wireless

May 7, 2015, 3:08 am

≫ Next: windows 8 doesn't boot from undionly.kkpxe

≪ Previous: Try to free Memory without Signature

$

0

0

Hai,
Could you help me? I was trying to boot wireless with ipxe. I have a small foot print xp of 150 mb which I currently boot using iscsi vhd and ipxe in ram. Plz let know the WiFi land card supported by ipxe by default. As I am not expert, cannot add driver as ipxe webpage instructs. Simply want to add ipxe supported WiFi card and boot easily.

Some website says bios should support and Capable of providing usb to lan dongle as boot device. And ipxe people say it doesnt have USB support.

Can I boot ipxe with pen drive and try to detect the WiFi card. Is it possible? Will it detect?

Supported wireless cards plz...

windows 8 doesn't boot from undionly.kkpxe

April 27, 2015, 7:04 pm

≫ Next: ipxe wireless boot

≪ Previous: ipxe wireless

$

0

0

Hi all.

I used undionly.kkpxe to boot windows 7 via iscsi.
Reason that i used kkpxe is short time to initialise.
kpxe took longer than kkpxe. i didn't know why.
but it was good enough. recently i have been trying to boot windows 8 with kkpxe. but i never succeed. it reboots repeatedly.

1. Can i use kpxe without delay like kkpxe?(delay means taking few seconds when ipxe show 'initialising devices')

2. Can i boot windows 8 with kkpxe?

thank you.

ipxe wireless boot

May 7, 2015, 3:33 am

≫ Next: tftp in ipxe script ?

≪ Previous: windows 8 doesn't boot from undionly.kkpxe

$

0

0

Could you help me? I was trying to boot wireless with ipxe. I have a small foot print xp of 150 mb which I currently boot using iscsi vhd and ipxe in ram. Plz let know the WiFi land card supported by ipxe by default. As I am not expert, cannot add driver as ipxe webpage instructs. Simply want to add ipxe supported WiFi card and boot easily.

Some website says bios should support and Capable of providing usb to lan dongle as boot device. And ipxe people say it doesnt have USB support.

tftp in ipxe script ?

May 7, 2015, 5:57 pm

≫ Next: EFI equivalent of undionly.kpxe

≪ Previous: ipxe wireless boot

$

0

0

Hi,
I have a script like:

------
#!ipxe
kernel http://192.168.59.3:9999/coreos_production_pxe.vmlinuz
initrd http://192.168.59.3:9999/coreos_producti...ge.cpio.gz
boot
--------
Files hosted on http seems to work fine how do i do files hosted on tftp ?

In other words,
if I host a files in my /tftpboot/

The statement
kernel tftp://192.168.59.3/coreos_production_pxe.vmlinuz

doesnt work .

I verified that the file can be transfered when tested using a tftpclient but doesnt work from ipxe.

Any idea?

Thanks.

---

EFI equivalent of undionly.kpxe

May 11, 2015, 6:14 am

≫ Next: EFI BC build

≪ Previous: tftp in ipxe script ?

$

0

0

Does an equivalent of undionly.kpxe exists where iPXE keeps the DHCP info? I'm already using snponly.efi but it still need to make a new DHCP request.

EFI BC build

May 11, 2015, 6:25 am

≫ Next: Booting CentOS6.5 kernel failed with UEFI mode

≪ Previous: EFI equivalent of undionly.kpxe

$

0

0

I'm able to boot to iPXE in a VM in UEFI mode. In the DHCP request, the vendor field is PXEClient:Arch:00009, which means UEFI x64 architecture.

However my actual clients (eg Dell Latitude E5540, Lenovo ThinkPad T540p) have PXEClient:Arch:00007 in their vendor field, which means UEFI byte code. I've tried to push them the same binary but it doesn't work. The system downloads the NBP, the screen turn dark and skip to IPv6 booting.

Is there a way to build a Byte Code version?

Booting CentOS6.5 kernel failed with UEFI mode

May 13, 2015, 11:59 pm

≫ Next: Pass CGI arguments to kickstart - Bring back uristring encoding?

≪ Previous: EFI BC build

$

0

0

We have erase the i350 NIC card with efirom, and the following script was used in our PXE server.

#!ipxe
kernel tftp://xxx.xxx.xxx.xxx/boot/vmlinuz initrd=initrd.img
initrd tftp://xxx.xxx.xxx.xxx/boot/initrd.img
boot

Such a scrip works normally with the ubuntu1404, which kernel verison is 3.13.

But we tried to use it with the CentOS6.5 or the Ubuntu 1004, which kernel version is about 2.6.XX

We met the following errors with the kernel.
"Could not select: Exec format error (http://ipxe.org/2e008081)
Could not boot image: Exec format error (http://ipxe.org/2e008081)"

Is there any solution for supporting boot the old 2.6 kernel with iPXE in the UEFI mode?

Pass CGI arguments to kickstart - Bring back uristring encoding?

May 18, 2015, 7:31 pm

≫ Next: A disk read error occurred (under load)

≪ Previous: Booting CentOS6.5 kernel failed with UEFI mode

$

0

0

I'm migrating from PXELINUX and currently pass CGI parameters to a CentOS kickstart file dynamically generated by PHP. iPXE 1.0.0 works fine but the latest git release no longer supports uristring as removed by:

https://git.ipxe.org/ipxe.git/commit/09b...46d875cdf4

I think git iPXE automatically URI encodes the first argument to the kernel command which is usually vmlinuz. But I want to pass the parameters onto the kickstart.

Here is a simplified extract of what I'm trying to do:

# read custom settings
echo -n Use RAID [0|1]: ${} && read raid
echo -n Use LVM [0|1]: ${} && read lvm

# create query string
set query raid=${raid:uristring}
set query ${query}&lvm=${lvm:uristring}

kernel centos7/vmlinuz root=live:centos7/squashfs.img ks=${base-url}/ks/ks7.php?${query}

Am I stuck with 1.0.0 or is there a better way to pass args to the kickstart?

A disk read error occurred (under load)

May 20, 2015, 11:40 am

≫ Next: zlib error

≪ Previous: Pass CGI arguments to kickstart - Bring back uristring encoding?

$

0

0

Hi. First post on this group. Thanks to everyone involved in this project!

I don't actually use iPXE, I'm using gPXE, but I expect the differences may be inconsequential for my purposes. (At this time I am restricted to gPXE).

I have a boot server with several iSCSI targets booting a number of VMs with embedded grub2/gPXE linux kernels. Most of the time everything works great.

My problem is that when the boot server is under heavy load (eg. all the VMs are booting at once), or starved for resources from the environment (eg. I limit its CPU cycles), several of the VMs fail to boot with the error message: "A disk read error occurred Press Ctrl+Alt+Del to restart"

I've tried the various "retry on failed boot" options in vmware, but they don't appear to detect this. I've also tried fallback options in grub, but the failure happens after grub has handed off control to gPXE. Restarting the VMs enough times will eventually lead to a successful boot.

I'm looking for mitigation strategies. Either a retry, or a increase to the timeout, or something else that can prevent the error entirely. Most of this stuff is automated, and its a major timesink to check each vm's console and restart it if it has failed. I'm comfortable editing source, if necessary, but I need someone to point me in the right direction.

Thanks in advance.

zlib error

May 21, 2015, 12:40 pm

≫ Next: error 38086101 and spanning tree/port-fast

≪ Previous: A disk read error occurred (under load)

$

0

0

I have tried and tried to make this work. I have tried to bypass the need to run make in order to use this program, as running the make command results in an error. I keep getting this error at the end of the make command within the src folder:
quote-
[BUILD] bin/hyperv.ids.o
[AR] bin/blib.a
ar: creating bin/blib.a
[HOSTCC] util/zbin
util/zbin.c:7:18: fatal error: lzma.h: No such file or directory
#include <lzma.h>
^
compilation terminated.
Makefile.housekeeping:1294: recipe for target 'util/zbin' failed
make: *** [util/zbin] Error 1
-end quote

I have all the required dependencies installed and I am trying to run this on a debian jessie install. I have found a few posts about this error from 2012 and it was noted to amend the make command with NO_WERROR=1 but this does not change the result. It still fails.

I have tried to create my own files at https://rom-o-matic.eu/ and can't get it to work. I am really confused about doing the simplest thing with this program, but I shall keep trying. This is what I would like to do.

A little background - I have a fully functioning PXE server with both the http and tftp daemons, with several grub entries serving up several different systems from both iso files and squashfs files (like gparted). It works fine because I have access to the router running dhcp and I can amend the dhcp.conf file to set the next-server and file information for other systems to boot from. I even created my own live version of debian to pxe boot. Again, it works fine.

Need to do - On another corporate network, I need to use a usb device to point the boot information to a specific ip address on a LAN (and/or WAN), because I will not have access to the router or the dhcp server. Can this be done with iPXE? From reading, and more reading, it seems like it would be easy but I am having no luck at all.

What I have done - I have successfully created a usb boot device with grub installed, and I can boot the ipxe.iso file from it. But from there I am brain locked and can't get past this.

Any help with the error message above and/or a way around this to make it work would be very appreciated. Thank you.

error 38086101 and spanning tree/port-fast

May 27, 2015, 10:10 am

≫ Next: HTTPS - unrecognised algorithm

≪ Previous: zlib error

$

0

0

Hi,
so we are using ipxe in our environment but more recently we have been running into problems with systems randomly hitting

waiting for link-up on net0......... Down (http://ipxe.org/38086101).

Now this error shows up after the server has already gotten an DHCP IP successfully but hits it after it chainloads ipxe. However this error shows up randomly and sometimes finds the link down but other times sees link up and continues. I will also note that we are seeing this more and more with newer servers overall.

Now we had done some exhaustive troubleshooting and we think we have figured out the problem but was hoping the ipxe team might test, validate, and maybe put a fix in. The problem I believe is actually caused if you are using switches and have spanning-tree on with port-fast on. Every time a pxe image is chainloaded it is actually shutting down the network interface, then turns it on and then requests for a DHCP address. The port on the switch the server is connected on sees the network interface go down and up, and due to portfast it correspondingly turns off/on the port which we actually observe by watching the port lights on the switch. The turning off and on the switch port probably takes a millisecond to 1 second to come back online but I think the chainloaded pxe images loads so fast that it actually gets to checking link-up on net0 while the switch is still resetting that port and thus sees the link as down. Hence a race condition is created and sometimes shows up based on what finishes first (is the switch still in the process of resetting the port while the ipxe loads and gets to checking link on net0).

I am hoping this makes sense and if it does I'm hoping someone can look into this and maybe add a simple sleep command for about 2 seconds before ipxe checks for link on network interfaces. Thanks.

---

HTTPS - unrecognised algorithm

June 2, 2015, 11:04 am

≫ Next: Ipxe EFI "initialising devices" hang

≪ Previous: error 38086101 and spanning tree/port-fast

$

0

0

Hi,

I'm having issues with HTTPS.

When chaining a https URL I'm getting: "Operation not supported (http://ipxe.org/3c00e103)"
We're using "real" certificates, so not self-signed.

I also tested on e.g https://google.com and here it works (no error)

Recompiled with DEBUG=asn1 and it seems that the unrecognised algorithm is part of a certificate. See screenshot at http://snag.gy/j2i8a.jpg

I'm testing with ipxe current from git (commit 6b7157c233541a4cb3c90021e8ca219b0b5dd358)

iPXE 1.0.0+ (6b71) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP HTTPS iSCSI TFTP AoE ELF MBOOT PXE bzImage Menu PXEXT

Fiddling with the code, basically ignoring the errors, it works.

diff --git a/src/crypto/asn1.c b/src/crypto/asn1.c
index aca12bf..6715685 100644
--- a/src/crypto/asn1.c
+++ b/src/crypto/asn1.c
@@ -507,7 +507,8 @@ int asn1_algorithm ( const struct asn1_cursor *cursor,
if ( ! *algorithm ) {
DBGC ( cursor, "ASN1 %p unrecognised algorithm:\n", cursor );
DBGC_HDA ( cursor, 0, cursor->data, cursor->len );
- return -ENOTSUP_ALGORITHM;
+ //return -ENOTSUP_ALGORITHM;
+ return 0;
}

return 0;
diff --git a/src/crypto/x509.c b/src/crypto/x509.c
index 00eb226..c42bc52 100644
--- a/src/crypto/x509.c
+++ b/src/crypto/x509.c
@@ -1763,7 +1763,8 @@ int x509_validate_chain ( struct x509_chain *chain, time_t time,
}

DBGC ( chain, "X509 chain %p found no usable certificates\n", chain );
- return -EACCES_USELESS;
+ //return -EACCES_USELESS;
+ return 0;
}

Ipxe EFI "initialising devices" hang

June 4, 2015, 9:59 am

≫ Next: ipxe on intel i210-at

≪ Previous: HTTPS - unrecognised algorithm

$

0

0

Hello,

i'm experiencing an issue with IPXE on EFI.
I compile IPXE from sources :
make bin-x86_64-efi/ipxe.efi DEBUG=realtek,efi_init

My network card is a realtek.

After booting on EFI shell and launch ipxe.efi, there is the result :


Any idea?

Thks in advance

ipxe on intel i210-at

June 5, 2015, 2:10 am

≫ Next: UEFI 32Bit and Wimboot

≪ Previous: Ipxe EFI "initialising devices" hang

$

0

0

I am trying to get ipxe on the option ROM of an intel i210-AT NIC. Buillding the ipxe image does not seem to be a problem, but flashing the option ROM is trickier.

I have tried the following tools and concluded

flashrom : no support
bootutil.exe : no support
lanconf.exe : only support for read write of entire image, including all or most firmware, not just option ROM

remaining option seems to be backwards engineering the image read with lanconf, but I'd rather not go there.

Anyone tried and succeeded in ipxe:ing the i210 ? if so how did you do it?

I have posted a thread at intel concerning this, google "ipxe i210-at" if you are interested

cheers
jomy

UEFI 32Bit and Wimboot

June 5, 2015, 3:11 am

≫ Next: Please help me. I can't get a DHCPOFFER with my rtl8168 card

≪ Previous: ipxe on intel i210-at

$

0

0

Hello IPXE Community

I have a Problem with a UEFI 32Bit Device. I try to boot a winPE wim(32Bit/4.0) over ipxe.

If I use the wimboot file from git I get the following error message:
All Download ... ok
Could not boot: Error 0x7f048283
Could not boot Image: Error 0x7f048283

Then I found a thread which found a solution with the wimboot.i386 file from git. With that file the wim could be started but then I have a Windows Boot Manager Error: 0xc0000017, "An unexpected error occured"

Do you have an idea what the problem could be?

Regards
Thomas

Please help me. I can't get a DHCPOFFER with my rtl8168 card

June 14, 2015, 12:51 am

≫ Next: Problems with ipxe and pxe-/syslinux

≪ Previous: UEFI 32Bit and Wimboot

$

0

0

Hi. I have this problem. When I boot the computer, the ipxe program starts, so I type Ctrl+B and dhcp. With my rtl8168 card, I am getting this issue: