Quantcast
Channel: iPXE discussion forum - All Forums
Viewing all 1484 articles
Browse latest View live

iPXE chain load over squid

$
0
0
All,

I'm new to iPXE, but was easily able to get DHCP, TFTP and HTTP running as a test of iPXE. However, in my environment, the target server lives on an isolated VLAN until the build is completed. Essentially, this means the "next-server" in dhcpd.conf is only reachable through a squid proxy.

Is there any way to specify a proxy in the URI string of dhcpd.conf, or scripted through the chain command?

Thanks.

DNS problem

$
0
0
Hi, I am setting up some chain loading environment (VMWare auto deploy) and I have the following:
----------------------------
iPXE 1.0.0+ (9361) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: HTTP HTTPS iSCSI DNS TFTP AoE bzImage ELF MBOOT PXE PXEXT Menu

iPXE> dhcp net0
DHCP (net0 b8:ac:6f:82:9d:2a)...... ok
iPXE> show ip
net0.dhcp/ip:ipv4 = 192.168.0.50
iPXE> show dns
net0.dhcp/dns:ipv4 = 192.168.0.1
iPXE> show gateway
net0.dhcp/gateway:ipv4 = 192.168.0.1
iPXE> show next-server
net0.dhcp/next-server:ipv4 = 192.168.0.1
iPXE> show netmask
net0.dhcp/netmask:ipv4 = 255.255.255.0
iPXE> show domain
net0.dhcp/domain:string = test.com
iPXE> chain https://192.168.0.52:6501/vmw/rbd/tramp
https://192.168.0.52:6501/vmw/rbd/tramp... Error 0x3e11613b (http://ipxe.org/3e11613b)
------------------------------------
When i looked up it is "Error: DNS name does not exist". Clearly dns is visible here..

Is there an iPXE equivilant to gpxelinux.0?

$
0
0
The traditional netboot process for Linux uses the pxelinux.0 file provided by syslinux.org . gPXE is also available using the gpxelinux.0 file, which is included with the syslinux RPM on EL systems.

Does iPXE provide an 'ipxelinux.0' equivalent of the gpxelinux.0 file? What would be the advantage of using 'ipxelinux.0' over the standard pxelinux.0 file?

wimboot and windows 8.1

$
0
0
Hello.
I want to boot windows 8.1 using pxe and wimboot but I get some errors that it can't find bootmgr.exe. This happens if I'm using the files from windows 8.1 like is described in the documentation.
If I'm using the bootmgr.exe and the rest of the files from windows 7 then I can get past this message but it bsod with error 0x0000001a. This means memory management error.
Can someone help?
Thank you.

ipxe wimbooted wim file slow to initialize

$
0
0
Does anyone have any idea why I can boot a .wim file in 2-3 seconds, get to where I can see the background and a mouse pointer, but then have to wait around 60 seconds or more before anything happens like the network initializing and my startup program running? if I boot this same file via syslinux it take a lot longer to load but once it gets to the windows screen it fires right up, loads the network and my startup program.

I am booting to syslinux with the following config
(Trimmed to show just the two lines im working on)

label wds
menu label wds - ghost
kernel pxeboot.0

label http boot
kernel ipxe.lkrn dhcp && chain http://10.48.0.200/winpe/ghostboot.ipxe

ipxe file contents
#!ipxe
cpuid --ext 29 && set arch amd64 || set arch x86
imgfree
kernel wimboot
initrd http://10.48.0.200/winpe/${arch}/ISO/bootmgr bootmgr
initrd http://10.48.0.200/winpe/${arch}/ISO/boot/bcd bcd
#initrd http://10.48.0.200/winpe/${arch}/ISO/wgl4_boot.ttf wgl4_boot.ttf
initrd http://10.48.0.200/winpe/${arch}/ISO/boot/boot.sdi boot.sdi
initrd http://10.48.0.200/winpe/${arch}/boot.wim boot.wim
imgstat
boot
I am running Windows server 2008 with wds/dhcp/dns on this server.

