similar to: EFI: ipxe + syslinux = Failed to read blocks: 0xC

>>> Using VMware I built a test setup of a server with dhcp, tftp and a http-server and several pxe-clients with EFI mode turned on. This setup worked, albeit with the exponential-like decay of IO rate I described earlier. The work-around of using HTTP works beautifully though. <<< ""exponential-like decay of IO rate"" could you please post a link on

> Some magic in dhcpd.conf: > > if option architecture-type = 00:09 { > filename "efi64/syslinux-87020-or.efi"; > option pxelinux.pathprefix "http://bla/efi64/"; > } elsif option > architecture-type = 00:07 { > filename "efi64/ipxe-git87981.efi"; > } else { > filename

Hello, I can't help with the problems on real hardware but have come across the qemu problems before and maybe I can give some hints on that. On Fri, 31 Jul 2015, Oscar Roozen via Syslinux wrote: > So it was time for the next step. Migrate this setup to our automated testing > environment that runs under qemu-kvm. For this I had to use OVMF so the nodes > would boot in EFI mode

On 31-07-15 14:25, Patrick Masotta wrote: > ""exponential-like decay of IO rate"" could you please post a link on > your comments on this? Sure, see the thread starting at: http://www.syslinux.org/archives/2015-June/023621.html And Gene's confirmation at: http://www.syslinux.org/archives/2015-June/023629.html > OK I got lost. > are you saying you finally

In another mail I discussed my adventures on netbooting syslinux 6.03 and newer from iPXE, either from an emulated rom on qemu/kvm/ovmf or by chainloading via ipxe.efi onto a real HP Proliant DL360 gen9 piece of iron. You might have asked yourself, why chainload? Why not load it directly? Believe me, i tried. First I had to 'fix' my dhcpd.conf because HP probably read the docs on

> I can't help with the problems on real hardware but have come across the > qemu problems before and maybe I can give some hints on that. Thank you, your help is much appreciated! >> The short story is that I never got further than syslinux proclaiming >> "Failed to read blocks: 0xC" before even getting to the stage where it >> tries to load ldlinux.e64.

Hello. I played with UEFI PXE booting the other day, and as usual, used qemu/kvm virtual machine for initial testing/debugging, because it is way easier and faster for this task than using a real hardware. However, it looks like either qemu or {pxe,sys}linux 6.03 is buggy, -- the two does not play well together. When booting, the system successfully loads syslinux.efi, at least the tftp server

On 31-07-15 18:45, Patrick Masotta wrote: >>>> > Is this possible? Are you saying the FW is stealing the DHCP response > away before iPXE gets it? I haven't thought of this possibility. > > Or am I misunderstanding you? > <<< > > I'm saying that "probably" iPXE is trigerring a new PXE sequence with a different arch but > the one

Hello, I'm trying to find out how to pxe boot with syslinux.efi on QEMU with OVMF. After getting through the initial hurdle caused by the iPXE based option ROM included with QEMU having a problem as described in these threads: http://www.syslinux.org/archives/2014-November/022804.html http://sourceforge.net/p/edk2/mailman/message/33236100/ I'm now getting further to almost being able

On 9/24/2015 4:33 AM, Gene Cumm wrote: > On Wed, Sep 23, 2015 at 5:43 PM, Alan Sparks via Syslinux > <syslinux at zytor.com> wrote: > Although it means another round of testing, you could also consider > lpxelinux.0 which can support HTTP URLs on its own and probably > interacts differently with iPXE. I am curious about a quantifiable > description of "an odd

On Sat, Jun 8, 2013 at 1:17 PM, H. Peter Anvin <hpa at zytor.com> wrote: > I have to say I wonder how much of this is iPXE and much is syslinux... > > Gene Cumm <gene.cumm at gmail.com> wrote: > >>On Thu, Jun 6, 2013 at 5:01 PM, H. Peter Anvin <hpa at zytor.com> wrote: >>> Very odd! >>> >>> This shows a TFTP connection being correctly

>>> > OK I got lost. > are you saying you finally were able to chainload syslinux.efi on the HP?? > by doing what? Some magic in dhcpd.conf: ? ? ???if option architecture-type = 00:09 { ? ? ? ???filename "efi64/syslinux-87020-or.efi"; ? ? ???option pxelinux.pathprefix "http://bla/efi64/"; ? ? ???} elsif option architecture-type = 00:07 { ? ? ?

On 2019-12-13 08:36, Gregory Lee Bartholomew via Syslinux wrote: > On Fri, 2019-12-13 at 08:47 +0100, jps--- via Syslinux wrote: >> Hi, >> >> We are currently testing PXE booting with syslinux.efi in UEFI mode. >> This is working fine. >> However the loading of syslinux.efi and the config files is still using >> TFTP protocol, the rest kernel and initrd is

>>> Is this possible? Are you saying the FW is stealing the DHCP response away before iPXE gets it?? I haven't thought of this possibility. Or am I misunderstanding you? <<< I'm saying that "probably" iPXE is trigerring a new PXE sequence with a different arch but the one that finally loads the new NBP is really the FW. >>> Since I'm

On Thu, Jun 6, 2013 at 5:01 PM, H. Peter Anvin <hpa at zytor.com> wrote: > Very odd! > > This shows a TFTP connection being correctly established and then > disconnected, with all the negotiation involved. I'm wondering if it is > iPXE that is playing games with us here... Packets 301-306, 309-312 show two successful attempts to read linux-install/pxelinux.cfg/C0A80058

Am 06.06.2013 07:00, schrieb Gene Cumm: > iPXE details. My testing was with an Intel PXE OROM in a VMware > hosted platform with 0 issues. > >> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" 200 26813 >> "" "iPXE/1.0.0+ (09c5)" This is the iPXE version that comes bundled with qemu as the default qemu boot rom. -------------- next

Stefan Hajnoczi <stefanha at gmail.com> writes: > On Sat, Jun 8, 2013 at 7:39 PM, Laszlo Ersek <lersek at redhat.com> wrote: >> Patches before the last are small cleanups. >> >> In the last patch I'm trying to extract / generalize an idea from Stefan >> Hajnoczi's review of my virtio-net driver for OVMF. How about a single patch which just replaces

Stefan Hajnoczi <stefanha at gmail.com> writes: > On Sat, Jun 8, 2013 at 7:39 PM, Laszlo Ersek <lersek at redhat.com> wrote: >> Patches before the last are small cleanups. >> >> In the last patch I'm trying to extract / generalize an idea from Stefan >> Hajnoczi's review of my virtio-net driver for OVMF. How about a single patch which just replaces

Hello, First, this setup works fine without any error in syslinux 4.06 as show below. For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] directories (~2MB each) are uploaded ready for test. As said before, this is tested on qemu-1.5.0 + dnsmasq 2.66 in Arch Linux @ 64-bit. If more info is needed, please let me know. Good luck! Relevant directory structure is at

Hello SYSLINUX folks, thanks for all your hard work over the years! I'm working on a fairly complex deployment services project, and one of the aspects of it is to make it possible to federate deployment services across our university. Supporting existing deployment services is a priority, so I am presently trying to integrate an existing PXELINUX install, part of a FOG windows imaging