From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.nue.novell.com (smtp.nue.novell.com [195.135.221.5]) (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 A20D821A143D0 for ; Wed, 14 Jun 2017 00:08:45 -0700 (PDT) Received: from emea4-mta.ukb.novell.com ([10.120.13.87]) by smtp.nue.novell.com with ESMTP (TLS encrypted); Wed, 14 Jun 2017 09:09:57 +0200 Received: from GaryWorkstation (nwb-a10-snat.microfocus.com [10.120.13.202]) by emea4-mta.ukb.novell.com with ESMTP (TLS encrypted); Wed, 14 Jun 2017 08:09:42 +0100 Date: Wed, 14 Jun 2017 15:09:35 +0800 From: Gary Lin To: Santhapur Naveen Cc: "Fu, Siyuan" , Karunakar P , "edk2-devel@lists.01.org" Message-ID: <20170614070935.2s3g32ikhvviod6f@GaryWorkstation> References: <625A2455CC232F40B0F38F05ACED6D97C8690EA8@Venus2.in.megatrends.com> <625A2455CC232F40B0F38F05ACED6D97C8691546@Venus2.in.megatrends.com> MIME-Version: 1.0 In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97C8691546@Venus2.in.megatrends.com> User-Agent: NeoMutt/20170421 (1.8.2) 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 07:08:46 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jun 13, 2017 at 09:31:49AM +0000, Santhapur Naveen wrote: > Hi Siyuan, > > Thank you for your reply. > And regarding the OS installation, we are able to download SUSE iso (>3 GB) 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. Which version of SLE are you using? SUSE Linux Enterprise supports EFI_RAM_DISK_PROTOCOL since 12 SP2, so any image older than 12 SP2 would not work. Per my test, as long as the firmware loads the iso into memory, the iso works as an additional CD-ROM, and the firmware can boot into the iso directly. Cheers, Gary Lin > > Regards, > Naveen > > -----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 > > Hi, Karunakar and Naveen > > 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. > > 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". > > Best Regards, > Siyuan > > > -----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 > > 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 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 > > 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 Section 12.3)." > > We're interested in exploring second scenario, when downloaded image is a UEFI-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 disk with the downloaded NBP, by appending a RamDisk device node to the device path above, like...". > > > > HttpBootDxe is doing this.But NBP file itself failing to download in the case 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 = HttpIoRecvResponse ( > > &Private->HttpIo, > > TRUE, > > ResponseData > > ); > > // Here the Status value is Success and ResponseData->Status = 00000023 > > > > if (EFI_ERROR (Status) || EFI_ERROR (ResponseData->Status)) { > > if (EFI_ERROR (ResponseData->Status)) { > > StatusCode = HttpIo->RspToken.Message->Data.Response->StatusCode; > > HttpBootPrintErrorMessage (StatusCode); > > Status = ResponseData->Status; > > // Here Status = 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 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 any printed copy. Thank you. > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel