[syslinux] pxelinux efi64 boot woes on hyper-v gen 2

[Luke Ledgerd]

Gene,

As it happened I started working on this again just as you mailed me.

It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no joy.

The bootfile size shows up as zero because that relates to "option boot-size" in dhcp and doesn't seem to be the problem

I've already fired up wireshark and had a look, and the tftp was the nas, so I'll move it over to the linux box to get the traffic. The ideas I have now to fix is to try setting up atftp to do multicast tftp.

"option bootfile-name" only freaks out the rom and adds extra characters at the end.

If I have option vendor-class-identifier "PXEClient"; before
Vendor-option-space PXE;
Option PXE.mtftp-ip 0.0.0.0

It freaks out the rom and it says no offer found. It's not just hyper-v I'm testing with a bare-metal system too.
My original configuration file started as the same on from dbrl-clonezilla-server but it's changed a bit now.

Do some PXE roms require MTFTP to boot in EFI mode?

Luke

-----Original Message-----
From: Gene Cumm [mailto:gene.cumm at gmail.com] 
Sent: Thursday, November 27, 2014 8:50 PM
To: Luke Ledgerd
Cc: syslinux at zytor.com
Subject: Re: [syslinux] pxelinux efi64 boot woes on hyper-v gen 2

On Mon, Nov 24, 2014 at 3:24 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote:
> http://www.niallbrady.com/2014/06/11/when-uefi-network-booting-on-a-hy
> perv-gen-2-vm-you-might-get-pxe-e99-unexpected-network-error/
>
> P.S. It's not this and I'm getting a PXE-E99 tftp failure "Unexepected Network Error", so I'll guess I'll need to investigate what kind of TFTP server makes hyper-v happy. Virtualbox, VmWare seem to have the same EFI boot code & output the same error message.
>
> Probably not a problem for the syslinux mailing list.

A packet capture may help figure out why there's a negative tftp/tftpd interaction.

(host 192.0.2.4 and host 192.0.2.5) and udp and (port 69 or (src portrange 1024-65535 and dst portrange 1024-65535))

This should be the easiest filter and can be done on the tftpd system.

> -----Original Message-----
> From: Luke Ledgerd
> Sent: Monday, November 24, 2014 3:06 PM
> To: 'syslinux at zytor.com'
> Subject: pxelinux efi64 boot woes on hyper-v gen 2
>
> I'm trying to boot pxelinux from a hyper-v generation 2 (efi 64), but 
> I keep getting NBP Filename bootx64.efi NBP Filesize 0 bytes and of 
> course it doesn't boot from the startup screen
>
> The thing is the tftpserver works fine with pxelinux.0 and bios mode, and I can use a unix tftp client to download bootx64.efi without any issues.
>
> http://www.syslinux.org/archives/2014-March/021825.html
> I have my DHCP server set up just like steven from CloneZilla.org does.
>
> Any suggestions for this one?
>
> Luke Ledgerd / Internal IT
>
> Add: 156 Xa Dan II, 14th Floor,
>          Dong Da District, Hanoi, Vietnam.
> Mobile Vietnam: +84 (0) 995304270
> Email: luke.ledgerd at niteco.se
> Skype: luke-ledgerd-niteco
> Web: http://niteco.se
>
>
>
>
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux



--
-Gene

A: Because it messes up the order in which people normally read text, especially the archives of mailing lists.
Q: Why is Top-posting such a bad thing?

"No one ever says, 'I can't read that ASCII(plain text) e-mail you sent me.'"