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; Tue, 21 May 2019 07:54:16 -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 22F98480062 for ; Tue, 21 May 2019 14:54:14 +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; Tue, 21 May 2019 15:54:08 +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; Tue, 21 May 2019 15:54:08 +0100 From: "Tomas Pilar (tpilar)" To: Devel EDK2 Subject: Re: iSCSI and iBFT Thread-Topic: iSCSI and iBFT Thread-Index: AdUPI6dlb8fU6MdhTKeFqUCo+7RKwQAwUYEw Date: Tue, 21 May 2019 14:54:07 +0000 Message-ID: References: <3644c44636fb4fe5b719128ec1443b4c@ukex01.SolarFlarecom.com> In-Reply-To: <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-24628.001 x-tm-as-result: No-20.044700-8.000000-10 x-tmase-matchedrid: oHOSwQSJZWhEXwnTCGfm3f0peXGEEBlvmHAp2UJ8+TxXG3yI9k2vbIfN L7D/HMEOxCW4LIIVzgLZPU+b5RcHaHzrWhwAg+mwydRP56yRRA/QTttTsZbKLwNPGPNKJEnBEYK gogWnjPMkV+WXvBbB8A9sSsR8rFpP+rU9PV9YsWImEURBmKrZlJkShYcLpGH9lnl3JcyTSxKRm9 B2yzQyz3SYMn8Dq9ZfaQCt577mlyQVzjlAzGTQzPviTY7JA6AzzA3oL3ZToRMbomw3ldamxhQy+ Gzi/Qd+QQtdgo5YSWgw8NARYeKsKxc1U+EFS2myR4PPMO+JjQ4KF0jiwuWuOLFbhhcWxNQO2Z5d 2c6tpnYADJaGAMyrsfG6Tbg7r/z5ViFDIhhiYLiCr5xa2StlIbWTdtEh1dU04EVFVDlEYUnCyWd Bi0EpO0gVzEz6oBYpbkLDzoqOPNgd6KvWfwuK0gI6GksNBIxV1ViV5EWK7TubKItl61J/yc8943 oc3p3s32mPO5tnasfxneSaHRJg7/saHqF4wLnIAnyos+evkJBeFhZOhxw74uKTmfqN6r+x x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No x-tmase-result: 10--20.044700-8.000000 x-tmase-version: SMEX-12.5.0.1300-8.5.1010-24628.001 MIME-Version: 1.0 X-MDID: 1558450455-EIeUzqeqzvRj Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_e24276b9cf8f40be93d56211b24ecc73ukex01SolarFlarecomcom_" --_000_e24276b9cf8f40be93d56211b24ecc73ukex01SolarFlarecomcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am going to commit the cardinal sin of online dev support. 'Never mind, found the problem' From: Tomas Pilar Sent: 20 May 2019 16:57 To: 'devel@edk2.groups.io' Subject: iSCSI and iBFT 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 --_000_e24276b9cf8f40be93d56211b24ecc73ukex01SolarFlarecomcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I am going to commit the cardinal sin of online dev = support.

 

‘Never mind, found the problem’

 

From: Tomas Pilar
Sent: 20 May 2019 16:57
To: 'devel@edk2.groups.io' <devel@edk2.groups.io>
Subject: iSCSI and iBFT

 

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

--_000_e24276b9cf8f40be93d56211b24ecc73ukex01SolarFlarecomcom_--