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

iPXE, iSCSI, isc-dhcp, FreeBSD 10.x

$
0
0
Hi, (I posted this to the developers list by accident)

I'm a little bit confused on using iPXE with isc-dhcp on legacy PXEboot.....

I've decided to go slow and use 192.168.0.x to test with.

Dhcpd.conf:

ddns-update-style none;
option routers 192.168.0.1;
option domain-name-servers 192.168.0.53;

(all the ipxe options)

option space ipxe;
option ipxe-encap-opts code 175 = encapsulate ipxe;
.
.
.
option ipxe.sdi code 40 = unsigned integer 8;
option ipxe.nfs code 41 = unsigned integer 8;

#subnet 192.168.0.0 netmask 255.255.255.0 {
# use-host-decl-names on;
# range 192.168.0.64 192.168.0.71;
# default-lease-time 3600;
# max-lease-time 86400;# class "iPXE" {
# match if option routers = "192.168.0.1";
# }
#}

subnet 192.168.0.0 netmask 255.255.255.0 {
use-host-decl-names on;
range 192.168.0.64 192.168.0.71;
default-lease-time 3600;
max-lease-time 86400;
}

host laptop1.test.net {
option domain-name "test.net";
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
next-server 192.168.0.1;
hardware ethernet 00:23:ae:14:a8:50;
fixed-address 192.168.0.21;
filename "boot/undionly.kpxe";
option iscsi-initiator-iqn "iqn.2012-06.net.test:target0";
option root-path "iscsi:192.168.0.1::::iqn.2012-06.net.test:target0";
# if exists user-class and option user-class = "iPXE" {
# filename "boot/undionly.kpxe";
# } else {
# filename "";
# option root-path "iscsi:192.168.0.1::::iqn.2012-06.net.test:target0";
# }
}

I installed the iscsi target from the laptop and made it the OS disk.
Everything went fine.

