From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: solarflare.com, ip: 148.163.129.52, mailfrom: tpilar@solarflare.com) Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [148.163.129.52]) by groups.io with SMTP; Mon, 20 May 2019 08:56:58 -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 22281480094 for ; Mon, 20 May 2019 15:56:56 +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; Mon, 20 May 2019 16:56:52 +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; Mon, 20 May 2019 16:56:52 +0100 From: "Tomas Pilar (tpilar)" To: "devel@edk2.groups.io" Subject: iSCSI and iBFT Thread-Topic: iSCSI and iBFT Thread-Index: AdUPI6dlb8fU6MdhTKeFqUCo+7RKwQ== Date: Mon, 20 May 2019 15:56:52 +0000 Message-ID: <3644c44636fb4fe5b719128ec1443b4c@ukex01.SolarFlarecom.com> 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-24624.003 x-tm-as-result: No-17.658300-8.000000-10 x-tmase-matchedrid: liXG6TWiBABHW+94FA8JF8K1Ib9JAALxrogFtKd/P7cLBZEuqIL9SpO9 mQGx4jC3Sa7i4WMGYwF/2SsgU8jyNW7vEKjEI8LygNylVbI/EAyoCf7IdvPAJzrW2rRfTfGrevR Ae5P8R96552PelBLuJnsRbtp3bY8XDEVT5M0HH4UiPTMUjkOgksC2kM0wuzzWmCNknSXswf//dF 8v22ms8eisj1kjegzMMPDQEWHirCsXNVPhBUtpskeDzzDviY0OChdI4sLlrjixW4YXFsTUDtmeX dnOraZ2AAyWhgDMq7Hxuk24O6/8+VYhQyIYYmC4gq+cWtkrZSG1k3bRIdXVNOBFRVQ5RGFJwsln QYtBKTtIFcxM+qAWKW5Cw86KjjzYHeir1n8LitICOhpLDQSMVdVYleRFiu07myiLZetSf8nPPeN 6HN6d7N9pjzubZ2rHsMYZc49s8JtEvoi86Jn9eZXNkroDWfGij2LsEu/21n9cyX7glGYx0UsMHB ii02BH x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No x-tmase-result: 10--17.658300-8.000000 x-tmase-version: SMEX-12.5.0.1300-8.5.1010-24624.003 MIME-Version: 1.0 X-MDID: 1558367818-Gdq8JY_S4LlO Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3644c44636fb4fe5b719128ec1443b4cukex01SolarFlarecomcom_" --_000_3644c44636fb4fe5b719128ec1443b4cukex01SolarFlarecomcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I have a bit of an esoteric problem. When I configure the software iscsi in= tiator that is part of EDK2 platform network stack, the platform network st= ack with install iBFT table into the ACPI tables so that the configuration = can be picked up by further boot loaders and the OS. So far so good. Problem: When I PXE boot into iPXE using my adapter, exit back into boot ma= nager, the iBFT has disappeared. Alternatively, if I use iPXE to then boot = WDS, the software initiator in WinPE won't find the iBFT table and therefor= e won't hook the network drive. Observations: * When I boot into UEFI shell on disk and exit back into boot manager, the = iBFT is preserved. * When I PXE boot into UEFI shell and exit, the iBFT is preserved. * When I boot into iPXE on disk and exit, the iBFT is preserved. * When I use a different adapter (Intel) to pxe boot into iBFT and exit bac= k to boot manager, the iBFT has moved from the penultimate position to the = last position in the ACPI tables. Almost as if something uninstalled the iB= FT and reinstalled it. Any ideas? Cheers Tom The information contained in this message is confidential and is intended f= or the addressee(s) only. If you have received this message in error, pleas= e notify the sender immediately and delete the message. Unless you are an a= ddressee (or authorized to receive for an addressee), you may not use, copy= or disclose to anyone this message or any information contained in this me= ssage. The unauthorized use, disclosure, copying or alteration of this mess= age is strictly prohibited. --_000_3644c44636fb4fe5b719128ec1443b4cukex01SolarFlarecomcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

I have a bit of an esoteric problem. When I configur= e 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 configuration can be picked up by further boot loaders and the OS. So far so good.

 

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 boot WDS, the software initiator in WinPE won’t fin= d the iBFT table and therefore won’t hook the network drive.

 

Observations:

* When I boot into UEFI shell on disk and exit back = into boot manager, the iBFT is preserved.

 

* When I PXE boot into UEFI shell and exit, the iBFT= is preserved.

 

* When I boot into iPXE on disk and exit, the iBFT i= s preserved.

 

* When I use a different adapter (Intel) to pxe boot= into iBFT and exit back to boot manager, the iBFT has moved from the penul= timate position to the last position in the ACPI tables. Almost as if somet= hing uninstalled the iBFT and reinstalled it.

 

Any ideas?

 

Cheers

Tom

The information contained in this message is confidential and is intended f= or the addressee(s) only. If you have received this message in error, pleas= e notify the sender immediately and delete the message. Unless you are an a= ddressee (or authorized to receive for an addressee), you may not use, copy or disclose to anyone this messag= e or any information contained in this message. The unauthorized use, discl= osure, copying or alteration of this message is strictly prohibited. --_000_3644c44636fb4fe5b719128ec1443b4cukex01SolarFlarecomcom_--