From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (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 B233521A16ED1 for ; Tue, 13 Jun 2017 23:02:58 -0700 (PDT) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Jun 2017 23:04:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,340,1493708400"; d="scan'208";a="99253780" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by orsmga002.jf.intel.com with ESMTP; 13 Jun 2017 23:04:13 -0700 Received: from fmsmsx117.amr.corp.intel.com (10.18.116.17) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 13 Jun 2017 23:04:13 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx117.amr.corp.intel.com (10.18.116.17) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 13 Jun 2017 23:04:13 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.116]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.56]) with mapi id 14.03.0319.002; Wed, 14 Jun 2017 14:04:08 +0800 From: "Fu, Siyuan" To: Santhapur Naveen , Karunakar P , "edk2-devel@lists.01.org" Thread-Topic: HTTP Boot failed to download NBP file if it is .iso type Thread-Index: AdLhJADZenTRkzHLTdKp4dJtuK+91AAI2B4wAKmnwnAADkPkQAAq8Vsg Date: Wed, 14 Jun 2017 06:04:08 +0000 Message-ID: References: <625A2455CC232F40B0F38F05ACED6D97C8690EA8@Venus2.in.megatrends.com> <625A2455CC232F40B0F38F05ACED6D97C8691546@Venus2.in.megatrends.com> In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97C8691546@Venus2.in.megatrends.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.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: Wed, 14 Jun 2017 06:02:58 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Naveen First let's kick out the HTTP and check whether your SUSE iso image could s= upport RAM disk boot: 1. Go to "RAM Disk Configuration" form in your setup browser. 2. Change the disk memory type to "Reserved" 3. Choose "Create from file" and select the SUSE iso image from a local ha= rddisk or USB disk. 4. After the RAM disk is created, go back to the boot manager, select the = new created RAM disk device to boot from it. If your SUSE iso image could boot in above way, please check whether your B= DS has been updated to support HTTP RAM disk boot. Best Regards, Siyuan > -----Original Message----- > From: Santhapur Naveen [mailto:naveens@amiindia.co.in] > Sent: Tuesday, June 13, 2017 5:32 PM > To: Fu, Siyuan ; Karunakar P > ; edk2-devel@lists.01.org > Subject: RE: HTTP Boot failed to download NBP file if it is .iso type >=20 > Hi Siyuan, >=20 > Thank you for your reply. > And regarding the OS installation, we are able to download SUSE iso (>3 G= B) > from the HTTP server. But the install didn't happen. > May I ask you what could be possible reason? Is there anything else I've > had missed, please let me know. >=20 > Regards, > Naveen >=20 > -----Original Message----- > From: Fu, Siyuan [mailto:siyuan.fu@intel.com] > Sent: Tuesday, June 13, 2017 8:17 AM > To: Santhapur Naveen; Karunakar P; edk2-devel@lists.01.org > Subject: RE: HTTP Boot failed to download NBP file if it is .iso type >=20 > Hi, Karunakar and Naveen >=20 > Status 00000023 is EFI_HTTP_ERROR, which means the HTTP server replied an > HTTP error. The HTTP error code is placed in HttpIo->RspToken.Message- > >Data.Response->StatusCode, and will be displayed in > HttpBootPrintErrorMessage() function. >=20 > If a downloaded NBP is a RAM disk image, the BDS will try to find a boot > file inside it according UEFI 2.7 section 3.5.1 "Boot via the Simple File > Protocol". >=20 > Best Regards, > Siyuan >=20 >=20 > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > Santhapur Naveen > Sent: Saturday, June 10, 2017 1:49 AM > To: Karunakar P; edk2-devel@lists.01.org > Subject: Re: [edk2] HTTP Boot failed to download NBP file if it is .iso > type >=20 > 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= ? >=20 > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > Karunakar 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 >=20 > Hi All, >=20 > We have facing an issue with HTTP boot. >=20 > [Issue] > HTTP Boot failed to download NBP file if it is an .iso type >=20 > [Reproduction Steps] >=20 > 1. Configure HTTP Server in Ubuntu environment. >=20 > 2. Place any iso image as NBP file. >=20 > 3. Perform UEFI HTTPv4 boot. >=20 > [Result] > DHCP process was success, But Failed to download NBP file. >=20 > [Observations] >=20 > 1. As per UEFI spec "23.7.1 Boot from URL" (UEFI 2.6, page 1222). >=20 > Here is what the section says about binary image returned by HTTP server: >=20 > "...the binary image [..] is a UEFI-formatted executable[...], or it coul= d > be mounted as a RAM disk which contains a UEFI-compliant file system (see > Section 12.3)." >=20 > We're interested in exploring second scenario, when downloaded image is a > UEFI-compliant file system. >=20 > Section "23.7.3.1 Device Path" on page 1226 provides examples of image UR= L: > http://192.168.1.100/boot.iso >=20 > The specification also says that "the HTTP Boot driver will register RAM > disk with the downloaded NBP, by appending a RamDisk device node to the > device path above, like...". >=20 >=20 >=20 > HttpBootDxe is doing this.But NBP file itself failing to download in the > case of iso image. >=20 >=20 >=20 > 2. HTTP boot fails in the following function >=20 >=20 >=20 > HttpBootGetBootFile() -> >=20 >=20 >=20 > EFI_STATUS >=20 > HttpBootGetBootFile ( >=20 > IN HTTP_BOOT_PRIVATE_DATA *Private, >=20 > IN BOOLEAN HeaderOnly, >=20 > IN OUT UINTN *BufferSize, >=20 > OUT UINT8 *Buffer, >=20 > OUT HTTP_BOOT_IMAGE_TYPE *ImageType >=20 > ) >=20 > { >=20 > . >=20 > . >=20 > . >=20 > Status =3D HttpIoRecvResponse ( >=20 > &Private->HttpIo, >=20 > TRUE, >=20 > ResponseData >=20 > ); >=20 > // Here the Status value is Success and ResponseData->Status =3D 00000023 >=20 >=20 >=20 > if (EFI_ERROR (Status) || EFI_ERROR (ResponseData->Status)) { >=20 > if (EFI_ERROR (ResponseData->Status)) { >=20 > StatusCode =3D HttpIo->RspToken.Message->Data.Response->StatusCode; >=20 > HttpBootPrintErrorMessage (StatusCode); >=20 > Status =3D ResponseData->Status; >=20 > // Here Status =3D 00000023 >=20 >=20 >=20 > } >=20 > goto ERROR_5; // goto ERROR_5 >=20 > } >=20 > . >=20 > . >=20 > . >=20 > } >=20 >=20 >=20 > Note: > We have HTTP server configured in Ubuntu Environment. >=20 > Could you please look into it. >=20 >=20 > Thanks, > karunakar >=20 >=20 > _______________________________________________ > 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 > privileged, confidential, or proprietary information that is exempt from > disclosure under law. If you have received this message in error, please > inform us promptly by reply e-mail, then delete the e-mail and destroy an= y > printed copy. Thank you. > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel