From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from IMSVA.IN.MEGATRENDS.COM (Webmail.amiindia.co.in [203.199.198.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 9638321967BC4 for ; Fri, 9 Jun 2017 10:47:26 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3E0F682059 for ; Fri, 9 Jun 2017 23:20:38 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 31F0482058 for ; Fri, 9 Jun 2017 23:20:37 +0530 (IST) Received: from webmail.amiindia.co.in (venus1.in.megatrends.com [10.0.0.5]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS for ; Fri, 9 Jun 2017 23:20:37 +0530 (IST) Received: from VENUS2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b]) by VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5%14]) with mapi id 14.01.0438.000; Fri, 9 Jun 2017 23:18:32 +0530 From: Santhapur Naveen To: Karunakar P , "edk2-devel@lists.01.org" Thread-Topic: HTTP Boot failed to download NBP file if it is .iso type Thread-Index: AdLhJADZenTRkzHLTdKp4dJtuK+91AAI2B4w Date: Fri, 9 Jun 2017 17:48:31 +0000 Message-ID: <625A2455CC232F40B0F38F05ACED6D97C8690EA8@Venus2.in.megatrends.com> References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.77] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-23122.001 X-TM-AS-Result: No--14.564-5.0-31-10 X-imss-scan-details: No--14.564-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23122.001 X-TMASE-Result: 10--14.563700-10.000000 X-TMASE-MatchedRID: WMT2WRIkHPPM/ECkaAy/4hhTGJQ1M8K9guwtqyXlE6Gyt+Bw0APWhqe7 nmhJA6kzox3eLPiNwxUJw69YfzT4YHHMXURFxRSfTd1FGyH+HrKnp0KWJWIxTDmpks4scE+jmKb hu5KaCkd7YoZrn6YJZH9y1Y/OQ9g6R0cAoC1UfG0D2WXLXdz+AcmWIruGUPzpPZer8OZsBgt6hG 9KQqk/+FA2BpUGyQ2W5JEhOHr9HLlYWbZEA8puehWCVBr+Ay98lS1vY7b3fBn7efdnqtsaE996V 2NgrEHiNlpmSQMjZB9A7GGikEUkNZbpMO7SraapT7jCYv2QJPGO74ZfTyAQsN1vuXkVV7ZbEWXA mFVxJU7weU23Zzx/pWi/5BPaxauJ717yJ8IcCtsc8J6ZrWP/q8hpcNaVl4hs+Cckfm+bb6BaeSL r129mSy11o3cgSMCfbYsPQfc3D1tccQ8eam5Eff7E6GNqs6ce3QfwsVk0Ubs3Afsjx8AVGkjNTK kDX2ppvQszSXardM7mTaja3B9Yq2uI0sRUg5sLiz7uFHhV/yM= X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-0 Subject: Re: HTTP Boot failed to download NBP file if it is .iso type X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jun 2017 17:47:27 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Even if we are able to download an ISO file successfully, how will EFI_RAM_= DISK_PROTOCOL comes to know what is the efi that needs to be used? -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Karu= nakar P Sent: Friday, June 09, 2017 9:04 PM To: edk2-devel@lists.01.org Subject: [edk2] HTTP Boot failed to download NBP file if it is .iso type Hi All, We have facing an issue with HTTP boot. [Issue] HTTP Boot failed to download NBP file if it is an .iso type [Reproduction Steps] 1. Configure HTTP Server in Ubuntu environment. 2. Place any iso image as NBP file. 3. Perform UEFI HTTPv4 boot. [Result] DHCP process was success, But Failed to download NBP file. [Observations] 1. As per UEFI spec "23.7.1 Boot from URL" (UEFI 2.6, page 1222). Here is what the section says about binary image returned by HTTP server: "...the binary image [..] is a UEFI-formatted executable[...], or it could = be mounted as a RAM disk which contains a UEFI-compliant file system (see S= ection 12.3)." We're interested in exploring second scenario, when downloaded image is a U= EFI-compliant file system. Section "23.7.3.1 Device Path" on page 1226 provides examples of image URL:= http://192.168.1.100/boot.iso The specification also says that "the HTTP Boot driver will register RAM di= sk with the downloaded NBP, by appending a RamDisk device node to the devic= e path above, like...". HttpBootDxe is doing this.But NBP file itself failing to download in the ca= se of iso image. 2. HTTP boot fails in the following function HttpBootGetBootFile() -> EFI_STATUS HttpBootGetBootFile ( IN HTTP_BOOT_PRIVATE_DATA *Private, IN BOOLEAN HeaderOnly, IN OUT UINTN *BufferSize, OUT UINT8 *Buffer, OUT HTTP_BOOT_IMAGE_TYPE *ImageType ) { . . . Status =3D HttpIoRecvResponse ( &Private->HttpIo, TRUE, ResponseData ); // Here the Status value is Success and ResponseData->Status =3D 00000023 if (EFI_ERROR (Status) || EFI_ERROR (ResponseData->Status)) { if (EFI_ERROR (ResponseData->Status)) { StatusCode =3D HttpIo->RspToken.Message->Data.Response->StatusCode; HttpBootPrintErrorMessage (StatusCode); Status =3D ResponseData->Status; // Here Status =3D 00000023 } goto ERROR_5; // goto ERROR_5 } . . . } Note: We have HTTP server configured in Ubuntu Environment. Could you please look into it. Thanks, karunakar _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel This e-mail is intended for the use of the addressee only and may contain p= rivileged, confidential, or proprietary information that is exempt from dis= closure under law. If you have received this message in error, please infor= m us promptly by reply e-mail, then delete the e-mail and destroy any print= ed copy. Thank you.