Now, I'm trying to PXEboot ye olde Dell Latitude 5500 laptop and I seem to be a wonderful circular loop. As can be seen above, I've tried the chainload (I think) to keep it from going into the PXE loop. (didn't seem to work).

Anyhow, it boots....

I get:

CLIENT MAC ADDR: 00 23 AE 14 A8 50 GUID <blather>
CLIENT IP: 192.168.021 MASK: 255.255.255.0 DHCP IP: 192.168.0.1
GATEWAY IP: 192.168.0.1
PXE->EB: !PXE at 9A22:0040, entry point at 9A22:00D6
UNDI code segment 9A22:4b50, data segment 966A:3B80
UNDI device is PCI 09:00.0, type DIX+802.3
601kB free base memory after PXE unload
iPXE initialising devices...ok

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

net0: 00:23:ae:14:a8:50 using undionly on UNDI-PCI09:00.0 (open)
[Link: up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 00:23:ae:14:a8:50)...... ok
net0: 192.168.0.159/255.255.255.0 gw 192.168.0.1 <--- Different Address???
Nothing to boot: No such file or directory (http://ipxe.org/2d03e13b)
No more network devices

Now, it seems it contacted the DHCP server a second time and got a different address? Why? (And how do I stop it from doing that?)

Also, when I go into the initial load where it says hit CTRL-B, I do so.

Everything looks good......

all the settings seem fine....

.
.
filename boot/undionly.kpxe
next-server 192.168.0.1
root-path iscsi:192.168.0.1::::iqn.2012-06.net.test:target0
.
.
.
latptop1.test.net
.
.
.
manufacturer Dell
product Latitude E5500
serial G08DXG1
.
.


So, how do I keep the settings it has on the first load and keep it from contacting DHCP again?

Thank you,

P.

rom-o-matic.eu fail on line 223

$
0
0
HI
I try to make RIOM ON rom-o-matic.eu, but fail on line 233
Can anyone help this?

wimboot - reach initrd image inside WinPE

$
0
0
Boot WinPE via wimboot like this:
Code:
#!ipxe
kernel wimboot
initrd boot/bcd         BCD
initrd boot/boot.sdi    boot.sdi
initrd sources/boot.wim boot.wim
initrd /scripts/dosomething.aspx somedata.dat
boot

Can I get the contents of somedata.dat inside WinPE? Somehow?
Is there any method to achieve this?

Problem creation KPXE image rom-o-matic.eu

$
0
0
Hello,

I tries to create new kpxe image in order to test another OS on boot on SAN.

I reuse my old script which was working, but now a have an error when i tried to compile it i on the website rom-o-matic.eu

My script is simple :


#!ipxe
dhcp net0
set keep-san 1
sanboot iscsi:192.168.1.245:::1:iqn.2016-04.windows10


here is the start of the error's report :

Build failed:

"make" unexpectedly returned exit value 2 at /var/www/ipxe-buildweb/build.fcgi line 233


Build log:
Path:
Parameters:
BINARY = undionly.kpxe
BINDIR = bin
DEBUG =
EMBED.00script.ipxe = #!ipxe
dhcp net0
set keep-san 1
sanboot iscsi:192.168.1.245:::1:iqn.2016-04.windows10
REVISION = master
Binary: undionly.kpxe
Binary directory: bin
Revision: master
Temporary embedded image directory: /var/tmp/ipxe-build/ipxe-embed-kbncye
Embedded image: /var/tmp/ipxe-build/ipxe-embed-kbncye/00script.ipxe
#!ipxe
dhcp net0
set keep-san 1
sanboot iscsi:192.168.1.245:::1:iqn.2016-04.windows10
Canonicalising revision master...


any idea???

Thanks for your great job :-)

Dark26

Error 0x420c6095 on default selection

$
0
0
Hi,

We have run into an issue we need some help with.
We have created a iPXE script that looks like this:

Code:
goto start

:start
menu iPXE boot menu
item --gap --           ------------------------- Operating systems ------------------------------
item vmlcus             Boot Vmware Esxi 6 installer
item --gap --           ------------------------- Advanced options -------------------------------
item config             Configure settings
item shell              Drop to iPXE shell
item reboot             Reboot computer
item --gap --           --------------------------------------------------------------------------
item exit               Exit iPXE and continue BIOS boot
choose --default vmlcus --timeout 5000 target && goto ${target}

:vmlcus
boot http://myserver.domain.com/esxi/mboot.efi ks=${testfile}

When we select the “vmlcus” menu item manually everything works perfect, but if we let the menu time out and it select the “vmlcus” menu item, we get this error:
http://i05652.dsv.com/esxi/mboot.efi... Error 0x420x6095 (http://ipxe.org/420c6095)
Could not boot image: Error 0x4206095 (http://ipxe.org/420c6095)

Why does it fail if the boot sequence a selected automatically by the time out?
Btw. We have read the 420c6095 article, but still it works if we select the item manually).[/quote]

Background not work on Microsoft VirtualPC

$
0
0
Because latest iPXE build not work in rom-o-matic.eu and in Linux i use iPXE from 2 March. I tested also the old version {png} Add support for PNG images. Both versions do not work in MS VPC 2007.
Command:
Code:
console -p dog.png
fails with the error: http://ipxe.org/err/2d8c203b
[Image: 7981142.png]
After build DEBUG=vesafb:3 have error:
[Image: 7809978m.png]
I tested different resolutions and different file type e.g. ipxe.pgm but still the same error.

vesamenu.c32 from PXELINUX work OK:
[Image: 7987305m.png]

rom-o-matic.eu and Linux build failed

[SOLVED] LoadImage in efi_image_probe fails on Lenovo ThinkPad Yoga 11e

$
0
0
Hi everyone,

we have another odd issue with one of these new devices (see thread subject). We try loading the kernel (version 4.4.x, EFI_STUB enabled!) via ipxe.efi and see this:
[Image: 1459493591647-c1.jpg]

I had the impression that maybe the kernel image got corrupted while transferring it via HTTP so we added imgverify trust check command and now we see this:
[Image: 1459777302441-8.jpg]

From my point of view this boils down to LoadImage call in efi_image_probe (image/efi_image.c) not being able to load that kernel image. So we tried to boot exactly this bzImage on a USB key as \EFI\BOOT\BOOTX64.EFI and guess what. I boots without an issue.

Has anyone an idea how to further debug this issue? Going to add EFI call debug next to see if we can get more information on where exactly LoadImage fails.

Thanks in advance!

Cheers
Sebastian

Background problem on GeForce2 MX400

NFS support for booting live ubuntu 15.04

$
0
0
hello ipxe team,
I am new user of ipxe
I've downloaded the last version of ipxe and made undionly.kpxe for chainloading with an embedded script :
#!ipxe
dhcp
set server_ip 192.168.1.75
set nfs_path /srv/nfs/ubuntu 15.04
kernel nfs://${server_ip}${nfs_path}/casper/vmlinuz.efi || read void
initrd nfs://${server_ip}${nfs_path}/casper/initrd.lz || read void
imgargs vmlinuz.efi root=/dev/nfs boot=casper netboot=nfs nfsroot=${server_ip}:${nfs_path} ip=dhcp splash quiet -- || read void
boot || read void

I've set up my nfs server service and it is okay I think
But when I want to set a client it replies that:
Could not start download: Operation not supported(http://ipxe.org/3c092003

Please answer me if ipxe supports nfs or not
Sorry for silly question

AMD Hyper-V fails to load iPXE ISO

$
0
0
Strange question here...

We have 3 Hyper-V Clusters running 2012 R2. Two clusters run Intel Processors and one runs AMD processors. When we try to boot a Hyper-V VM (Gen 1 or Gen 2, Legacy or Standard NIC), the iPXE ISO loads properly. However, when we try the same configuration on the AMD environment it hangs at "iPXE initializing devices....".

We've tried every configuration on the Hyper-V VM that we can think of and we can't get past this. We were able to get a gPXE ISO to boot to a Hyper-V Gen1 VM with a Legacy adapter on the AMD hypervisor.

Any thoughts or suggestions?

booting error when using code signing for linux kernel image

$
0
0
[Image: 5o34u38ryytb.jpg]
Hello ,

Image link : image link

We are trying to implement code signing while using ipxe.

Case 1 : We implemented code signing without enabling HTTPS. It worked.

Case 2: We turned on HTTPS option, embedded our private root certificate in ipxe binary, installed self-signed cert on our nginx server. As you can see in the screenshot, the fetching of our script "debian.ipxe" over HTTPS is successful. However, code signing seems to fail even after we get 'ok' for signature verification.

Please help. Thank you in advance.

New to iPXE, struggling with inconsistent sanboot connections

$
0
0
Hello everyone,

Let me start by saying thanks for your help and suggestions.

What I'm trying to achieve:
I have a fairly basic environment where I'd like to serve up 2-3 different ISOs, one of which is a Macrium Reflect recovery ISO, another is memtest86 (all things supported by iPXE), and maybe a diagnostic CD image or driver scanner.

These images would be served up to any PXE-based computer on a small network, and would include a short menu with the different choices available.

Where I'm at now:
At this point I am still figuring iPXE out, and trying to get some of the basics down before delving into more complicated aspects (e.g. building a menu, accounting for drive 0x80 parameters, etc.)

I have iPXE working at the moment, but it doesn't work every time (even on the same machine). I am only trying to load one ISO (Macrium) currently, and can get it to work if entered manually on the client machine (using Ctrl B).

[Image: 20160408_135814.jpg]

Once I get it working manually, it will work for the next few reboots, then go back to not finding the sanboot device (Nothing to boot: No such file or directory). The manual parameters that I enter are the same that I have listed in a text file that iPXE is supposed to read. Obviously I'm missing a key step(s) somewhere in here.

[Image: 20160408_135554.jpg]


Here is my dnsmasq.conf code:
Quote:no-resolv
dns-forward-max=1024
server=8.8.8.8
server=8.8.4.4
cache-size=4096
# dynamic pool for unknown clients, 140 addresses
dhcp-host=6c:e8:39:35:39:4d:9e,192.168.1.15
dhcp-range=192.168.1.150,192.168.1.240,infinite
dhcp-option=option:router,192.168.1.3
dhcp-option=6,192.168.1.15
dhcp-userclass=set:ENH,iPXE
dhcp-boot=tag:!ENH,undionly.kpxe
dhcp-boot=tag:ENH,http://192.168.1.15/ipxe.txt
enable-tftp
tftp-root=/var/www
log-dhcp

Note: my undionly.kpxe is in the www folder, which has not been edited.

And here is what I have in my ipxe.txt file:
Quote:#!ipxe
set sanboot-url http://192.168.1.15/
sanboot --no-describe http://192.168.1.15/macrium3.1.iso


Any thoughts or advice would be helpful.
Thanks!

Boot ISOs over network, it's possible??

$
0
0
Hi,

I set up a ipxe server, and it's great, but I wanted mostly to be able to install windows, some linux distros and other utilities.

The problem I found is I can't use the ISO directly, one "solution" would be to use memdisk to load the ISO to memory and boot from there, I read some linux distributions don't work.

I was thinking if any way to create a virtual disk over the network and appear as a real one. A lot of problems reside when a modern OS do a hardware test and try to find the memdisk, this is not found. Or we use a lot of ram for having all the iso in memory.

I think the problem can be splited in two questions:
1) Is any way or possible to create a virtual media that a hardware test find as an actual media?
2) If so I can assume we can make it to map the content to memory or a network media? (nfs,iscsi,AoE)

