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 > <syslinux at zytor.com> 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. I am using the latest tftp-hpa > > package with the following config: > > > > # /etc/default/tftpd-hpa > > > > TFTP_USERNAME="tftp" > > TFTP_DIRECTORY="/var/lib/tftpboot" > > TFTP_ADDRESS="[::]:69" > > TFTP_OPTIONS="--secure --verbose" > > > > I was using the latest version of syslinux from here: > > https://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-6.03.tar.gz > > I then started testing with this version of syslinux: https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.03/syslinux-6.03-pre6.tar.gz > > 6.03-pre6 is older than 6.03. Numerous UEFI PXE issues should be > addressed in my personal build. > > > I had read in some archives that my issue was resolved for users > > of the 6.03-pre6 version of syslinux but testing with this version > > reveals the same issue for me. > > > > 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. It appears as though the > > file doesn't actually get transferred until a later packet request > > (this time with only one option of blksize included) gets sent > > from my VM client to my tftp server. When it does, I can see an > > acknowledgement from my tftp server (with only the blksize option > > this time) and the file transfer for syslinux.efi begins. I can see > > that my VM client receives the file and is aware of its size. Once > > this file is received, my VM client then requests ldlinux.e64 from > > my tftp server. This request for ldlinux.e64 again has options for > > both tsize and blksize included, and the response packets from the > > tftp server include both options as well. At this stage, unlike wh! > en! > > syslinux.efi was requested, a second request (that includes only > > the blksize option) is never sent and thus ldlinux.e64 is never > > actually transferred. At this point the VM client just sits, > > waiting at the UEFI screen. > > > > I have tried this with both the syslinux-6.03.tar.gz and > > syslinux-6.03-pre6.tar.gz syslinux releases. I have also modified > > my tftp-hpa configuration to refuse tsize, blksize and both options > > together. But I have not had any success in getting UEFI clients > > to boot. > > > > 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?attredirects=0&d=1 > https://sites.google.com/site/genecsyslinux/sl604p0g18-bios.tgz?attredirects=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 Thanks, James
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?attredirects=0&d=1 > > https://sites.google.com/site/genecsyslinux/sl604p0g18-bios.tgz?attredirects=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
> 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/syslinuxHi 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.