iPXE with Omni-Path

[awray]

Does iPXE support Omni-Path (for UEFI chain-loading would be sufficient for what I was trying to get to work)? If not, are there any plans to add support for Omni-Path?

[NiKiZe]

For now EFI iPXE does not have any san booting support/interface so even if the Omni-Path hardware where supported for communication boot of some kind of iSCSI-alike device would not be possible in EFI mode yet.

But Omni-Path is new to me, found this where as i understand it you just need hardware support. but since pxelinux is mentioned, I guess ipxe undionly.pxe would work just as well in legacy mode, for efi you could try snpoinly.efi which should hopefully just work.

Can you shed any more light on which NIC you are intending to use?

[awray]

(2016-10-04 18:58)NiKiZe Wrote:  For now EFI iPXE does not have any san booting support/interface so even if the Omni-Path hardware where supported for communication boot of some kind of iSCSI-alike device would not be possible in EFI mode yet.

But Omni-Path is new to me, found this where as i understand it you just need hardware support. but since pxelinux is mentioned, I guess ipxe undionly.pxe would work just as well in legacy mode, for efi you could try snpoinly.efi which should hopefully just work.

Can you shed any more light on which NIC you are intending to use?

I was mainly interested in PXE boot--not iSCSI/SAN type boot with Omni-Path. The specific NICs I was trying to use was the single-port OPA x8 and x16 (100 series) adapters.

---

(2016-12-01 17:12)awray Wrote:  

(2016-10-04 18:58)NiKiZe Wrote:  For now EFI iPXE does not have any san booting support/interface so even if the Omni-Path hardware where supported for communication boot of some kind of iSCSI-alike device would not be possible in EFI mode yet.

But Omni-Path is new to me, found this where as i understand it you just need hardware support. but since pxelinux is mentioned, I guess ipxe undionly.pxe would work just as well in legacy mode, for efi you could try snpoinly.efi which should hopefully just work.

Can you shed any more light on which NIC you are intending to use?

I was mainly interested in PXE boot--not iSCSI/SAN type boot with Omni-Path. The specific NICs I was trying to use was the single-port OPA x8 and x16 (100 series) adapters.

I tried snponly.efi (this was built from source on 6/4/16, so its probably old though) and got this output:

>>Start PXE over IPv4.
Station IP address is 10.22.66.207

Server IP address is 10.22.66.95
NBP filename is xcat/snponly.efi
NBP filesize is 133376 Bytes
Downloading NBP file...

Succeed to download NBP file.

Downloading NBP file...

Succeed to download NBP file.
iPXE initialising devices...ok



iPXE 1.0.0+ (f6e8) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP TFTP EFI Menu

net0: 00:01:00:00:fe:80 using NII on NII-PCI06:00.0 (open)
[Link:down, TX:0 TXE:0 RX:0 RXE:0]
[Link status: Unknown (http://ipxe.org/1a086194)]
Configuring (net0 00:01:00:00:fe:80).................. No configuration methods succeeded (http://ipxe.org/040ee186)
No more network devices

The 00:01:00:00:fe:80 isn't really the whole identifier for the adapter--that was (from the DHCP discover during PXE--option 61):

3d 13 ff 00 00 00 00 00 02 00 00 01 57 00 11 75 01 01 67 11 ad

however the hardware address of the OPA adapter shown by ip addr in Linux is:

80:00:00:02:fe:80:00:00:00:00:00:00:00:11:75:01:01:67:11:ad brd 00:ff:ff:ff:ff:12:40:1b:80:01:00:00:00:00:00:00:ff:ff:ff:ff

[NiKiZe]

Ok so extension of mac address, arp and other L2 features is needed to have it working.
You might want to contact Michel directly to see what kind of support is possible, he seems to be quite busy right now tho.

(oh, not that it matters in your case then, but SAN booting in EFI has arrived )