Thanks in advance! Smile

0xc000000d Win 7 x86 wim

$
0
0
The issue was described here:

https://www.mail-archive.com/ipxe-devel@...04095.html

I am facing exactly this, but my wim is only 140 Mb

2.52 is no go at all (is that a bug in 2.52 that makes it mostly unusable? - saying that, I have SCCM PXE ADK10 wims that ARE bootable via wimboot 2.52), if I try to use 2.52 I get

[Image: 2rdygew.jpg]

and beeping computer

With 1.06 I get Windows to start booting & then hangs on (non-descriptive) Windows Boot Manager 0xc000000d


I do DHCP undionly.0 --> PXELINUX 4.06 (for menu) & then swap to another server via

COM32 pxechn.c32
APPEND 10.0.0.55::undionly.0

and run wimboot via

KERNEL ipxe.lkrn
initrd wim-boot-W10.ipxe

RTL8168 driver not initialising

$
0
0
Hello Everyone
I'm doing something a little different booting IPXE from Windows XP with Grub4Dos as a bootloader. This is done using ipxe.lkrn as a menu entry in the Grub4Dos menu file and by passing an initial config file to ipxe through an initrd command

title ipxe
kernel (hd0,0)/ipxe.lkrn
initrd run.ipxe


and with run.ipxe containing (amongst others)

