wimboot, I'm stumped

January 11, 2014, 5:46 pm

≫ Next: wimboot MDT generated WinPE 5 with wimboot

Im hoping i'm missing something particularly trivial here, I cant find the disconnect.

I didnt want to install iPXE directly on my networking card, so i settled on chainloading. I have my TFTP server set up, and can successfully PXE boot, pull the undionly.kpxe, and get to the IPXE> command line from ctrl + B.

from there, I decided for now i would manually direct to which setups i wanted to do until i better understood how to configure menus. I have my windows 7 installation media all unpacked and in a folder on a web server. (address 192.168.1.10/Win7) permissions are all set and i can access.

I followed the wimboot instructions and set up an boot.ipxe file *well, i named it W7.ipxe). So from the IPXE> command line i type the following and it hangs. so maybe its something in my W7.ipxe file?

Code:

IPXE> dhcp 

configuring (blah blah blah)

IPXE> chain http://192.168.1.10/Win7/W7.ipxe

http://192.168.1.10/Win7/W7.ipxe... ok

_

W7.ipxe is below (note ive tried using relative paths... my install files are in server/Win7/W7, ive tried moving them to server/Win7)

Code:

#!ipxe

  set wimboot-path http://192.168.1.10/Win7

  kernel ${wimboot-path}/wimboot

  initrd ${wimboot-path}/W7/bootmgr          bootmgr

  initrd ${wimboot-path}/W7/boot/bcd         BCD

  initrd ${wimboot-path}/W7/boot/boot.sdi    boot.sdi

  initrd ${wimboot-path}/W7/sources/boot.wim boot.wim

  imgstat

  boot

is something wrong with my file that i'm missing?

as an example, I tried this, with success:

Code:

IPXE> dhcp 

configuring (blah blah blah)

IPXE> chain http://boot.ipxe.org/demo/boot.php

If i need to give more information, i gladly will. I'm at a loss for ideas..

Thanks for any help i can get!

↧

wimboot MDT generated WinPE 5 with wimboot

January 16, 2014, 8:49 am

≫ Next: ipxe iscsi boot fails, even in virtualbox

≪ Previous: wimboot, I'm stumped

Hi everyone,

I'm using Microsoft Deployment Toolkit (MDT) to generate Litetouch wim files. I utilize wimboot for PXE purposes. This all worked great until the latest version came out. MDT 2013 create WinPE 5 wim files based on Windows 8.1. The first problem is the decompression of bootmgr. That I've fixed by replacing it with an extracted version as per the instructions on the FAQ page. It now tries to boot into the wim file but that results in a BSOD with the error: A required device isn't connected or can't be accessed (0xc000000f).

The funny thing is that MDT also creates an ISO using the same wim file and bootfiles that I used for wimboot and when I use memdisk to boot the ISO all works fine.

Thoughts anyone?

↧

ipxe iscsi boot fails, even in virtualbox

January 16, 2014, 1:46 pm

≫ Next: How do I know the dhcp server's address in the shell

≪ Previous: wimboot MDT generated WinPE 5 with wimboot

Hi,

I set up an iscsi server running iscs-dhcp-server and tftpd-hpa.
At boot I get the following screen:

[Image: iscsi_boot.jpg]

allow booting;
allow bootp;
ddns-update-style none;
log-facility local7;
default-lease-time -1;
max-lease-time 7200;
authoritative;
option space ipxe;
option ipxe-encap-opts code 175 = encapsulate ipxe;
option ipxe.keep-san code 8 = unsigned integer 8;
option ipxe.bus-id code 177 = string;

subnet 10.0.0.0 netmask 255.255.0.0 {
use-host-decl-names on;
range 10.0.0.164 10.0.0.192;
#option routers 10.0.0.111;

that's my dhcpd.conf

option domain-name-servers 10.0.0.1;
option broadcast-address 10.0.255.255;
option root-path "10.0.0.111:/var/lib/tftpboot/";
next-server 10.0.0.111;
if not exists ipxe.bus-id {
filename "undionly.kpxe";
option routers 10.0.0.1;
} else {
filename "";
option root-path "iscsi:10.0.0.111:::1:iqn.2013-09.at.lightserver.empower:windows";
option ipxe.keep-san 1;
option routers 0.0.0.0;
}
server-name "empower";
server-identifier 10.0.0.111;
}

