similar to: Syslinux 4.10-pre15: now release track

On 25/10/15 01:04, Gene Cumm wrote: > On Sat, Oct 24, 2015 at 6:15 PM, Michael Brown via Syslinux > <syslinux at zytor.com> wrote: > >> Also, not a fork: http://git.ipxe.org/ipxe.git/commitdiff/8406115 > > A fork is a fork, regardless the reasons behind it (yes, I have some > understanding in this case). iPXE is based off of forking further > development as of a

Hi, I found this message in your online mail archive, i have found the same problem and did some research in the past on this. Maybe you would be interested to know it is a problem on any virtualisation product not just ESX. Second it is a problem in gPXE that you embedded in gPXElinux. The problem was build in gPXE after version 0.97 so any gPXElinux build a newer version has this problem. I

On Thu, Oct 10, 2013 at 10:00 AM, Michael Brown <mbrown at fensystems.co.uk> wrote: > On 09/10/13 10:45, Robin Smidsr?d wrote: >> >> On 09.10.2013 02:56, H. Peter Anvin wrote: >>> >>> The gPXE in the Syslinux tree is ridiculously old. We could either >>> replace it with iPXE or just drop it, giving people a recipe for how to >>> integrate

Hi Bootmeisters, I am using gpxelinux.0 + sanboot.c32 to boot a diskless machine into Linux. I would like to use device-mapper-multipath to provide fault tolerant access to its root disk. Although I am able to do this by hardcoding the additional paths in the initrd, it would be better if the bootloader could pass the information in the iBFT (iSCSI Boot Firmware Table). However, at the

Hello All. Yesterday I?m trying another ways but without luck. Issue still exist ? Please help. Is it possible to rewrite DHCP setting for sanboot.c32 after gpxelinux.0 load? Will be nice to have this possibility because: 1. DHCP can be ?black box?. 2. DHCP admin not available. 3. PXE server rewrite dhcp setting. I cannot boot from cdrom after pxe(gpxelinux.0) ? please help. LABEL Windows 7

Hi, I have a working PXE environment that chainloads gPXE and loads pxelinux.0 afterwards. As I'm also interested in doing san boot (in my case aoe) I tried loading the new gpxelinux.0 file instead of my gPXE --> pxelinux.0 setup (works) and booting from my aoe target by adding this to the default config file: LABEL doaoe MENU LABEL Continue AoE kernel sanboot.c32 append

Hi, I've been trying a couple of day now, but I can't seem to figure it out. On www.etherboot.org, I found the example of configuring gPXE so that it mounts an iSCSI lun and then boot from CDROM so you are able to install on the LUN. But if I use gpxelinux.0 (latest release 3.73), with sanboot.c32 like this: label sanboot2008srv menu label ^[iscsi] Windows server 2008 kernel

On Sat, Oct 24, 2015 at 6:15 PM, Michael Brown via Syslinux <syslinux at zytor.com> wrote: > Also, not a fork: http://git.ipxe.org/ipxe.git/commitdiff/8406115 A fork is a fork, regardless the reasons behind it (yes, I have some understanding in this case). iPXE is based off of forking further development as of a certain gPXE commit with some backporting of gPXE development to iPXE. --

On Thu, Mar 13, 2014 at 3:31 PM, Ian Bannerman <ian at internals.io> wrote: > Question, > > Some Linux distributions I support show two approaches for pxe booting them. One uses memdisk to boot an ISO file. The other uses pxelinux to boot kernel and initrd a squashfs file. > I'm unfamiliar with the impact to memory either approach has. Like, does using memdisk permanently

All, For several days, I've been trying to debug an issue booting a Windows 7 machine over iscsi (utilizing gpxelinux.0 and sanboot.c32). ? ??? - I can get it to function OK utilizing plain gPXE (so I know my iscsi config is OK and also the iscsi drive is OK). ??? - When utilizing gpxelinux, the system shows that the iscsi drive is mounting and trying to boot. However, at that point the

Hello again, * TFTP and DHCP started using: dnsmasq --port=0 \ --no-daemon \ --enable-tftp \ --tftp-root=/run/archiso/bootmnt \ --dhcp-range=192.168.0.2,192.168.0.254,86400 \ --dhcp-boot=/arch/boot/syslinux/gpxelinux.0 \ --dhcp-option-force=209,boot/syslinux/archiso.cfg \ --dhcp-option-force=210,/arch * and for DHCP+HTTP

Hi All, I've been trying to understand how to use pxechn.c32 to chain a local pxelinux menu item to a remote server which has it's own pxelinux hierarchy served via TFTP and HTTP. We have no control over DHCP next-server and filename fields so I wanted to exploit the "prefix" -p option that pxechn.c32 accepts. I spent a long time hitting my head against a brick wall until I

On Jun 29, 2014 9:37 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi Peter, > > I approached you before on this issue that I?m having with the SYSLINUX 6.03-pre18 when booting with iPXE option ROM. > > The issue was reproduced on different OEMs, and also on 2 different cards (Mellanox and Intel), with latest and 2 years old iPXE code. > > Just

For me the motivation for gpxelinux.0 was the HTTP support. If this would work reliably in newer versions then I could happily live without a iPXE-based pxelinux. On 9 October 2013 13:36, Ferenc Wagner <wferi at niif.hu> wrote: > "H. Peter Anvin" <hpa at zytor.com> writes: > > > The gPXE in the Syslinux tree is ridiculously old. We could either > >

I have a working pxelinux environment. I point the "boot server" (windows dhcp) to my tftp server and "Bootfile name" to pxelinux. How would I invoke the chain loader over iscsi? I was reading the following page and wondering if I could use gpxelinux to boot this? http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_xp_iscsi I saw examples of san boot here

Hi All, I've been enjoying playing with gpxe and gpxelinux, however I have a few questions that I'd love to get some answers for... 1) Will gpxelinux support chain loading of other NBPs without hanging or is this already resolved ? 2) Why does gpxelinux take much longer than pxelinux to enumerate the UUID, MAC address, then hex IP address chop ? 3) Can gpxelinux load gpxe scripts at all

I'm looking for either a way of setting the root path - a Linux style "pivot_root" functionality, that would be perfect. Also a way of overriding prefixing the root path with a URL or some other acceptable syntax to designate to use a different TFTP server. That would really make PXELinux really versatile. Some people concerned about security may want a way of blocking that just

On Jul 16, 2013 2:01 PM, "Alexandre Blanchette" <blanalex at gmail.com> wrote: > > On Tue, Jul 16, 2013 at 6:26 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > > On Mon, Jul 15, 2013 at 11:57 PM, Alexandre Blanchette > > <blanalex at gmail.com> wrote: > > > In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to >

On Tue, Jul 16, 2013 at 6:26 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Jul 15, 2013 at 11:57 PM, Alexandre Blanchette > <blanalex at gmail.com> wrote: > > In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to > use > > pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE > > script. > > > > The

On 24/10/15 21:57, Doug Scoular via Syslinux wrote: > 1. gpxe - a mothballed Network Boot Program but with a possibly problematic > and slow HTTP implementation. > 2. ipxe - an active fork of gpxe but still with the possibly problematic > and slow HTTP implementation (?) iPXE's HTTP implementation is definitely not slow. On a Gigabit LAN, you should get the full 1000Mbps speed