thr3ads.net - Syslinux - [syslinux] Hyper-V Gen 2 waiting for ldlinux.e64 [Oct 2015]

If this information is useful, please help other people find it:
Share via:

Clements, James

2015-Oct-07 13:55 UTC

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

> On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux
> wrote:
> > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux
wrote:
> > > On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux
wrote:
> > > > Hi,
> > > >
> > > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM
as a
> > > > PXE client (no physical machines available). This is a UEFI
VM,
> > > > and as per instructions I've read I have disabled secure
boot on
> > > > this VM for the installation of Linux.
> > > >
> > > >
> > > > The problem I am experiencing is that when I attempt to PXE
boot
> > > > my Hyper-V VM client, I can see it requesting the
syslinux.efi
> > > > file from the tftp server. The initial request has options
for
> > > > both tsize and blksize included, and the response packets
from the
> > > > tftp server include both options as well.
> > > >
> > > > I have a packet capture here (please excuse the
'noise') which
> > > > demonstrates the problem I am seeing here:
> > > >
> > > > https://dl.dropboxusercontent.com/u/102712992/capture.pcap
> > >
> > > http://www.syslinux.org/archives/2015-October/024375.html
> > >
> > > git://github.com/geneC/syslinux.git
> > > https://github.com/geneC/syslinux.git
> > >
> > > Branch 1efipxe
> > >
> > >
> > >
https://sites.google.com/site/genecsyslinux/sl604p0g18-x64.tgz?attre
> > > directs=0&d=1
> > >
https://sites.google.com/site/genecsyslinux/sl604p0g18-bios.tgz?attr
> > > edirects=0&d=1
> > >
> > > Please try these binaries.  Thanks in advance.
> > >
> >
> >
> > Hi Gene,
> >
> > 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, found this
>
> 13:36:47.954215 IP 192.168.205.50.1938 > 192.168.205.1.tftp:  40 RRQ
> "efi64/syslinux.efi" octet blksize 1482
> 13:36:47.954774 IP 192.168.205.1.47973 > 192.168.205.50.1938: UDP,
length 15
> 13:36:47.955380 IP 192.168.205.50.1938 > 192.168.205.1.47973: UDP,
length 4
> 13:36:47.955417 IP 192.168.205.1.47973 > 192.168.205.50.1938: UDP,
length
> 1486
> 13:36:47.955421 IP 192.168.205.1 > 192.168.205.50: udp
> 13:36:47.955482 IP 192.168.205.50.1938 > 192.168.205.1.47973: UDP,
length 4
> 13:36:47.955499 IP 192.168.205.1.47973 > 192.168.205.50.1938: UDP,
length
> 1486
> 13:36:47.955502 IP 192.168.205.1 > 192.168.205.50: udp
> 13:36:47.955553 IP 192.168.205.50.1938 > 192.168.205.1.47973: UDP,
length 4
> 13:36:47.955568 IP 192.168.205.1.47973 > 192.168.205.50.1938: UDP,
length
> 1486
> 13:36:47.955571 IP 192.168.205.1 > 192.168.205.50: udp which is the
start of
> the TFTP transfer of efi64/syslinux.efi
>
> Then at the end
>
> $ /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.
>
>
>
> Groeten
> Geert Stappers
> --
> Leven en laten leven
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
Hi Geert,

Do you have any suggestions on how I could resolve this issue then?

Thanks,

James

This e-mail and any attachments may be confidential or legally privileged. If
you received this message in error or are not the intended recipient, you should
destroy the e-mail message and any attachments or copies, and you are prohibited
from retaining, distributing, disclosing or using any information contained
herein.  Please inform us of the erroneous delivery by return e-mail. Thank you
for your cooperation.

Geert Stappers

2015-Oct-07 15:35 UTC

head link

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

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

Geert Stappers

2015-Oct-07 16:01 UTC

head link

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

On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux
wrote:> On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote:
> > On Wed, Oct 07, 2015 Geert Stappers wrote
> > > 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
> 
And now a better suggestion

--- a/core/fs/pxe/isr.c
+++ b/core/fs/pxe/isr.c
@@ -267,6 +267,7 @@ void pxe_start_isr(void)
        int hwad = ((int)MAC[0] << 16) + ((int)MAC[1] << 8) +
MAC[2];
        dprintf("pxe_start_isr: got %06x %04x\n", hwad,
pxe_undi_iface.ServiceFlags);
        if ((hwad == 0x000023ae) && (pxe_undi_iface.ServiceFlags ==
0xdc1b) ||
+           (hwad == 0x0000155d) && (pxe_undi_iface.ServiceFlags ==
0xdc1b) ||
            (hwad == 0x005c260a) && (pxe_undi_iface.ServiceFlags ==
0xdc1b) ||
            (hwad == 0x00180373) && (pxe_undi_iface.ServiceFlags ==
0xdc1b)) {
                asm volatile("orb $1,%0" : "+m"
(pxe_need_poll));


See commit 1ada8a37ae30c2e4283c3e65444ccd72cf8a2e85 for where I see simularity.


Groeten
Geert Stappers
-- 
Leven en laten leven

Reasonably Related Threads

Search for more possibly parallel threads

Syslinux - Oct 2015 - Hyper-V Gen 2 waiting for ldlinux.e64

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

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

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

Reasonably Related Threads