but however windows 7 doesn't come up, the boot process quits with a bluescreen.
My router is running is OpenWRT. Do I have to set something special to enable iscsi boot?
I found a guide here > etherboot.org/wiki/sanboot/win2k8_iscsi_install < but the rule

iptables -A forwarding_lan -i br-lan -o br-lan -j ACCEPT

brings an error:

iptables: No chain/target/match by that name.

So I checked with ifconfig:

ifconfig
br-lan Link encap:Ethernet HWaddr A0:F3:C1:78:07:C0
inet addr:10.0.0.1 Bcast:10.0.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8677375 errors:0 dropped:5180 overruns:0 frame:0
TX packets:13955772 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1039227257 (991.0 MiB) TX bytes:17619986844 (16.4 GiB)

Is it very likely OpenWRT is blocking required packet exchange? iptables v1.4.20

best regards

↧

How do I know the dhcp server's address in the shell

January 23, 2014, 12:18 am

≫ Next: If statement based on IP address?

≪ Previous: ipxe iscsi boot fails, even in virtualbox

I have enter the ipxe‘s shell , I want to know the DHCP SERVER's address, is there some command can tell me this?

I use the PXE to load the ipxe, and then I want to use ipxe load the vxworks’ bootrom, the bootrom is stored on the dhcp server, so I want to know the dhcp server's address. Please help me , thanks very much：）

I‘m a CHINESE， my English is not so good, I hope you can understand what I said Big Grin

↧

If statement based on IP address?

January 23, 2014, 7:23 am

≫ Next: no physical memory for windows boot manager

≪ Previous: How do I know the dhcp server's address in the shell

Is there a variable for subnet? I'm trying to point to different chain scripts depending on the subnet from which the request originates.

Something like this:

Code:

#!ipxe

dhcp

goto ${subnet} || goto unknown

:192.168.0.0

chain http://server1/boot.ipxe

:172.29.28.0

chain http://server1/boot.ipxe

:unknown

boot tftp://server3/pxelinux.0

↧

no physical memory for windows boot manager

January 29, 2014, 11:12 am

≫ Next: iPXE broken with B75M-GL / rtl8111e?

≪ Previous: If statement based on IP address?

I'm getting an error when trying to boot to the local hard disk. The error is: "No physical memory is available at the location required for the Windows Boot Manager. The system can not continue.". This is on an HP bl460c G8 blade server with an Emulex NIC.

I am using the sanboot trick. If I simply exit, iPXE exits the PXE ROM, and then the machine gives the RSOD (red screen of death) with Illegal Opcode.

I am running BIOS version 9/8/13.

Bizarrely, the same machine can boot WinPE (using wimboot) - but not the local disk.

I have another blade server - a bl465 G0 with a Broadcom NIC that will boot just fine.

I've also got a VMware VM that will boot just fine.

I wonder if I am trying to do too deep of a chain?

I am using undionly.kkpxe with an embedded script:

Code:

#!ipxe

dhcp

chain http://awebsite/boot.php

which returns

Code:

#!ipxe

sanboot --no-describe --drive 0x80

Thoughts? Suggestions?

↧

iPXE broken with B75M-GL / rtl8111e?

February 1, 2014, 4:35 am

≫ Next: iPXE Menu loses video

≪ Previous: no physical memory for windows boot manager

I'm attempting to run iPXE on a B75M-GL board (ASRock). It uses the Realtek 8111E adapter.

I get the "iPXE Initializing devices" then the machine reboots.

I have tried each loading undionly.kpxe, ipxe.pxe, and rtl8168.pxe over tftp and off USB. Everything does the same thing, it gets to initializing devices then reboots. I tried both with the legacy net-boot and UEFI net-boot with the same results.

Any ideas?

↧

iPXE Menu loses video

February 1, 2014, 9:19 am

≫ Next: compiling bin-i386-efi/snponly.efi

≪ Previous: iPXE broken with B75M-GL / rtl8111e?

