From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: solarflare.com, ip: 67.231.154.164, mailfrom: tpilar@solarflare.com) Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) by groups.io with SMTP; Wed, 22 May 2019 02:55:45 -0700 X-Virus-Scanned: Proofpoint Essentials engine Received: from webmail.solarflare.com (uk.solarflare.com [193.34.186.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1-us3.ppe-hosted.com (PPE Hosted ESMTP Server) with ESMTPS id 016FEB8005A; Wed, 22 May 2019 09:55:43 +0000 (UTC) Received: from ukex01.SolarFlarecom.com (10.17.10.4) by ukex01.SolarFlarecom.com (10.17.10.4) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 22 May 2019 10:55:39 +0100 Received: from ukex01.SolarFlarecom.com ([fe80::3c10:6f38:9305:ac6d]) by ukex01.SolarFlarecom.com ([fe80::3c10:6f38:9305:ac6d%14]) with mapi id 15.00.1395.000; Wed, 22 May 2019 10:55:39 +0100 From: "Tomas Pilar (tpilar)" To: Devel EDK2 , "lersek@redhat.com" Subject: Re: [edk2-devel] iSCSI and iBFT Thread-Topic: [edk2-devel] iSCSI and iBFT Thread-Index: AdUPI6dlb8fU6MdhTKeFqUCo+7RKwQAwUYEwAAguGQAAH4XaoA== Date: Wed, 22 May 2019 09:55:38 +0000 Message-ID: <1c6545291d0f460fac20abf2187a551c@ukex01.SolarFlarecom.com> References: <3644c44636fb4fe5b719128ec1443b4c@ukex01.SolarFlarecom.com> In-Reply-To: Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.17.25.143] x-tm-as-product-ver: SMEX-12.5.0.1300-8.5.1010-24630.003 x-tm-as-result: No-16.053700-8.000000-10 x-tmase-matchedrid: u6ojmU07PKzuo96mfIBuopzEHTUOuMX33dCmvEa6IiGoLZarzrrPmfrF pSTwk+pCB9BKdYQu5uVi1z02mY0EEWdUTmnrNz1OqJSK+HSPY+9JaD67iKvY02AMM0WKD4ascVo lGMdkWBvoHgrZ+UltMUGq4Vc2O5SVQlyD2wqbJRC1u/qNjkzEXJUqYZRn9aeRKgGZaOQty4vDi1 qA9dFHHFFDWBoOM+0ifzKpHT1GR5WYXuSElV1g6hmlzjMYni4oGbJMFqqIm9zk1kyQDpEj8Of1F RvbDqwVzpPzIE7ocQGBrrKlfaYs/jwe897U/PjCbRZGrsoeW/hAmMl/so7kGhtVRURjpT+v6DQP GnwL9La6ihXkOgGrrDAED5vkHquavTl5/j7foof1WO1NzV/CYAZyESFXAljf8axg/T4HQTVg21A HDDlGdP+mDtMQ4jTKtQw5ef8H/due7Ex/4fMHcceuFL5UpINxAQ+35UHH2f2RiV0eo0RbuJhRBY xZ+VWnaVfzQVR3Kx+0l2XPsIg6YmREc2tmV2Niy7GglnbkiH9xZkR+u3smBVnFZNfj6Xm2/fZeS /lDEATPi27s6VEdRunb9ZCRNMIy0Dg2p0ztpjRNq5/Y+tFvW6kHfh7O2L+7+nDqnR0MvOFrYHJB lx9pJ0s68SHVdwUKlxnSJwunsOq/WXZS/HqJ2sC4UUZr4lSF+gD2vYtOFhgqtq5d3cxkNQwWxr7 XDKH84GapJ/l1MqOX2347xebsaar2SPx7JOF6+ib2USp140wFgi/2Gbcz+A== x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No x-tmase-result: 10--16.053700-8.000000 x-tmase-version: SMEX-12.5.0.1300-8.5.1010-24630.003 MIME-Version: 1.0 X-MDID: 1558518944-7y_oWe7-ZQYd Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable iPXE identifies the device it was pxe booted from by searching parents of t= he LoadedImage which support SNP and NII and uses the address of the instal= led NII and SNP as a discriminant to see if a device is in fact the one it = was pxe booted from. This convoluted process is done to shoehorn chainload = drivers into the ipxe driver api. Then it will chainload NII or SNP drivers on all devices if they pass the = above check. My driver used a global static NII struct and installed that a= s NII on all ports so ipxe then tried to bind its NIIONLY driver on all por= ts on the adapter, not just the one it was pxebooted with. Thus it kicked o= ff the network stack including the iSCSI connection on the second port even= though it was pxe booted into using the first port. Ugh. -----Original Message----- From: devel@edk2.groups.io On Behalf Of Laszlo Erse= k Sent: 21 May 2019 20:48 To: Devel EDK2 ; Tomas Pilar Subject: Re: [edk2-devel] iSCSI and iBFT On 05/21/19 16:54, Tomas Pilar (tpilar) wrote: > I am going to commit the cardinal sin of online dev support. heh :) > 'Never mind, found the problem' What was it? I didn't ignore your original email -- I looked at iPXE briefly, but could= n't blame anything at once, and then I quickly ran out of steam. There wasn't anything I could have added to the thread. Thanks, Laszlo > From: Tomas Pilar > Sent: 20 May 2019 16:57 > To: 'devel@edk2.groups.io' > Subject: iSCSI and iBFT >=20 > Hi, >=20 > I have a bit of an esoteric problem. When I configure the software iscsi= intiator that is part of EDK2 platform network stack, the platform network= stack with install iBFT table into the ACPI tables so that the configurati= on can be picked up by further boot loaders and the OS. So far so good. >=20 > Problem: When I PXE boot into iPXE using my adapter, exit back into boot= manager, the iBFT has disappeared. Alternatively, if I use iPXE to then bo= ot WDS, the software initiator in WinPE won't find the iBFT table and there= fore won't hook the network drive. >=20 > Observations: > * When I boot into UEFI shell on disk and exit back into boot manager, t= he iBFT is preserved. >=20 > * When I PXE boot into UEFI shell and exit, the iBFT is preserved. >=20 > * When I boot into iPXE on disk and exit, the iBFT is preserved. >=20 > * When I use a different adapter (Intel) to pxe boot into iBFT and exit = back to boot manager, the iBFT has moved from the penultimate position to t= he last position in the ACPI tables. Almost as if something uninstalled the= iBFT and reinstalled it. >=20 > Any ideas? >=20 > Cheers > Tom >=20 >=20 >=20 >=20