UEFI boot and sanhook

[NiKiZe]

(2018-09-20 09:24)parthy Wrote:  I think I've tracked the issue down to the call chain shutdown_boot() -> efi_remove() -> efi_driver_disconnect_all(). The entire subsystem is removed, even though the boot services are still active. Hence, the network connection is gone and the iSCSI disk is no longer available. So the remaining question is if this is intentional or not, i.e., if an iSCSI hook should remain functional after a kernel is loaded (I see the shutdown call in ELF, Multiboot, and Linux loading).

I've tested the shell example on qemu (with drivers e1000 and rtl8139) and on an Intel NUC7 with I219-LM (8086:156f). It seems the problem is not a specific driver, but the fact that a driver is used instead of the UEFI network services.

iPXE provides a full stack that can be shutdown, some Firmware might not.
If something shuts down the nic it is expected that it also brings it up.
For example Linux would start the nic, see iBFT (tools in the initramfs) and then configure the nic correctly and connect to the iSCSI device.
The nic is _always_ shutdown when a real OS kernel takes over which then re-initializes the nic.