#!ipxe
dhcp

When booting like this (rebooting straight from xp and directly into ipxe )
the dhcp command fails with a timeout although ifstat shows the link open
However if I do the following
. Turn off the dhcp server
. reboot XP but press F12 during the boot process and select network boot
. let it fail
. turn the device off completely
. re-enable the dhcp server
. turn it on and through grub go straight to ipxe without ever letting XP boot
then dhcp gives me an address and everything works fine
Finally If I replace XP with Windows 7 there are never any problems going from Windows to ipxe. Everything inc the dhcp command works fine

I'm concluding that the XP driver somehow initialises something in a bad state that the Ipxe Realtek driver doesn't put back but the embedded ipxe stack on the network card does.
Anyone ever seen this or do you have any thoughts or ideas?
Thanks a lot
AndydeSheffield

How can I use ipxe without Tiny PXE Server

$
0
0
Hi devs,
First i'm sorry for my bad English.
I just want to use only ipxe without needed 3rd tool.
I booted VM from network then press Ctrl B to type command.
Follow demo guide, i type dhcp then chain to out demo.php (ipxe script). It work fine.
Since it work fine with our demo ipxe script, i try with my ipxe script on real machine.
I try to create a small menu.ipxe and put at root directory.
Run WM, boot from network then type command (see my screenshot)
It say that connection timed out.
I do not which step i did wrong. If i try 3rd tool (Tiny PXE server then menu.ipxe was configured by ipxe).
Please give me some hints. Tks
[Image: Capture.png]

