[syslinux] PXELINUX 4.10-pre*

[Gene Cumm]

On Wed, May 4, 2011 at 14:20, Eric W. Biederman <ebiederm at xmission.com> wrote:
> Gene Cumm <gene.cumm at gmail.com> writes:
>
>> On Tue, May 3, 2011 at 23:04, H. Peter Anvin <hpa at zytor.com> wrote:
>>> On 05/03/2011 07:07 PM, Gene Cumm wrote:
>>>> So far I tested PXELINUX from 4.10-pre12, 4.10-pre9 and 4.10-pre6.
>>>> The first two take a long time with a TFTP file not found and
>>>> eventually find my file but error out (presumably to kaboom).  The
>>>> last takes a long time, does a lot of retransmitted packets (didn't
>>>> watch the first two), then eventually loads the file but continues
>>>> this behavior for TFTP and HTTP transfers.  This is on VMware Server
>>>> 2.0.2-203138 in Linux using the DHCP server that comes with VMware
>>>> Server, the PXE ROM from VMware Server (info below) and tftpd-hpa 5.0.
>>>>
>>>> HPA, if there's a test you'd like me to try (patch, different -pre,
>>>> etc) let me know.
>>>>
>>>> PXE ROM strings:
>>>>
>>>> Network boot from AMD Am79c970A
>>>> Copyright (C) 2003-2005  VMware, INC.
>>>> Copyright (C) 1997-2000  Intel Corporation
>>>>
>>>>
>>>> UNDI code segment at 9ECC len 0A0D
>>>> UNDI data segment at 9C7F len 24D0
>>>>
>>>
>>> I know the VMware PXE stack is awful beyond belief.  However, could you
>>> get a packet trace (e.g. wireshark) by any chance?
>>
>> Emailed privately.
>
> How does gpxelinux.0 in pxelinux 4.04 fair under vmware?
>
> I am curios to know if the pxelinux on top of gpxe/ipxe on top
> of vmware's pxe rom fairs better.

All three of the above versions are an utter fail in the
aforementioned environment..  They reboot just after printing the UNDI
data segment (nothing else is visible before the reboot).  gpxelinux.0
from Syslinux-4.04 has no issues.

I can try on top of a current ESXi box tomorrow.

-- 
-Gene