The syslinux pxeboot is slow to boot but loads right away
the ipxe boot really fast and then takes a minute or more to load after you see the windows screen.

UEFI and iPXE

$
0
0
I am trying to UEFI: IPv4 PXE boot into clonezilla via iPXE.

This machine is an Acer AIO which does not have legacy BIOS support. But I would also like to see if EFI PXE booting is a possibility for future machines.

I updated dhcp.conf to serve snponly.efi (http://rom-o-matic.eu), which I embedded to point at our server http://server.local/ipxe.menu

So far the menu is displayed and looks good, however if I try to load something I get the error http://ipxe.org/error/2e008001

Code:
:clonezilla
echo Booting Clonezilla Live 2.0.1-1-i686-pae
set base-url ${boot-url}/clonezilla
kernel ${base-url}/clonezilla-live-2.0.1-1-i686-pae/vmlinuz
initrd ${base-url}/clonezilla-live-2.0.1-1-i686-pae/initrd.img
imgargs vmlinuz root= etc etc ..................
boot || goto failed
goto start

:pxelinux
set 210:string tftp://${next-server}/
chain ${210:string}pxelinux.0 || goto failed
goto start

Both get the error message "Could not boot: Exec file error http://ipxe.org/error/2e008001"

Is this not supported yet? Or am I doing the wrong way?

Kind regards

dnsmasq incompatibility?

$
0
0
Hi!

I am trying to netboot a laptop that has no builtin PXE support.
I tried gPXE 1.0.1 and iPXE 1.0.0+ (9361).

After getting IP config over DHCP, gPXE prints:
No filename or root path specified
No more network devices

iPXE prints a similar message:
Nothing to boot , http://ipxe.org/2d03e13b

Apparently filename and root-path are empty (checked as described on the error page).

The cause might be some incompatibility between iPXE and dnsmasq as described here: http://etherboot.org/wiki/dnsmasq#a_pote..._and_a_fix

Other PCs with builtin PXE support work fine on the same LAN.

Any idea how to proceed troubleshooting? Use a debug build?

http://ipxe.org/err/380861

$
0
0
Hi

I m trying to boot a bare metal server using razor. The node gets the IP address from DHCP and after the razor menu, it keeps on trying to link-up net0 and ultimately fails.
The ipxe error says "check that the cable is plugged in" .
Waiting for link-up on net0... failed: Down (http://ipxe.org/38086101)

If the cable was not plugged in, then it wouldnt have got the DHCP address initially and had not gone beyond the razor menu.
Appreciate any help in this regards.

pxelinux.cfg/default
default menu.c32
prompt 0
menu title Razor Boot Menu

timeout 50
f1 help.txt
f2 version.txt

label razor-boot
menu label Automatic Razor Node Boot
kernel ipxe.lkrn
append initrd=razor.ipxe

label boot-else
menu label Bypass Razor
localboot 1
----

/var/log/messages

Jul 10 18:47:06 learn in.tftpd[16634]: RRQ from 10.37.53.92 filename pxelinux.0
Jul 10 18:47:06 learn xinetd[16570]: START: tftp pid=16633 from=10.37.53.92
Jul 10 18:47:06 learn in.tftpd[16634]: tftp: client does not accept options
Jul 10 18:47:06 learn in.tftpd[16635]: RRQ from 10.37.53.92 filename pxelinux.0

Earlier i got these logs too in /var/log/messages
Jul 10 23:50:03 learn in.tftpd[7812]: RRQ from 10.37.53.92 filename pxelinux.0
Jul 10 23:50:03 learn in.tftpd[7812]: tftp: client does not accept options
Jul 10 23:50:03 learn in.tftpd[7813]: RRQ from 10.37.53.92 filename pxelinux.0
Jul 10 23:50:04 learn in.tftpd[7814]: RRQ from 10.37.53.92 filename pxelinux.cfg/44454c4c-3600-1038-805a-b9c04f4c5631
Jul 10 23:50:04 learn in.tftpd[7814]: sending NAK (1, File not found) to 10.37.53.92
Jul 10 23:50:04 learn in.tftpd[7815]: RRQ from 10.37.53.92 filename pxelinux.cfg/01-d4-ae-52-b5-79-ad
Jul 10 23:50:04 learn in.tftpd[7815]: sending NAK (1, File not found) to 10.37.53.92
Jul 10 23:50:04 learn in.tftpd[7816]: RRQ from 10.37.53.92 filename pxelinux.cfg/0A25355C
Jul 10 23:50:04 learn in.tftpd[7816]: sending NAK (1, File not found) to 10.37.53.92
Jul 10 23:50:04 learn in.tftpd[7817]: RRQ from 10.37.53.92 filename pxelinux.cfg/0A25355
Jul 10 23:50:04 learn in.tftpd[7817]: sending NAK (1, File not found) to 10.37.53.92
Jul 10 23:50:04 learn in.tftpd[7818]: RRQ from 10.37.53.92 filename pxelinux.cfg/0A2535
Jul 10 23:50:04 learn in.tftpd[7818]: sending NAK (1, File not found) to 10.37.53.92
Jul 10 23:50:04 learn in.tftpd[7820]: RRQ from 10.37.53.92 filename pxelinux.cfg/0A253
Jul 10 23:50:04 learn in.tftpd[7820]: sending NAK (1, File not found) to 10.37.53.92
Jul 10 23:50:04 learn in.tftpd[7821]: RRQ from 10.37.53.92 filename pxelinux.cfg/0A25
Jul 10 23:50:04 learn in.tftpd[7821]: sending NAK (1, File not found) to 10.37.53.92
Jul 10 23:50:04 learn in.tftpd[7822]: RRQ from 10.37.53.92 filename pxelinux.cfg/0A2
Jul 10 23:50:04 learn in.tftpd[7822]: sending NAK (1, File not found) to 10.37.53.92
Jul 10 23:50:04 learn in.tftpd[7823]: RRQ from 10.37.53.92 filename pxelinux.cfg/0A
Jul 10 23:50:04 learn in.tftpd[7823]: sending NAK (1, File not found) to 10.37.53.92
Jul 10 23:50:04 learn in.tftpd[7824]: RRQ from 10.37.53.92 filename pxelinux.cfg/0
Jul 10 23:50:04 learn in.tftpd[7824]: sending NAK (1, File not found) to 10.37.53.92
Jul 10 23:50:04 learn in.tftpd[7825]: RRQ from 10.37.53.92 filename pxelinux.cfg/default
Jul 10 23:50:04 learn in.tftpd[7826]: RRQ from 10.37.53.92 filename menu.c32
Jul 10 23:50:04 learn in.tftpd[7827]: RRQ from 10.37.53.92 filename pxelinux.cfg/default
Jul 10 23:50:09 learn in.tftpd[7828]: RRQ from 10.37.53.92 filename ipxe.lkrn
Jul 10 23:50:09 learn in.tftpd[7829]: RRQ from 10.37.53.92 filename razor.ipxe

--
My /var/lib/tftpboot directory looks like this
-rw-r--r-- 1 root root 1048576 Jul 11 15:05 ipxe.iso
-rw-r--r-- 1 nobody nobody 398344 Jul 10 23:36 ipxe.lkrn
-rw-r--r-- 1 nobody nobody 56164 Jul 10 23:36 menu.c32
-rw-r--r-- 1 nobody nobody 26449 Jul 10 23:36 pxelinux.0
drwxr-xr-x 2 nobody nobody 4096 Jul 11 00:22 pxelinux.cfg
-rw-r--r-- 1 nobody nobody 1027 Jul 10 23:36 razor.ipxe
-rw-r--r-- 1 nobody nobody 63524 Jul 10 23:36 undionly.kpxe

TFTP Configuration
port = 69
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
group = root
server = /usr/sbin/in.tftpd
bind = 0.0.0.0
server_args = -v -v -v --secure -u nobody /var/lib/tftpboot
per_source = 11

cps = 100 2
flags = IPv4
------
dhcpd.conf

ddns-update-style none;
# ----------
# # PXE Configuration
# # ----------
next-server 10.37.53.89;
filename "pxelinux.0";

subnet 10.37.48.0 netmask 255.255.240.0 {
pool
{
range 10.37.53.91 10.37.53.94;
}

option subnet-mask 255.255.240.0;
option routers 10.37.48.1;
}

host razored {
hardware ethernet d4:ae:52:b5:79:ad;
fixed-address 10.37.53.92;
option host-name "razored";
}
-------

iSCSI boot shows error at boot time using OpenELEC

$
0
0
Hello there,

I posted this already in the OpenELEC forums but nobody seems to know anything about this issue.

I recently installed OpenELEC 3.1.1 testing on an iSCSI target (Synology Diskstation 411slim) which is connected via Gigabit ethernet to a TP-Link TL-WR1043ND. OpenELEC runs on an Asus E45M1-M PRO, also connected via Gigabit ethernet to the TP-Link. The TP-Link runs Gargoyle firmware v1.5.10. Its WLAN is bridged to an AVM FRITZ!Box 7330 which acts as gateway to the Internet.

Installation of OpenELEC was fine with the help from http://wiki.openelec.tv/index.php?title=...ot_-_iSCSI

Everything went fine until the database has been created (about ~500 MB). Since then, I get this error very often at boot time:

Code:
Error in mount_flash: iscsistart: Unable to auto connect
System halted.

I recently updated to OpenELEC 3.1.2, but nothing changed. In 3 of 4 tries, I get the error at boot time and I have to reset the system. With a little bit of luck, the system then boots normally and everything is fine.

I am using iPXE "The Hard and Techy Way": http://wiki.openelec.tv/index.php?title=...P.C2.A0.21

That's my start script to boot OpenELEC:

Code:
:openelec
echo Booting Openelec from iSCSI for ${initiator-iqn}
set root-path ${base-iscsi}:DiskStation
:retry_sanboot
sanboot ${root-path} || goto retry_sanboot

Every idea is welcome!

Thank you very much!

sanboot from AoE using DHCP info

$
0
0
Hello,

Is there they config field in DHCP setting to indicate SAN boot device. I am looking to automate the Server boot from an AOE disk.

Currently I could manually boot the server from AoE target using the following command in that order.

1, dhcp net7 (AoE target disk is available only on net7 of this server).
2. sanboot aoe:e1.0 (Command to boot this server using the AoE target disk with address e1.0)

Please let me if there is setting/parameter for sanboot target disk details could be passed from DHCP server. (similar to next_server for pxe server).

Thanks,
Raghu

iPXE hackathon in Tønsberg, Norway - post-mortem

Windows 8/Server 2012

$
0
0
Hi,

I'm going to setting up a diskless and headless computing cluster. (no monitor, keyboard, mouse)

Right now I'm in testing phase, here's my setup:
1 Win Server 2012 with MSDHCP, IIS 8, iSCSI Target and a TFTP server for undionly.
1 Diskless Node with display so I can monitor progress
1 Diskless Headless Node
Gigabit LAN
WinPE4

Windows Server Unattended Installation finishes then boots to OS at first, then I shut it down.

This is where my problems start: I turn it back on, it loads for a long time then fails, it restarts automatically then boots to Windows fine.

This is my real problem: When the boot fails and it restarts, its MAC address are all zeros. When it has its original MAC address it does NOT boot, when it restarts with the MAC address 00 00 00 00 00 that is when it boots to windows.

PS: I will be using differencing VHD's with this, one child VHD per node.

I know nothing about PHP, dynamic scripts, and databases so I used this simple script I made:

Code:
!ipxe

:retry
dhcp net0 || goto retry
set initiator-iqn computenode
set arch amd64
set keep-san 1
sanboot --drive 0x80 iscsi:${root-path}::::${mac} ||
module amd64/media/bootmgr                     bootmgr        ||
module amd64/media/Boot/BCD                    BCD        ||
module amd64/media/Boot/Fonts/segmono_boot.ttf segmono_boot.ttf    ||
module amd64/media/Boot/Fonts/segoe_slboot.ttf segoe_slboot.ttf    ||
module amd64/media/Boot/Fonts/wgl4_boot.ttf    wgl4_boot.ttf    ||
module amd64/media/Boot/boot.sdi               boot.sdi        ||
module amd64/media/sources/boot.wim            boot.wim        ||
chain wimboot || reboot

Any help would be greatly appreciated. Smile

Assembler 'make' errors on Mac OS X

$
0
0
Hi, all.

I'm stumped.

I'm trying to build this package on Mac OS 10.8.3 (command-line tools from Xcode 4.6.3), but getting an error during the make process. I've only found one hit on these forums, but no resolution - I've got the same issue:
http://forum.ipxe.org/showthread.php?tid=4559

$ make
FATAL:/usr/bin/../libexec/as/x86_64/as: I don't understand '-' flag!
[...]
[DEPS] libgcc/__divdi3.c
FATAL:/usr/bin/../libexec/as/x86_64/as: I don't understand '-' flag!
[...]
FATAL:/usr/bin/../libexec/as/x86_64/as: I don't understand '-' flag!
[BUILD] bin/__divdi3.o
In file included from <command-line>:0:
./include/compiler.h:196:1: error: "__weak" redefined
<built-in>: error: this is the location of the previous definition
make: *** [bin/__divdi3.o] Error 1

It seems that an option is being set in the makefiles that the assembler doesn't like. But I've scanned every makefile, tried commenting out every possible ASFLAG assignment, and still I'm getting this error.

Running make -p doesn't reveal a smoking gun. The issue seems to surround the __divdi3.c module, but I'm unclear why the assembler would be called for it (or where).

Caveat: I'm a hack c++/asm/perl coder at best, so out of my element here.

Help!

Feature Suggestion - Easily Customizable iPXE Binary

$
0
0
Hi, guys.

Tossing out an idea for consideration...

It seems to me that a (the?) major use case for iPXE involves just embedding a script in the bootloader. This relatively benign step is far more difficult than it should be.

For non-developers, getting their environment setup to successfully complete a full build can be more difficult than you might realize. This seems a bit over-the-top, just to embed a block of text in the binary.

Instead...
Why not provide a ready-to-go binary iPXE image (a la the ISO), then provide a tool to patch it with the user's script? A pretty generous block of space could be reserved in the executable for this, only requiring a full build for unusually large scripts.

Taking this one step further...
Why not provide the above as a service via your website. Allow a user to paste their script into a form, then immediately download the binary.

I suspect there are a lot of folks out there like myself who would like to use iPXE, but getting it configured is a real obstacle.

FWIW,
Richard

Build structure and UEFI

$
0
0
Hi,

Pardon me if I am wrong here, but from my understanding of UEFI, interrupt services are not supported there. Also from the ipxe code I see COM32 image format using interrupts.

Don't read further if the above was wrong!!

So my question is
1. Is bin-i386-efi a valid target - because again I think UEFI supports only 64 bit systems ?
2. If bin-i386-efi was valid, then it includes a lot of arch/i386/interface/syslinux code (COMBOOT and COM32), which it should not support (because of interrupts) ?

Thanks for the help!

Sanboot Windows 2012 Intel Nuc.

$
0
0
Hey,

Okay so the current problem I have makes no sense to me.

My setup is the following.

Synology DS412+ DHCP/TFPT/iSCSI/Fileserver

Gateway = Asus Router 192.168.1.1
DHCP/iSCSI = Synology DS412+ 192.168.1.5
So, same subnet.

Intel Nuc i3, successfully sanbooting Windows 8 with setX/gateway 0.0.0.0 after installing it with WinPE.

Windows 2012 Standard/Datacenter Ed. installation works fine. After installation is complete it does not boot, it bluescreens.

With or without gateway. Tried setX/gateway 0.0.0.0, set gateway 192.168.1.5 / 192.168.1.1, Nothing seems to work. Sad

Let me know if you need any logs.

Appreciate any help.

Thanks

Feasible Concept? Booting to local RAM Filesystem

$
0
0
I'd like some help to validate a general concept for PXE... am I heading down a feasible path here?

My goal is to have a system boot quickly via iPXE, run independently (local file system), and run entirely from RAM. The application is for burn-in testing of new systems. We need full access to the local disks to beat them up, swap them out, etc. A small-ish memory footprint would be nice-to-have because we also need to exercise RAM.

I've found processes for installing to local disk via PXE, and PXE-booting diskless workstations from an NFS share. This fellow seems to be the closest, apparently installing CentOS from an ISO to a RAM filesystem:
http://blog.braastad.org/?p=160
Now, I understand that PXE booting an ISO takes like 2x the RAM due to initrd, and doing a kickstart install vs. copy would seem like a much slower boot process. But, maybe his approach is the best option?

Is it conceptually feasible to combine some of these concepts? E.g., the NFS-based approach, adding in a copy-to-ramfs step and booting it locally? I'm wondering how the RAM filesystem would survive the boot, with a new kernel taking over.

FWIW, here's Redhat's approach for NFS-based booting:
https://access.redhat.com/site/documenta...stems.html

The appeal of their "diskless" approach is that I expect the boot time to be faster than a kickstart installation. And it'll be very easy for others to make changes to the source filesystem after I get it working (i.e., no ISO rebuilds). The drawback is this has an ongoing dependency on the NFS server, so I'd like to move the filesystem into local RAM. (The NFS server itself will be a test node at points, so won't always be online.)

Is it conceptually possible to PXE boot from NFS, copy the filesystem, and "remount" the root at the RAMdisk instead? Or PXE boot to an interim OS, create/populate the RAM filesystem, then boot the CentOS6 kernel from within it?

Thanks,
Richard

IPXE Server with Windows Server 2012

$
0
0
Hello people,

I want to install a IPxE Server to Windows Server 2012 base.
I have installed the IIS role. Copied the boot files under wwwroot
Files are in the server IP Available (for all users)

At the start of the Boot CD (http://boot.ipxe.org/ipxe.iso) I have the command (strag + B). dhcp && http: \ \ SERVER \ boot.ipxe executed the works, but until "ok" is no boot file is loaded, why?

// Auf deutsch/german:

Hallo Leute,

ich möchte einen IPXE Server auf Windows Server 2012 basis installieren.
Ich habe die Rolle IIS Installiert. Die Boot Datein unter wwwroot kopiert
Datein sind unter unter der Server IP Abrufbar (für alle User)

Beim starten von der Boot CD (http://boot.ipxe.org/ipxe.iso) habe ich den Befehl (strag + B). dhcp && http:\\SERVER\boot.ipxe ausgeführt, das funktioniert auch, aber bis auf " ok" wird keine Bootdatei geladen, warum ?

efi_image_exec

$
0
0
Hi,

I was trying to chain boot an efi image.
My setup is all like traditional PXE with snponly.efi as the PXE file.

While chainloading an EFI file, I always fail at last_opened_snpdev() as it internally tries to find a PCI SNP device which it does not find. Is the problem here itself ??

Or what I understood that this can be the case as this is a software interface with no PCI address. To fix that I tried installing the protocols onto a new handle (initially NULL) and then loading the image, however the image never finds any files to read. So I tried doing this on the efi_image_handle itself. And this failed again with none of these protocols even being found on the device handle of the new image.

Any suggestions??

Regards

iPXE and hidden SSID

$
0
0
Hi,
First of all as this is my first post here I want to thank the very good work you do here. Thanks.

I'm trying to install a kind of desktop using wireless and we were successful to init wireless adaptor to use WPA2-PSK auth model using an embed script from USB. This works like a charm, but if the SSID is hidden even though we know the SSID we are unable to associate to the AP.

Do you know if hidden SSID is currently supported by iPXE like when connecting to a hidden wireless network?

Thanks so much
Viewing all 1484 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>