I have an iPXE menu script set up that works great on most hardware. However, on certain hardware, specifically anything with an Intel Cedarview based chipset, it fails. When the script gets to the menu portion ("choose" command), the screen goes blank and the system becomes unresponsive. I've also confirmed the same symptom by simply entering the "config" command.

At first, I thought the problem was that the menu was outputting only to the LVDS connector, a known issue with Cedarview on Linux. However, I also don't get any output on the serial or syslog consoles.

Any advice on this issue would be appreciated.

↧

compiling bin-i386-efi/snponly.efi

February 1, 2014, 2:33 pm

≫ Next: iPXE iSCSI sanboot unreliable with 82573L at 1Gbit

≪ Previous: iPXE Menu loses video

I am trying to compile bin-i386-efi/snponly.efi for booting a early mac mini and I am getting a huge number of errors regarding relocation truncation. I assume this means there are too many components selected. Is this the case? if so what should I disable?

Code:

[LD] bin-i386-efi/snponly.efi.tmp

bin-i386-efi/blib.a(librm.o): In function `p2r_jump_vector':

(.data16+0x3e): relocation truncated to fit: R_386_16 against `.text16'

bin-i386-efi/blib.a(librm.o): In function `init_librm':

(.text16+0x8): relocation truncated to fit: R_386_16 against `.data16'

bin-i386-efi/blib.a(librm.o): In function `init_librm':

(.text16+0xe): relocation truncated to fit: R_386_16 against `.data16'

bin-i386-efi/blib.a(librm.o): In function `init_librm':

(.text16+0x16): relocation truncated to fit: R_386_16 against `.data16'

bin-i386-efi/blib.a(librm.o): In function `init_librm':

(.text16+0x21): relocation truncated to fit: R_386_16 against symbol `rm_cs' defined in .data16 section in bin-i386-efi/blib.a(librm.o)

bin-i386-efi/blib.a(librm.o): In function `init_librm':

(.text16+0x28): relocation truncated to fit: R_386_16 against `.data16'

bin-i386-efi/blib.a(librm.o): In function `init_librm':

(.text16+0x35): relocation truncated to fit: R_386_16 against `.data16'

bin-i386-efi/blib.a(librm.o): In function `init_librm':

(.text16+0x3e): relocation truncated to fit: R_386_16 against symbol `rm_ds' defined in .text16.data section in bin-i386-efi/blib.a(librm.o)

bin-i386-efi/blib.a(librm.o): In function `init_librm':

(.text16+0x45): relocation truncated to fit: R_386_16 against `.data16'

bin-i386-efi/blib.a(librm.o): In function `init_librm':

(.text16+0x52): relocation truncated to fit: R_386_16 against `.data16'