Error in code signing using ipxe for Linux kernel

$
0
0
Hello ,
Please refer to the screenshot to see the error. The error code has no description on ipxe website.

Error screenshot

The error is http://ipxe.org/0216eb3c - This does not exist on ipxe site.


Here is what happened :

Case 1: HTTPs was not enabled on ipXE. We implemented code signing and it worked.

Case 2: We turned on HTTPS option. We created our own CA infrastructure, embedded the root certificate in ipxe binary and signed the nginx server certificate with our root certificate. Now, we are getting error in code signing.

Can anybody please help ?? THank you.

New to iPXE, struggling with inconsistent sanboot connections

$
0
0
Hello everyone,

Let me start by saying thanks for your help and suggestions.

What I'm trying to achieve:
I have a fairly basic environment where I'd like to serve up 2-3 different ISOs, one of which is a Macrium Reflect recovery ISO, another is memtest86 (all things supported by iPXE), and maybe a diagnostic CD image or driver scanner.

These images would be served up to any PXE-based computer on a small network, and would include a short menu with the different choices available.

Where I'm at now:
At this point I am still figuring iPXE out, and trying to get some of the basics down before delving into more complicated aspects (e.g. building a menu, accounting for drive 0x80 parameters, etc.)

I have iPXE working at the moment, but it doesn't work every time (even on the same machine). I am only trying to load one ISO (Macrium) currently, and can get it to work if entered manually on the client machine (using Ctrl B).

[Image: 20160408_135814.jpg]

Once I get it working manually, it will work for the next few reboots, then go back to not finding the sanboot device (Nothing to boot: No such file or directory). The manual parameters that I enter are the same that I have listed in a text file that iPXE is supposed to read. Obviously I'm missing a key step(s) somewhere in here.

[Image: 20160408_135554.jpg]


Here is my dnsmasq.conf code:
Quote:no-resolv
dns-forward-max=1024
server=8.8.8.8
server=8.8.4.4
cache-size=4096
# dynamic pool for unknown clients, 140 addresses
dhcp-host=6c:e8:39:35:39:4d:9e,192.168.1.15
dhcp-range=192.168.1.150,192.168.1.240,infinite
dhcp-option=option:router,192.168.1.3
dhcp-option=6,192.168.1.15
dhcp-userclass=set:ENH,iPXE
dhcp-boot=tag:!ENH,undionly.kpxe
dhcp-boot=tag:ENH,http://192.168.1.15/ipxe.txt
enable-tftp
tftp-root=/var/www
log-dhcp

Note: my undionly.kpxe is in the www folder, which has not been edited.

And here is what I have in my ipxe.txt file:
Quote:#!ipxe
set sanboot-url http://192.168.1.15/
sanboot --no-describe http://192.168.1.15/macrium3.1.iso


Any thoughts or advice would be helpful.
Thanks!

Emulate Media to boot ISOs over network, it's possible??

$
0
0
Hi,

I set up a ipxe server, and it's great, but I wanted mostly to be able to install windows, some linux distros and other utilities.

The problem I found is I can't use the ISO directly, one "solution" would be to use memdisk to load the ISO to memory and boot from there, I read some linux distributions don't work.

I was thinking if any way to create a virtual disk over the network and appear as a real one. A lot of problems reside when a modern OS do a hardware test and try to find the memdisk, this is not found. Or we use a lot of ram for having all the iso in memory.

I think the problem can be splited in two questions:
1) Is any way or possible to create a virtual media that a hardware test find as an actual media?
2) If so I can assume we can make it to map the content to memory or a network media? (nfs,iscsi,AoE)

Thanks in advance! Smile
Viewing all 1484 articles
Browse latest View live


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