Re: [ipxe-devel] Script embedding in EFI environment

2016-12-02 Thread Martin Habets
Maybe you could use DHCP option 209? https://tools.ietf.org/html/rfc5071#section-4 Martin On 01/12/16 15:49, Lukas Zapletal wrote: > Hello, > > our project (www.theforeman.org ) provides > functionality to generate bootdisk for individual hosts. These are either >

Re: [ipxe-devel] Script embedding in EFI environment

2016-12-02 Thread Lukas Zapletal
Thanks, I haven't noticed it's moderated. Had to miss the message there. 2016-12-01 23:40 GMT+01:00 Christian Nilsson : > The forum is moderated for new users, approved one of your posts and > responded to it here: > http://forum.ipxe.org/showthread.php?tid=8244 > > On Thu, Dec

Re: [ipxe-devel] Script embedding in EFI environment

2016-12-02 Thread Hummel Frank
I do that via DHCP server configuration. Legacy (Syslinux) and IPXE clients use different user-classes. Legacy and UEFI use different architectures. As IPXE initiates a new DHCP request you have to break the boot-loop by detecting the iPXE user-class Shortened code snippet from my dhcpd.conf:

[ipxe-devel] [PATCH 1/1] [intelxvf] Reset all vf settings before config

2016-12-02 Thread Vishvananda Ishaya Abrams
From: Vishvananda Ishaya Some vf data is not cleared with reset, so make sure to return all the settings to default before configuring the vf. This fixes an issue where network packets would fail to be received if the vf was previously used by the linux ixgbevf driver.

[ipxe-devel] [PATCH 0/1] [intelxvf] Reset all vf settings before config

2016-12-02 Thread Vishvananda Ishaya Abrams
Iscsi booting off a virtual function using ixgbevf works correctly during the first boot, but after booting into a guest os running linux and hard rebooting, the guest will no longer iscsi boot. I tracked the issue down to an issue with the reset of the virtual function. Reset does not actually

[ipxe-devel] [PATCH 0/1,WIP] [efi] allow setting of uefi filename

2016-12-02 Thread Vishvananda Ishaya Abrams
The uefi iscsi boot will only boot the default iscsi filename on the san drive (\EFI\BOOT\BOOTX64.EFI). Unfortunately, most os installers do not put the default efi file in place. Generally, they will install an efi file in a vendor directory and set up an efivar to tell the firmware where to find

[ipxe-devel] [PATCH 1/1,WIP] [efi] allow setting of uefi filename

2016-12-02 Thread Vishvananda Ishaya Abrams
From: Vishvananda Ishaya This patch adds a new setting to allow a uefi filename to be specified. The parameter is uefi-filename and can be set in a script like so: set uefi-filename \EFI\vendor\file.efi If specified, this filename will be used during the sanboot