Search
Member List
Calendar
Help
|
UEFI boot and sanhook
|
|
2018-09-18, 15:27
Post: #1
|
|||
|
|||
|
UEFI boot and sanhook
Hi,
I have a question about the hooking of iSCSI drives in iPXE when booting on UEFI machines. On legacy systems, it was possible to transparently access the hooked drive using int13h. iPXE would catch those calls and translate them to iSCSI requests. Is there an equivalent method for UEFI systems? I got as far as hooking the drive and starting an EFI application (either via Multiboot2 using an experimental branch, or just chain shellx64.efi), but I couldn't find a way to actually access the drive from within that application. Directly booting via sanboot seems to work fine. Using DEBUG=efi_block:3 I see that iPXE installed the drive in the iBFT, and also registered some protocol with UEFI. But trying to do anything on that protocol just hangs, and I see one line of debug output like this one: Code: EFIBLK 0x80 read LBA 0x... to ...Has anyone tried this before? Or is it just not designed for this and only iPXE itself can access the hooked device? |
|||
|
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
UEFI boot and sanhook - parthy - 2018-09-18 15:27
RE: UEFI boot and sanhook - NiKiZe - 2018-09-18, 18:24
RE: UEFI boot and sanhook - NiKiZe - 2018-09-19, 12:40
RE: UEFI boot and sanhook - parthy - 2018-09-19, 13:06
RE: UEFI boot and sanhook - NiKiZe - 2018-09-19, 13:16
RE: UEFI boot and sanhook - parthy - 2018-09-20, 09:24
RE: UEFI boot and sanhook - NiKiZe - 2018-09-20, 20:32
|
User(s) browsing this thread: 1 Guest(s)