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

Can't install ESXI 5.1 and 5.5 on DL585 G7

December 6, 2015, 9:02 pm
$
0
0
Greetings!

We use iPXE to install various OS' on a number HP ProLiant server models. We are using iPXE from one of the latest releases: I built it out of commit 6847232e70f7 , and have a problem installing ESXi 5.1 and newer on the HP DL585 G7 model only.
The same ipxe binaries with the same ipxe script, mboot config and the kickstart file work fine on DL580 G7, but fail on DL585 G7.

The main difference between these 2 models are their processors:
DL585 G7 has AMD OpteronTM 6376 (2.3GHz/16-core/16MB/115W) Processor (doesn't work), and DL580G7 has Intel® Xeon® E7-4870 (2.40GHz/10-core/30MB/130W) Processor (works fine)

Here is the error message (can't attach a screenshot for some reason):
"Configuration error while parsing http://xxx.xxx.xxx.3:8000/de/boot/mboot/...32-484844e
Fatal error: 15 (Not found)"

The config file that it shows as not found actually exists, and I can open it in my browser. Also, the same exact setup works on DL580 G7.
Here is our ipxe script:
------
#!ipxe

# UUID: 35393532-3431-435a-3331-343933345450
# Command: deploy
# Task ID: 1742
# OS Family: ESX
set os_media_host xxx.xxx.105.21

set web_svc_address xxx.xxx.105.21


set install_uri http://${os_media_host}/installers/ESXI55//SP2/X64
set ks_uri http://${web_svc_address}:8000/de/kickstart/35393532-3431-435a-3331-343933345450
set pe_uri http://${web_svc_address}/installers/PE
set mboot_cfg http://${web_svc_address}:8000/de/boot/mboot/uuid/35393532-3431-435a-3331-34393334545


dhcp net0
imgfree
kernel -n mboot.c32 ${install_uri}/mboot.c32
imgargs mboot.c32 -c ${mboot_cfg}
boot mboot.c32
--------


Here is mboot_cfg file:
-----
bootstate=0
title=Loading ESXi installer
prefix=http://xxx.xxx.105.21/installers/ESXI55/SP2/X64/
kernel=tboot.b00
kernelopt=ks=http://xxx.xxx.105.21:8000/de/kickstart/35393532-3431-435a-3331-343933345450 BOOTIF=78:e3:b5:0c:67:ec
modules=b.b00 --- jumpstrt.gz --- useropts.gz --- k.b00 --- chardevs.b00 --- a.b00 --- user.b00 --- sb.v00 --- s.v00 --- misc_cni.v00 --- net_bnx2.v00 --- net_bnx2.v01 --- net_cnic.v00 --- net_tg3.v00 --- scsi_bnx.v00 --- scsi_bnx.v01 --- elxnet.v00 --- ima_be2i.v00 --- lpfc.v00 --- scsi_be2.v00 --- char_hpc.v00 --- char_hpi.v00 --- hp_ams.v00 --- hp_build.v00 --- hp_conre.v00 --- hp_esxi_.v00 --- hp_smx_p.v00 --- hpbootcf.v00 --- hpnmi.v00 --- hponcfg.v00 --- hpssacli.v00 --- hptestev.v00 --- scsi_hpd.v00 --- scsi_hps.v00 --- scsi_hpv.v00 --- net_igb.v00 --- net_ixgb.v00 --- scsi_mpt.v00 --- net_mlx4.v00 --- net_mlx4.v01 --- net_mst.v00 --- ima_qla4.v00 --- net_nx_n.v00 --- net_qlcn.v00 --- qlnative.v00 --- scsi_bfa.v00 --- scsi_qla.v00 --- ata_pata.v00 --- ata_pata.v01 --- ata_pata.v02 --- ata_pata.v03 --- ata_pata.v04 --- ata_pata.v05 --- ata_pata.v06 --- ata_pata.v07 --- block_cc.v00 --- ehci_ehc.v00 --- weaselin.t00 --- esx_dvfi.v00 --- xlibs.v00 --- ipmi_ipm.v00 --- ipmi_ipm.v01 --- ipmi_ipm.v02 --- lsi_mr3.v00 --- lsi_msgp.v00 --- misc_dri.v00 --- mtip32xx.v00 --- net_be2n.v00 --- net_e100.v00 --- net_e100.v01 --- net_enic.v00 --- net_forc.v00 --- net_vmxn.v00 --- ohci_usb.v00 --- rste.v00 --- sata_ahc.v00 --- sata_ata.v00 --- sata_sat.v00 --- sata_sat.v01 --- sata_sat.v02 --- sata_sat.v03 --- sata_sat.v04 --- scsi_aac.v00 --- scsi_adp.v00 --- scsi_aic.v00 --- scsi_fni.v00 --- scsi_ips.v00 --- scsi_lpf.v00 --- scsi_meg.v00 --- scsi_meg.v01 --- scsi_meg.v02 --- scsi_mpt.v01 --- scsi_mpt.v02 --- scsi_qla.v01 --- uhci_usb.v00 --- xhci_xhc.v00 --- tools.t00 --- xorg.v00 --- imgdb.tgz --- imgpayld.tgz
build=
updated=0
-------

Any help will be greatly appreciated.
Thank you!
↧
Search

Hyper-V VESAFB not work

December 8, 2015, 9:27 am
$
0
0
Hello,

I have tried configure CONSOLE_FRAMEBUFFER and starting a vm in Hyper-V the message is Could not configure console. I have enable DEBUG = vesafb and the error is vesafb could not get mode xxxx.

Is there any workaround?

All regards,
↧
↧

Burn IPXE on Intel NUC D54250WYKH2 (80861559.efirom)

December 8, 2015, 11:59 pm
$
0
0
Hi,

I followed this to build my 80861559.efirom, related to my Intel® Ethernet Connection I218-V card that seems to be integrated on my motherboard. In fact, I preferred at the end to use rom-o-matic to build it because I didn't get any issues with it. At the end, I followed the Intel IPXE doc and used Rufus to burn the specific dosboot.img to my USB key.

Is that right I can't burn 80861559.efirom to my Ethernet card with bootutil -nic 1 -restoreimage -file 80861559.efirom and that I need to mod my UEFI/BIOS to integrate IPXE on it?

Because when I did bootutil -e and pressed on TAB key, I didn't see any 80861559.efirom, but something like 808615..EFI and I couldn't anything with that file.

So, I'm asking if I have to use UEFI Bios Updater to mod my BIOS.

But I don't know how to use it...

Is chainloading finally the only way for my Intel NUC to use IPXE??

And I really don't know how to get a modded BIOS with an IPXE Option ROM instead of the classic LAN/PXE Option Rom. I really prefer IPXE. I have an Intel Visual BIOS FYI.

Any ideas?

Should I do with MMTool (I really don't know) and how? I'm lost. [Image: 1449832374.png]

Thanks in advance,
HLFH
↧

[howto] chainload wimboot

December 10, 2015, 6:12 am
$
0
0
Hello to everyone,

like the subject says I need to know if there is a way to chainload wimboot within an other bootloader.
The background of this question is that im currently writing my own bootloader that starts a WINPE over HTTP. In the last weeks I managed to start a bootmgfw.efi over PXE. And now I want to chainload the wimboot instead of the bootmgfw.efi and afterwarts let the wimboot start the WINPE over HTTP. Ist this possible? And what do I have to do?
I have no idea how to start with this and I hope someone of you could help me.

p.s. I'm very sorry but english is not my nativ language so please apologize if I did misspell some words.

Kind regards
Bowser
↧

Multiple Wim Or Variable Passing

December 17, 2015, 12:04 pm
$
0
0
Hi!

I know this has been asked in the past but I wanted to see if anyone had any new ideas. I have a bunch of images that are just slightly different, if I could pass varibles through wimboot, then I could have one image and a script that knew how to handle that. Or if I could attach a secondary wim that just had what I needed. Then I could have the one main image I maintain and a few small ones. Any ideas?

My only thought right now was to have a system checking to a webserver while booting a image, then once the image starts ask the webserver what the ipxe menu said.
↧
↧

Reversing iPXE burning to ROM

December 27, 2015, 1:13 pm
$
0
0
If I'm going to burn iPXE into my Mellanox InfiniBand ROM, is this process reversible?

Before doing so, can I save the existing ROM to a file? Would downloading Mellanox's flash image and applying it overwrite iPXE, or is that for a different ROM area?
↧

Cannot boot vmlinuz in efi

December 28, 2015, 1:57 am
$
0
0
Hello, I've recently cam across this problem when trying to boot an installation iso of RHEL 6.7
I can boot centos 7, fedora 22, and rhel 7 with no issues in EFI and legacy mode.
However i cannot boot RHEL 6.7, when ever i try to boot the kernel i get the error code 2e008081 (http://ipxe.org/err/2e0080)

If i burn the iso to a usb key i can boot in both EFI and legacy.

Any idea why this is happening (old kernel version?), i've also tried coping vmlinuz from RHEL 7 iso and boot it with the initrd.img of RHEL 6, it boots but cannot recognize any network devices.

My last effort was to try to chain BOOTX64.efi, but i can't seem to make it load the config file.

Here's my menu entry:

:rhel67server
echo Starting RHEL 6.7 Server x64
set repo ${http-images}/iso_images/RHEL_6.7_server
imgfetch ${repo}/images/pxeboot/vmlinuzboot
initrd ${repo}/images/pxeboot/initrd.img
imgargs vmlinuzboot repo=${repo} initrd=initrd.img
boot vmlinuzboot || goto failed

i used imgfetch because if i use kernel it will stop with an error, with imgfetch it will go to boot and if failed then return to menu. BTW all other menu entries are exactly like this and they all work in EFI/Legacy.
↧

skip unplugged network cards

January 5, 2016, 6:39 am
$
0
0
Hi, so after working with iPXE for the last few months and having a working environment the only thing that bugged me is having to wait for ipxe to try and configure every NIC that is present even if it's not connected.
So after getting a hint on the IRC channel i managed to make some modifications to the code and write a startup script that will skip unplugged NICs.

Note: only after I finished this i discovered that undionly or snponly doesn't have this issue, since they only use the NIC that made the actual PXE boot, but undionly downloads a little slower (300Mb took 2 seconds with ipxe.kkkpxe and 6 seconds with undionly, snponly vs ipxe.efi both download at the same rate)

So I figured I'll explain how to accomplish this so maybe it'll help others.

First of all some code needs to be added in net/netdev_settings.c and include/ipxe/settings.h.

netdev_settings.c:
find the following comment /** Network device predefined settings */
below it add:
Code:
const struct setting link_setting __setting ( SETTING_NETDEV, link ) = {
        .name = "link",
        .description = "Link status",
        .type = &setting_type_uint32,
};

add the following function (i added it before store MAC settings)
Code:
/**
* Fetch link setting
*
* @v netdev        Network device
* @v data        Buffer to fill with setting data
* @v len        Length of buffer
* @ret len        Length of setting data, or negative error
*/
static int netdev_fetch_link ( struct net_device *netdev, void *data,
                   size_t len ) {
    uint32_t link = netdev->link_rc;
    
    if ( len > sizeof ( link ) )
        len = sizeof ( link );

    memcpy ( data, &link, len );
    return sizeof ( link );
}

find the following comment /** Network device settings */ and below it add
Code:
{ &link_setting, NULL, netdev_fetch_link },

in settings.h somewhere between lines 420-460 add the following
Code:
extern const struct setting
link_setting __setting ( SETTING_NETDEV, link );

with those changes I can compile without any errors, now for the startup script (the script embedded with ipxe when building) I use the following one:
Code:
#!ipxe

set i:int8 0

:loop
set net-link:string ${net${i}/link}
iseq ${net-link} 0x0 && ifconf --configurator dhcp net${i} && goto boot || ifclose net${i}
inc i
iseq ${i} 10 || goto loop

:boot
chain http://192.168.0.1/boot/boot.ipxe || exit

:exit
echo Something went wrong, restart and try again

Now if you have multiple NICs or ports that are not connected, iPXE with skip those and only boot using the one that is up.

My knowledge with C isn't all that great, so I'm pretty sure the code can be made batter, with those changes when you write "echo ${net0/link}" you'll get either 0x0 (link up) or a sequence of numbers (like 0x141215) meaning link is down, this can probably be changes to show "Up" or "Down, but for me the current state is fine.

PS.
I've tried using ipxe.pxe and couldn't even get a 100mb link, max is 10mb, and at that speed booting is extremely slow, would love to find out why.
↧
Search

O

December 12, 2015, 4:43 am
$
0
0
New Asus laptop win10 certified in the efi settings (bios replacement) there is an option for the os to boot. windows 7 or Windows 8.x

I boot with secureboot enabled
-Memtest86 (commercialised version)
-wimboot winPE
-Grub2

Grub2 works with the windows7 option but not Windows 8.x that result in
http://ipxe.org/err/2e0081
All other options work.

Any ideas? Grub2 not yet signed for the new win10 hardware, is all I can assume. Anyone in a better position to know what gives.

PaulD
↧
↧

chainload with Win2012R2 problem

December 18, 2015, 6:18 am
$
0
0
Hi everybody

I'm new to iPXE. I configured my test environemt (Win2012R2, SCCM, IIS 8.5) according the howto's on ipxe.org.
So far, I get it to work that it boots up to iPXE but after that it can't find the files on the IIS. It says "nothing to boot".
However, if I press CTRL-F8 and enter "chain http://dc01/iPXE/sccm.ipxe" it downloads the wim file and after that I can start the SCCM task sequence.

So I suppose the problem lies in the configuration of my DHCP. Unfortunately, the howto here: http://ipxe.org/howto/msdhcp doesn't work on Win2012R2 anymore. The selection of the user class doesn't exist anymore. Because of that, I created a DHCP policy. But that doesn't seem to work. It doesn't matter if this policy is activated of not. If I boot into iPXE, I always get the error "nothing to boot".

If I can't solve this, I thought of using an embedded script like is is described here: http://ipxe.org/howto/chainloading
Is there any documentation on how and where I have to integrate a script like this?

Many thanks for your help.
↧

efi_x86_64_ipxe get ipv6 ip always time out

December 22, 2015, 6:15 pm
$
0
0
Dear

1. I setup ipxe server for datacenter. In the IPv4 environment the test system will boot into LiveOS successfully. However it will fail in IPv6 environment. Test system can get IPv6 ip in the PXE and can download ipxe.efi file. After Ipxe initial device, it can’t get IPv6 ip and always connection timed out.

We had try below methods
a. Disable cisco spanning tree mod
b. Using wireshark to log package, test system send correct DUID to server
c. Direct connect server and test system 10G sfp, it was still fail.
d. Use newest ipxe source code to build ipxe.efi.
e. Using the error message to search in the Web, however the solation was used in IPv4 environment

We had checked the ipxe driver support list, our device was supported. The card we use is Intel-x520-DA1. The most confused us was it was workable in the IPv4 environment. Because my dhcpd6 send IPv6 ip need more 30 sec to send IPv6 IP, but the ipxe was time out about 20 sec. I can't find out any surce code or configure to increase dhcp IPv6 time out sec.

Could you check the messages, is there anything we missing?

Below was the information when we build ipxe

a.The command using when I build ipxe.efi. I has enable "NET_PROTO_IPV6"
#cd /ipxe/src/
#make bin-x86_64-efi/ipxe.efi EMBED=ipxescriptfile

b.My embedded ipxe script <ipxescriptfile>
==============
#!ipxe
:retry
dhcp || ifconf -c ipv6 || ifconf -c dhcp net0 ||goto retry

time initrd http://[fc80::4]/initramfs.img
time kernel http://[fc80::4]/vmlinuz root=live:http://[fc80::1]/squashfs.img rootfstype=auto ro liveimg nodiskmount nolvmmount rd.luks=0 rd.md=0 rd.dm=0 keymap=us lang=en_US text console=ttyS0,57600n8 debug crashdump=128M initrd=\initramfs.img
boot

==============



c. My error message capture from test server
==============================
>>Checking Media Presence......
>>Media Present......
>>Start PXE over IPv6..
Station IP address is FC80:0:0:0:0:0:1Big Grin
Server IP address is FC80:0:0:0:0:0:0:4
NBP filename is ipxe.efi
NBP filesize is 872128 Bytes

>>Checking Media Presence......
>>Media Present......
Downloading NBP file...

Succeed to download NBP file.
iPXE initialising devices...ok




iPXE 1.0.0+ -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP TFTP EFI Menu
Configuring (net0 90:e2:ba:a3:f1:20) ........................... Error 0x040ee186 (http://ipxe.org/040ee186)
Waiting for link-up on net0 ... ok
Configuring [ipv6] (net0 90:e2:ba:a3:f1:20) .................. Connection timed out (http://ipxe.org/4c076092)
Waiting for link-up on net0 ... ok
Configuring [dhcp] (net0 90:e2:ba:a3:f1:20) ................................................ Connection timed out (http://ipxe.org/4c106092)
↧

How setup iPXE to skip dhcp root-path parameter on boot

December 24, 2015, 7:41 pm
$
0
0
Hello.
Merry Christmas!
I have the following issue: For my boot image needed option dhcp root-path for future use in the format of IP:/some/path/. But if my DHCP server returns it, iPXE trying to connect SAN device and receives an error - Could not open SAN device: Operation not supported (http://ipxe.org/3c092003).
Can I setup iPXE so that it skip and ignored the option dhcp root-path and continues to boot without attempting to open SAN device?
Best regards.
↧

SMSC Lan9512/lan9514 USB 2.0 10/100 Not working

December 28, 2015, 12:26 pm
$
0
0
I was able to use IPXE with different network cards; however, the above card does not work. The card is from Microchip and would appreciate if you can help out.

Thanks and regards,
↧
↧

How setup iPXE to skip dhcp root-path parameter on boot

December 28, 2015, 10:01 pm
$
0
0
Hello.

I have the following issue: For my boot image needed option dhcp root-path for future use in the format of IP:/some/path/. But if my DHCP server returns it, iPXE trying to connect SAN device and receives an error - Could not open SAN device: Operation not supported (http://ipxe.org/3c092003).
Can I setup iPXE so that it skip and ignored the option dhcp root-path and continues to boot without attempting to open SAN device?

Best regards.
↧

Synology iSCSI Disconnect Issues

January 2, 2016, 6:10 am
$
0
0
Hi all,

I'm in need of some help Dodgy

Over the last few days I've been trying to get iPXE connect to my Synology iSCSI target with little success. I want to do this so I can boot from SAN ESX in my lab.

So far I've configured the following...

Added DHCP options for undionly.kpxe to boot from tftp.
Embedded a script in undionly.pkxe to load a script from http.
The script contains the following

#!ipxe
sanboot -k iscsi:172.16.10.229::::iqn.test.com || chain http://172.16.10.230/pxelinux.0

Created pxelinux.cfg/default to point at a menu for the ESXi installation via http if sanboot fails.


When I attempt to boot a diskless host(VM in workstation at the moment) I see iPXE load and then the ESX installation starts. Which is all good but I dont get presented with an iSCSI lun to install into... Sad
I've looked at the iSCSI logs on the target I see Login, which is then followed by Close about 15 seconds later...

So at this point I'm not sure if the issue is with iPXE or the target. So I built a freenas iscsi target and I was seeing the same issue.

I've tried to make it was simple as possible by booting onto the ipxe.iso and running the following

dhcp
sanhook iscsi:172.16.10.230::::iqn.test.com

which responds with

Registered SAN device 0x80

but I still see the disconnect on the iSCSI Synology server about 5 - 15 seconds after.

I even tried a Freenas iscsi target and in the logs it gives me this
freenas WARNING: 172.16.10.127 (iqn.initiator.com): no ping reply (NOP-Out) after 5 seconds; dropping connection

Anyone got any ideas? Should what I'm trying to do work?

Thanks

James
↧
Search

UEFI Network Boot: loop and exec format error

January 6, 2016, 1:01 pm
$
0
0
Is there a resource I am overlooking for compiling and setting up a UEFI network boot through PXE? Otherwise, I am not sure what I am doing wrong. Any ideas?

Compiling myself:
When attempting to compile iPXE I don't get any errors, but when booting to the ipxe.efi file on the client I get a loop where it tries to download the file, succeeds and then tries to download again. There does not seem to be an error message or I am missing it. Compiled master from last change (Wed, 6 Jan 2016 12:55:08 -0600 (18:55 +0000)). Changing the config in config/general.h does not seem to make a difference, although, I have tried with changes and without. I may be missing something there.

Precompiled:
ipxe.efi downloaded from the bottom of the page here: http://ipxe.org/howto/chainloading

When I ctrl-b and run chain ipxe/menu.ipxe, then select CentOS 6.5 I get "Could not select: Exec format error (http://ipxe.org/2e008081)." Searching for the error I did not find anything. I tried this with a test CentOS menu item with http:// and nfs://.

Hardware:
HP DL60 Gen9
HP Ethernet 1Gb 2-port 361i Adapter
(up to date firmware as of 11/2015)

menu.ipxe:
Code:
#!ipxe

:start
menu PXE Client Menu
item centos65   CentOS 6.5
item netbootall Network Boot Multiple OS Test
choose target && goto ${target}

:centos65
kernel http://10.10.10.1/installs/centos-65-net/images/pxeboot/vmlinuz initrd=http://10.10.10.1/installs/centos-65-net/images/pxeboot/initrd.img
initrd http://10.10.10.1/installs/centos-65-net/images/pxeboot/initrd.img
boot

:netbootall
chain http://boot.salstar.sk

dhcpd.conf:
Code:
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

ddns-domainname     "domain.company.com";
ddns-rev-domainname    "in-addr.arpa.";
option domain-search "test.company.com";
option domain-name "test.domain.company.com";
option domain-name-servers 172.16.0.179, 172.16.0.177;
default-lease-time 604800;
max-lease-time 604800;
ignore client-updates;
authoritative;

## EFI options
option architecture-type code 93 = unsigned integer 16;

##iPXE Options
option space ipxe;
option ipxe-encap-opts code 175 = encapsulate ipxe;
option ipxe.priority code 1 = signed integer 8;
option ipxe.keep-san code 8 = unsigned integer 8;
option ipxe.skip-san-boot code 9 = unsigned integer 8;
option ipxe.syslogs code 85 = string;
option ipxe.cert code 91 = string;
option ipxe.privkey code 92 = string;
option ipxe.crosscert code 93 = string;
option ipxe.no-pxedhcp code 176 = unsigned integer 8;
option ipxe.bus-id code 177 = string;
option ipxe.bios-drive code 189 = unsigned integer 8;
option ipxe.username code 190 = string;
option ipxe.password code 191 = string;
option ipxe.reverse-username code 192 = string;
option ipxe.reverse-password code 193 = string;
option ipxe.version code 235 = string;
option iscsi-initiator-iqn code 203 = string;

# Feature indicators
option ipxe.pxeext code 16 = unsigned integer 8;
option ipxe.iscsi code 17 = unsigned integer 8;
option ipxe.aoe code 18 = unsigned integer 8;
option ipxe.http code 19 = unsigned integer 8;
option ipxe.https code 20 = unsigned integer 8;
option ipxe.tftp code 21 = unsigned integer 8;
option ipxe.ftp code 22 = unsigned integer 8;
option ipxe.dns code 23 = unsigned integer 8;
option ipxe.bzimage code 24 = unsigned integer 8;
option ipxe.multiboot code 25 = unsigned integer 8;
option ipxe.slam code 26 = unsigned integer 8;
option ipxe.srp code 27 = unsigned integer 8;
option ipxe.nbi code 32 = unsigned integer 8;
option ipxe.pxe code 33 = unsigned integer 8;
option ipxe.elf code 34 = unsigned integer 8;
option ipxe.comboot code 35 = unsigned integer 8;
option ipxe.efi code 36 = unsigned integer 8;
option ipxe.fcoe code 37 = unsigned integer 8;
option ipxe.vlan code 38 = unsigned integer 8;
option ipxe.menu code 39 = unsigned integer 8;
option ipxe.sdi code 40 = unsigned integer 8;
option ipxe.nfs code 41 = unsigned integer 8;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

subnet 10.10.10.0 netmask 255.255.255.0 {
  option routers 10.10.10.1;
  option subnet-mask 255.255.255.0;
  option broadcast-address 10.10.10.255;

## remove this when on dhcp proxy/relay
    option ipxe.no-pxedhcp 1;

  option domain-name "test.mbx.com";
    range 10.10.10.21 10.10.10.254;
    default-lease-time 1300;
    if option architecture-type = 00:09 {
      filename "ipxe/ipxe.efi";
      next-server 10.10.10.1;
    } elsif option architecture-type = 00:07 {
      filename "ipxe/ipxe.efi";
      next-server 10.10.10.1;
    } else {
      filename "bios/pxelinux.0";
      next-server 10.10.10.1;
    }
    option root-path "/srv/fsroot";
    ddns-update-style none;
  }
↧

How to use script when chainloading from UEFI GRUB

January 8, 2016, 11:39 am
$
0
0
Greetings,

I have a UEFI bootable USB stick which I want to use to load iPXE and run a custom script.
Here is the GRUB2 entry:

menuentry "iPXE"{
search --no-floppy --set=root -f /live/ipxe.efi
chainloader /live/ipxe.efi + 1
}

I have placed a plain text file script at /live/script.ipxe but it doesn't see the script. What do I have to do?

Thanks,
David
↧
↧

iscsi handoff problem

January 9, 2016, 2:26 am
$
0
0
Hello everyone,

I have a system that boots via iscsi just fine, but I need to point it to another target and port. The volume itself isnt changing, just the target name and port.

The target iqn and IP port number are changed in the ipxe config and from what I can tell, the system boots as expected... then when ipxe hands the iscsi session off to the OS, it loses the connection and the OS crashes.

My guess is that the handoff isn't passing the new port number and iqn.

I'm using fedora 23. I can't see where the OS stores the iscsi configuration. All those files are empty... probably because it inherits it from ipxe.

If I look at an strace of "iscsiadm -m session -P 3", I can see that it's pulling it's iscsi values from /sys/class/... -- unfortunately, that structure is dynamically built when the system boots so I can't edit the files there.

So, how can I get the port number change to pass through? I'm moving from port 3160 to 44301.

Any help would be appreciated.

Thanks to you all in advance.
-Michael
↧

iSCSI boot black screen after Win logo

January 12, 2016, 8:22 am
$
0
0
Hi,

I'm trying to boot win7 from an iSCSI target. As I should do with the help of WinPE I installed Win7 adn after the installation as requested I rebooted. The problem is after the Windows logo I can see black screen and I can do nothing except Ctrl+Alt+Del wich occurs reboot.
Please give me some idea(s) how can I solve this problem.

Thank xou in advace
↧

Blank Screen ESX5.1 VMWare V9

January 14, 2016, 9:23 am
$
0
0
Hi,

We've stumbled across a bit of a strange problem resulting in blank screen when building Windows 2012 server during the WINPE stage of the build process.

Components involved are iPXE, WIMBoot 5.1, ESX 5.1, Virtual Machine hardware version 9, WINPE 5.1, Windows 2K8 WDS, Windows Server 2012.

The problem seems to occur when WIMBoot calls winload.exe from WINPE 5.1 - the display goes blank but the build continues as normal, just can't be seen! using Virtual Hardware Version 8 works with no issues, it's only when we select VM version 9 in vCenter as the virtual machine does it become a problem. It smacks of VMware driver issues in WINPE, but the latest drivers have been injected into the PE WIM.

Anyone seem anything similar? any help appreciated Smile
↧
Viewing all 1484 articles
Browse latest View live
Search