search for: vmhwv10

Patrick, I think I've been able to figure out some missing details about your VMware Workstation tests. For a proxyDHCP, I'm using dnsmasq. Could you try to confirm your test was the same basic setup? On VMware Workstation 10 with a VMHWv10 VM set to EFI firmware for x64, I've been able to get mixed results, depending on if a gateway is provided. With a VMHWv9 VM, I see what appear to be the issues you see. VMHWv10, NAT: Boot Service Discover (a BOOTP style request) sent to the wrong MAC address (MAC address of gateway) VMHWv10...

...te: >>>> > Patrick, I think I've been able to figure out some missing details > about your VMware Workstation tests. For a proxyDHCP, > I'm using dnsmasq. Could you try to confirm your test was the > same basic setup? > > On VMware Workstation 10 with a VMHWv10 VM set to EFI > firmware for x64, I've been able to get mixed results, depending on if agateway is provided. > > With a VMHWv9 VM, I see what appear to be the issues you see. > > VMHWv10, NAT: Boot Service Discover (a BOOTP style request) > sent to the wrong MAC address (MA...

>>> Patrick, I think I've been able to figure out some missing details about your VMware Workstation tests.? For a proxyDHCP, I'm using dnsmasq.? Could you try to confirm your test was the same basic setup? On VMware Workstation 10 with a VMHWv10 VM set to EFI firmware for x64, I've been able to get mixed results, depending on if agateway is provided.? With a VMHWv9 VM, I see what appear to be the issues you see. VMHWv10, NAT: Boot Service Discover (a BOOTP style request) sent to the wrong MAC address (MAC address of gateway)...

...;> Patrick, I think I've been able to figure out some missing details >> about your VMware Workstation tests. For a proxyDHCP, >> I'm using dnsmasq. Could you try to confirm your test was the >> same basic setup? >> >> On VMware Workstation 10 with a VMHWv10 VM set to EFI >> firmware for x64, I've been able to get mixed results, depending on if agateway is provided. >> >> With a VMHWv9 VM, I see what appear to be the issues you see. >> >> VMHWv10, NAT: Boot Service Discover (a BOOTP style request) >> sent to t...

...PXE 6.04-pre1 Copyright (C) 1994-2015 H. Peter Anvin et al". This is on the free ESXi 6.0.0. The license of the host has no relevance in this situation. > I tried different VM hardware versions but this did not produce a different result. Which ones? I typically use VMHWv8 for BIOS and VMHWv10 for EFI. VMHWv8 has the most management compatibility while VMHWv10 resolves a bunch of EFI-specific quirks/bugs. > I haven't tried 4.07 yet, I'll try that. > > Thanks, > Dan Jackson (Lead ITServices Technician). > > -----Original Message----- > From: Syslinux [mailto:...

Just tested with the latest VirtualBox and that works OK, so it's definitely something specific to ESXi 6.0.0 (it worked previously under 5.x ESXi versions). Thanks, Dan Jackson (Lead ITServices Technician). -----Original Message----- From: Syslinux [mailto:syslinux-bounces at zytor.com] On Behalf Of Jackson, Dan via Syslinux Sent: 16 June 2016 09:27 To: 'syslinux at zytor.com'

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

On Mon, Oct 26, 2015 at 9:47 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Oct 26, 2015 at 2:09 PM, Alan Sparks via Syslinux > <syslinux at zytor.com> wrote: >> 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

Gene, All good questions. Thanks for taking time to respond. You've given me great leads to follow up w/ DHCP appliance consultant. >filename being file. I presume it looks like "/path/to/syslinux.efi" >or "/path/to/bootx64.efi" and not a TFTP URL? Correct. >> TFTP Server Name (66) -- a string. I have tried: >> - TFTP Server's IP