search for: vmhw

Issue Statement: PXE booting from BIOS systems works fine on both 6.03 and 6.04-pre1. New clients only support (u)EFI which results in the inability to load remote kernel or initrd. Tested with both Syslinux 6.03 and 6.04-pre1. So far unable to boot any (u)EFI clients unless both initrd and kernel are on PXE server. Using packet captures I see that the URI request for the remote file on the repo

...hey're configured NIC-wise (even just one model for now), since I believe we've seen differing behavior on different models. > So PXE is the last option? Are you manually selecting PXE from this > NIC or is the server automatically selecting this? Using VMware Workstation 10 with a VMHW v10 VM (aka vmx10 though misnomer), RHEL-6 64-bit guest OS hint, (1) e1000 NIC, forcibly changed to UEFI mode. Boot order of floppy, CD, NIC, HDD, 2 manual entries of EFI images on HDD, and the internal shell. Manually selecting NIC, booting sl604p0g18 binaries, config directive as "LOCALBOO...

...issue however we need to try to separate this into either a Syslinux issue or a firmware issue. Did you happen to test HTTP versus TFTP? > System used for initial testing > *ESXi 5.5U3 VM Version 8 (EFI mode) > NIC - vmxnet3 At one point, I remember having a lot of issues with a VMHW v9 VM when I was working on a multi-NIC issue and changed to doing most of testing on VMHW v10 with VMware Workstation 12 or ESXi 6.5 however I still tend to test with VMHW v8 on BIOS. > *Dell R7425 (AMD Epyc based), does not offer a "BIOS" mode > NIC - Broadcom 57412 (10G...

...ernini first noticed this. We both tried using gpxe/gpxelinux.0 from Syslinux-4.04-pre22. ernini used pxechain to a commercial NBP which RETs (the same as PXELINUX) and failed. Both of us had success with core/pxelinux.0 from Syslinux-4.04-pre22. For my test, I have a VM in VMware Server 2.0.2 (VMHW v7). I loaded gpxelinux.0 using the VM's built-in PXE ROM. Then I used pxechain.com to load PXELINUX 4.03 from another directory on the same TFTP server. At this point, I tried LOCALBOOT -1 and 0. -1 (which executes INT 19h) succeeded while 0 failed. Ctrl-Alt-Del does not reboot the machine...

Michael, If you actually get virtualbox PXE booting via UEFI, please let us know how. I spent about two weeks trying to get this to work. This virtualbox PXE booting via UEFI appears so new, it was poorly documented. As of two months ago, when I was doing all this testing. Allegedly, it has experimental support for UEFI PXE boot, if you have Intel NICs. (It uses the UEFI boot code from the

...i >> "EFI BC" -> EFI64\syslinux.efi >> "EFI IA32"-> EFI32\syslinux.efi I only send back 1 filename. >> but it always hangs w/o requesting any other transfer, >> I also tested using VMware 11 same results. My VMs always request files. I created a VMHW v10 VM then added: firmware = "efi" to the VMX and had no issues. Are they actually transferring the syslinux.efi files? What values are present in DHCP options 60 and 93? I've found feeding EFI32 binaries to my VMs results in hangs/failures. >> any idea? 6.03 as in the p...

> I'm testing syslinux PXE EFI boot with VMware workstation 9.04 running > on Windows 8.1 > > VMware correctly performs the DHCP request indicating either > the "EFI IA32" or "EFI BC" architecture and the TFTP server > correctly sends back w/o error the "corresponding" syslinux.efi > "EFI BC" -> EFI64\syslinux.efi >

I'm still trying fruitlessly to get some sort of local disk boot from syslinux EFI to work... using the 6.03 modules. Tried various combinations of configurations on Gene's test binaries. For reference this is on different models of HP Proliant Gen-9 systems with UEFI. Firmware as up to date as it comes. The UEFI boot order has the hard drives and OS ESPs before the PXE interfaces

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

...ponding" syslinux.efi >> "EFI BC" -> EFI64\syslinux.efi >> "EFI IA32"-> EFI32\syslinux.efi >I only send back 1 filename. > Me too, I just send the ""corresponding"" syslinux.efi >My VMs always request files.? I created a VMHW v10 VM >then added: >? firmware = "efi" >to the VMX and had no issues. > Are they actually transferring the syslinux.efi files?? > sure > What values are present in DHCP options 60 and 93?? I've found > feeding EFI32 binaries to my VMs results in hangs/failure...