bin-i386-efi/blib.a(librm.o): In function `init_librm':

(.text16+0x56): additional relocation overflows omitted from the output

make: *** [bin-i386-efi/snponly.efi.tmp] Error 1

↧

iPXE iSCSI sanboot unreliable with 82573L at 1Gbit

February 6, 2014, 5:15 am

≫ Next: Console command inside and outside a virtualbox

≪ Previous: compiling bin-i386-efi/snponly.efi

Hello,

first of all, iPXE is a real, cool and fancy bootloader. Good work @ devel.

But, we got a big problem if we try to boot a Windows (7,8, 2008 (R2) or 2012 (R2)) on a mainboard equiped by an Intel 82573L NIC chipset.
Here are the symptoms.
We boot into an iSCSI target LUN , install Windows on it, everthing is fine. The installation succeeds. But then, some times, an iSCSI boot failed. The next iscsi boot works fine again, on the same machine, the same target, the same ipxe loader. It is impossible to say when will this boot succeeds of fails.

Deeper investigations showed that the problem only occurs if the link speed of the iscsi client interface is 1 Gbit/s. This problem only occurs on mainboards with the specified NIC 82573L, any other Intel NIC works without any problems. One workaround is to tear down the speed to 100 Mbit at boot time. Because as long as the speed is at 100 Mbit during the boot of Windows, it is safe to go up to 1Gbit while Windows is running.
Furthermore, we could see on tcp dumps that the iSCSI traffic suddenly stops without any idea why, when the boot failed. The iSCSI client stops to send iSCSI read requests.

So, as discussed in http://forum.ipxe.org/showthread.php?tid...ight=speed it would be a fix for us to set the link speed hard to 100 Mbit at iPXE boot time. Or, does anyone have any other idea to kill this bug or a better workaround? I hope it's obvious that changing the port speed at switch level everytime a boot occurs can't be a fix.
I'm looking forward to hearing of someone who wants to help me Smile

If any further information is needed, I will provide them.

↧

Console command inside and outside a virtualbox

February 11, 2014, 10:59 pm

≫ Next: ipxe timeout

≪ Previous: iPXE iSCSI sanboot unreliable with 82573L at 1Gbit

I'm having issues getting the console command to work consistently actually, and I thought this may be the most relevant topic to post on.

At present, I can use the console command just fine in a virtualbox VM, however none of my actual PCs seem to be able to do it.
For example, using the command: console -x 1024 -y 768
Results in a "No such file or directory" error 0x2d8c203b

Merely using the command alone does reset the screen, but attempting to use any parameters at all results in the "No such file or directory" error.
I've tried using the DEBUG=console:3 in the build parameters, but I'm not getting any more output than normal from it :/
Any ideas?

My build command is: make clean bin/ipxe.lkrn EMBED=script.ipxe
Are there any hints even how to enable debugging of this command (so it prints stuff out etc.)

↧

ipxe timeout

February 12, 2014, 11:20 am

≫ Next: Install iPXE on HDD as default bootloader

≪ Previous: Console command inside and outside a virtualbox

Hi,

While wrestling with pxe I suddenly came accros gpxe and not much later accross ipxe, so I was relieved and enthusiastic that something better than pxe finally showed up !!

It had been a struggle to get everything finally working, but with ipxe I'm still not getting through.

With gpxe I managed to get several scripts loading untill it wanted to load a menu and then it just hangs on a real pc, the virtualbox crashes with an error message (so the app, not the machine).

With ipxe I can't get past the stage where it loads the chained script from http or nfs.
I keeps throwing the same error 040ee119, which I believe is an tftp time-out ?
But even when I enter the command prompt and run ipconf or dhcp it returns the same error.

What could be wrong ?
(What config files do I post ?)

↧

Install iPXE on HDD as default bootloader

February 13, 2014, 7:50 pm

≫ Next: Load iPXE in DomU of Xen

≪ Previous: ipxe timeout

Hi,

Is there a way to install iPXE to the MBR of the HDD, so that iPXE can behave as the default bootloader to replace GRUB?

I believe this can be achieved. Can anyone share some hints?

Thanks!

↧

Load iPXE in DomU of Xen

February 18, 2014, 9:07 pm

≫ Next: ipxe/memdisk/http iso - Only rebooting

≪ Previous: Install iPXE on HDD as default bootloader

Hi All,

Is there a way to chainload ipxe.lkrn in the DomU of Xen?

I saw a supporting request posted in the ipxe developing mailing two years ago. And I did the same test by letting pvgrub to load ipxe.lkrn and get the expected following error.

xc: error: panic: xc_dom_bzimageloader.c:655: xc_dom_probe_bzimage_kernel: boot protocol too old (0207): Invalid kernel
xc: error: panic: xc_dom_core.c:621: xc_dom_find_loader: no loader found: Invalid kernel

That supporting request also pointed out that iPXE needs to be built as a bzImage instead of a zImage and a new driver will be needed for Xen virtual network interface (netfront). Is there anything else we need to consider if we want to load ipxe.lkrn in DomU?

Thanks in advance!
Cheng

↧

ipxe/memdisk/http iso - Only rebooting

February 14, 2014, 5:21 am

≫ Next: samba/CIFS support

≪ Previous: Load iPXE in DomU of Xen

Hi guys,

I'm hoping someone can help me with an issue..

I'm using a usb drive to boot into syslinux. From there I can boot multiple ISO files from the USB correctly using memdisk

However, I also have some ISO's online. So I let syslinux boot into ipxe, it gets dhcp address, it downloads the files, and than, it just reboots. FOr about half a second there is some text scrolling, but to short to read anything.

I've tried several methodes of booting, but all have the same issue, on multiple PC's.

The code used:
#!ipxe
dhcp
initrd http://.../linux/debian-live-7.1-amd64-standard.iso
chain http://.../memdisk iso raw

Has anybody seen this before, or have a possible solution?

↧

samba/CIFS support

February 19, 2014, 7:54 am

≫ Next: How iPXE detect PCI version?

≪ Previous: ipxe/memdisk/http iso - Only rebooting

Hi all, firstly I want to say that you all did a nice job on iPXE, it works really great. I have used it for some private projects but now we are switching deployment environments at work. We are trying to change to a new process kickstarted by iPXE. Currently we have the ISO's we want to boot set up on a web-server, but this is not the original locations of the ISO's; those are actually located on a samba share. So we were wondering if it is possible for iPXE to boot from samba/CIFS instead of http/nfs. Searching through the documentation and forum did not turn anything up for me except that nfs is supported. Being able to boot from a share removes the hassle of copying the ISO's every time we make a change to one of them, which happens fairly often. Thanks in advance for all the help you can offer, it is greatly appreciated!

↧

How iPXE detect PCI version?

February 20, 2014, 5:41 am

≫ Next: Sanboot with sanhooked drive?

≪ Previous: samba/CIFS support

I know that while PC boot from iPXE ROM this displays PCI version like this:

Code:

iPXE (http://ipxe.org) 00:04.0 C100 PCI2.10 PnP...

This means that PCI version is PCI2.1 right? How iPXE check this?

↧

Sanboot with sanhooked drive?

February 23, 2014, 11:59 pm

≫ Next: undionly.kpxe and windows7 load problem

≪ Previous: How iPXE detect PCI version?

Hello,

Is it possible to sanboot Windows OS with sanhooked 2nd drive?

sanhook --drive 0x81 iscsi-target
==> this will be D: drive under Windows
sanboot iscsi-target
==> this will be C: driver under windows

I did quick test but didn't make it work.
is there any way to achieve this?

Thank you in advance.

↧

undionly.kpxe and windows7 load problem

February 25, 2014, 12:23 pm

≫ Next: BUG in undionly.kpxe

≪ Previous: Sanboot with sanhooked drive?

First of all thank this fantastic project. I have a problem when undionly.kpxe use to boot windows7 home (linux debian work fine). This screen is locked and the computer reset.
if I use the iso http://boot.ipxe.org/ipxe.iso works perfectly. Start ipxe.krn, dhcp send http://iscsi.informaticaamado.lan/boot.ipxe, load boot.ipxe.cfg, menu.ipxe and boot iscsi.
I've noticed that when I'm using RTL8169 ipxe.krn charge and otherwise undionly driver
What I'm doing wrong?
Thanks and regards.

↧

BUG in undionly.kpxe

February 25, 2014, 3:37 pm

≫ Next: Problems with Asus Z87-K MB: NIC Does not reset after boot

≪ Previous: undionly.kpxe and windows7 load problem

I have came across a bug in undionly.kpxe ( the latest version ) and would like to draw your attention to it if I may, here is the situation :

DHCP Server : ISC DHCPd
OS : Centos 6.5 as a KVM Host
Hardawre : DELL Poweredge 2950

DHCP Server : ISC DHCPd
OS : Centos 6.5 as a KVM Host
Hardawre : SuperMicro

issue :
When trying to boot a VM from iPXE on the DELL it causes the VM to enter a Paused state where it will not be reset.

Troubleshooting steps :
1-) New VM was created with new HDD on both hosts.
2-) Trying boot from the SuperMicro Host ( Issue DOESN'T exist )
3-) Trying to boot from the DELL Host ( Issue EXISTS )
4-) Booting from the older version of undionly.kpxe on both hosts works well.
5-) Booting from VMware Workstation ( Issue DOESN'T Exist )

Please look into this issue and let me know what is it and how to remedy it.
right now I am just using the older version of undionly.com

Thank you

↧