[syslinux] Hyper-V Gen 2 waiting for ldlinux.e64

[Geert Stappers]

On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote:
> On Wed, Oct 07, 2015 Geert Stappers wrote
> > On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux
> > > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote:
> > > >
> > > > http://www.syslinux.org/archives/2015-October/024375.html

 "UseDefaultAddress" and "server in DHCP"


> > > > https://sites.google.com/site/genecsyslinux/sl604p0g18-x64.tgz?attredirects=0&d=1
> > > > https://sites.google.com/site/genecsyslinux/sl604p0g18-bios.tgz?attredirects=0&d=1
> > > >
> > > > Please try these binaries.  Thanks in advance.
> > > >
> > >
> > > Thanks for the quick reply. I have just tested the binaries from
> > > sl604p0g18-x64.tgz and still have the same   issue. Here is another
> > > capture using the new binaries, although to be honest the ldlinux.e64
> > > behaviour looks much like the first:
> > >
> > > https://dl.dropboxusercontent.com/u/102712992/capture2.pcap
> > >
> >
> > Did wget that PCAP-file
> >
> > $ /usr/sbin/tcpdump -r capture2.pcap ether host 00:15:5d:7c:99:03 | tail
> > reading from file capture2.pcap, link-type EN10MB (Ethernet)
> > 13:36:47.964568 IP 192.168.205.1.47973 > 192.168.205.50.1938: UDP, length 1486
> > 13:36:47.964571 IP 192.168.205.1 > 192.168.205.50: udp
> > 13:36:47.964623 IP 192.168.205.50.1938 > 192.168.205.1.47973: UDP, length 4
> > 13:36:47.964636 IP 192.168.205.1.47973 > 192.168.205.50.1938: UDP, length 30
> > 13:36:47.964685 IP 192.168.205.50.1938 > 192.168.205.1.47973: UDP, length 4
> > 13:36:47.974245 IP 192.168.205.50.1939 > 192.168.205.1.tftp:  47 RRQ "efi64/ldlinux.e64" octet tsize 0 blksize 1408
> > 13:36:47.974552 IP 192.168.205.1.56054 > 192.168.205.50.1939: UDP, length 28
> > 13:36:48.975612 IP 192.168.205.1.56054 > 192.168.205.50.1939: UDP, length 28
> > 13:36:50.971212 IP 192.168.205.1.57375 > 192.168.205.50.1937: UDP, length 28
> > 13:36:50.977653 IP 192.168.205.1.56054 > 192.168.205.50.1939: UDP, length 28
> >
> > I do read in that 192.168.205.50 going deaf.
> >
> 
> Do you have any suggestions on how I could resolve this issue then?
> 

Start with sharing more information. Information that I miss.

 * text which is on the screen of the netbooting (virtual) machine
 * when/why was the network capture stopped


Groeten
Geert Stappers
-- 
Leven en laten leven