similar to: pxelinux boot problem in qemu

Hi, As requested on IRC, here are the step-by-step instructions to reproduce the failure I see: On http://rom-o-matic.net/gpxe/gpxe-1.0.1/contrib/rom-o-matic/build.php: output format: .dsk NIC type: e1000_82540 x CONSOLE_PCBIOS x CONSOLE_SERIAL BANNER_TIMEOUT: 20 COMCONSOLE: 0x3F8 _ COMPRESERVE COMSPEED: 57600 COMDATA: 8 COMPARITY: 0 COMSTOP: 1 x DOWNLOAD_PROTO_TFTP x DOWNLOAD_PROTO_HTTP _

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 > >

Hi, I'm in the position that a network console would occasionally be very useful for me to control pxelinux. Has the possibility of adding it (next to VGA and serial) been ever discussed? I understand that it may sound somewhat contorted, but it could also serve instead of a TFTP PUT for extracting hardware info, for example... How hard would it be to add (considering gPXE as well)? --

I have been looking at the etherboot site and at the syslinux/pxelinx sites trying to figure out how to use gpxe, and I am a bit confused. :) In a nutshell, I simply want to use http to grab the config and messages files. (I need those files to be dynamic.) I tried just replacing pxelinux.o with gpxelinux.0. But, gpxe complains (A LOT) about unrecognized commands. I can't find a simple

Hi All, Sorry if this is a stupid question, but I've managed to get pxelinux to load gpxe and then manually load linux by using the gpxe command line and HTTP for the kernel and initial ram disk. My question is whether it is possible to somehow pass gpxe commands through some mechanism other than the DHCP filename response. Since I don't have control over our DHCP infrastructure, but do

Hello everyone I am experiencing problems with PXELinux/gPXE when netbooting using HTTP. The problems I encounter: - When the intel bootROM is sending out a DHCPDISCOVER it might not recieve an IP address, but the server did send out a OFFER. Capturing packets reveals the packets have been sent, and the client _should_ have recieved it. But when it passes that stage: - When the gPXE bootROM is

Hi, I'm investigating using LTSP for thin clients at my place of work, and I've encountered a problem that I don't know how to approach. I don't know if the problem is with gPXE, PXELinux, or the LTSP kernel, but I think PXELinux is probably the right level to investigate it. My situation is as follows: I've installed the LTSP system from Ubuntu Gutsy. I've tested it

Hi , Thought I would keep the same topic as a previous post in June - still is a problem with pre49 Setting dhcp options 209 and 210 is breaking gpxe/pxelinux - everything else being the same, it works fine in 3.86 and not 4.00. ..Inserting following into pxelinux.gpxe ... set 209:string pxelinux.cfg/default set 210:string http://xxxxxxxx.xxx.xx.uk/pxe/ It is hanging with 'Trying to

I'm using gpxe to chain to pxelinux on a different host than gpxe was loaded from. The chain command looks like this chain tftp://other-host/pxelinux.0 Unfortunately, pxelinux is ignoring other-host and going back to the original host to look for its files. Is there any way to alter this behavior? Thanks, Mike

Hi Hpa and all I am confused about some function of pxelinux and gpxelinux/gpxe. 1, after I read the document (http://edgyu.excess.org/ols/2008/H%20Peter%20Anvin%20-%20x86%20network%20bo oting%3a%20integrating%20gPXE%20and%20PXELINUX.pdf), I knew there are two major module in standard gPXE, PXE BC and UNDI. And I can understand why I need to produce different boot file for different NIC from

Hi, This is the first time I use syslinux mailing list, so I am sorry if I have made any mistake. Well, I follow this post : http://www.linuxbyexamples.net/2012/08/boot-winxp-from-http-server.html and I can successfully boot into winxp using gpxelinux.0 loading vhd image through http. This works well. But when the vhd image getting bigger than 512MB (I added some more files into the image),

Hey, It is some real awesome work you are doing. Thanks. I have been trying to use gpxe - pxelinux to boot Linux from a remote location. It works with pxelinux 2.02 and lower. However pxelinux 2.03 and higher return errors and booting is incomplete. Why? syslinux-3.00 gives the following dump and hence the system does not boot. Loading Linux...........................................Ready.

Hello everyone, I have just released SYSLINUX 3.71. This is pretty much a bug fix and hardware support release. The major new *features* are the "initrd" command (syntactic sugar, but it supposedly makes it easier for some tools), the "hide" option to chain.c32, and the ifcpu64.c32 module. As always, special thanks to rPath, Inc., my employer, for the countless hours I

I am using gPXE 1.0.0 to boot PXELINUX 3.86 over HTTP without problems, but when I switch pxelinux.0 3.86 with 4.00-pre47, I get ?Unable to locate configuration file?. Is HTTP booting not working with 4.00, or is some special compile/settings needed?

On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > Now I have something I can reproduce. Booting my same ipxe.iso to > perform an initial TFTP load shows what I saw already. Attempting to > load a file via http results in an immediate error message with no > resulting traffic as far as I can see. OK. Found it. core/fs/pxe/pxe.h disabled all of the

"H. Peter Anvin" <hpa at zytor.com> writes: > 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 with iPXE themselves. > > What do people think? Do you mean a recipe for creating [gi]pxelinux.0 or for deploying iPXE and using pxelinux on top of that? Is there any

OK, 6.01 is now out. The main intention of this release was to fix the terrible bug in Syslinux 6.00 which made it impossible to boot kernels from BIOS. This resulted in a way shorter than usual release cycle, and it does mean that there are some bugs that have been reported that haven't yet been fixed. Shortlog appended below. Thanks to everyone who helped test things out. --- Gene Cumm

Hi all, I need a hint how to load *nbi images directly with gpxe /pxelinux etc. I have some networkboot images available only as *.nbi, loaded by a startrom.0 with "kernel startrom.0" and then a *.lst for the menue of the nbi images. The *nbi images and the startrom.0 is closed source and I have found no solution to unpack and patch them. I need to boot the images directly without the

it seems versions of pxelinux 4.00 and later hangs qemu (0.12.x, 0.13.x) when network booting using etherboot or gPXE and qemu's kvm support is enabled. pxelinux 3.86 and earlier do not appear to trigger the problem. i also didn't experience the problem with qemu-kvm (formerly known as kvm). qemu without kvm support enabled also seems to work fine. for more details, please see:

On Sat, Sep 26, 2015 at 1:59 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Sep 24, 2015 at 6:59 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >>> Now I have something I can reproduce. Booting my same ipxe.iso to >>> perform an initial TFTP load shows what I