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 226F221AE263C for ; Wed, 21 Jun 2017 04:45:34 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6BFDA82055; Wed, 21 Jun 2017 17:19:03 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 55AE982046; Wed, 21 Jun 2017 17:19:03 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Wed, 21 Jun 2017 17:19:03 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Wed, 21 Jun 2017 17:16:54 +0530 From: Karunakar P To: "Fu, Siyuan" , "edk2-devel@lists.01.org" Thread-Topic: HTTP Boot failed to download NBP file if it is .iso type Thread-Index: AdLhJADZenTRkzHLTdKp4dJtuK+91AAI2B4wAKmnwnAADkPkQAAq8VsgAWvCWVA= Date: Wed, 21 Jun 2017 11:46:54 +0000 Message-ID: References: <625A2455CC232F40B0F38F05ACED6D97C8690EA8@Venus2.in.megatrends.com> <625A2455CC232F40B0F38F05ACED6D97C8691546@Venus2.in.megatrends.com> In-Reply-To: Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.200] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-23146.006 X-TM-AS-Result: No--27.751-5.0-31-10 X-imss-scan-details: No--27.751-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23146.006 X-TMASE-Result: 10--27.750600-10.000000 X-TMASE-MatchedRID: Rp71wniPtoPM/ECkaAy/4lPjo7D4SFg4pLOv1YSZntytj24Xqh0yXJXW hmtVIiN3qSBo8TKOOgO2a6lsK6mSwtUMAwTDOBnsFYJUGv4DL3wrHkgIan9a0cg9ufahCGm1M4q s8hVLF7ae9KDDJzvibygywW45LfL0k3shAVOzj+LmAId+2bAQwlHewY36PuY0tivu7VTPVKIM2b 9SLN604iUt2Ltcg1pzlYsc85ylG6IM0+A2uk9QHVWeeIqHthMLC/ExpXrHizwzFWOYrWw6A8Xc7 IYNlQVC2BXP32nYpKA0RPefk8cJwKGsq9dfniq5T7jCYv2QJPGO74ZfTyAQsAZbeEWcL03VmIpz nkhMtm+P5vZTh1OvvxSG2FrT70yK5RxXFd4TFVaM29hkek7XdxNtTUpgahCnBtslyrlLAqJKTtp DX7vbCiFxdHijRu1bzlVLPIrowwZWL+AaoC7iVAPZZctd3P4ByZYiu4ZQ/Ok9l6vw5mwGC3qEb0 pCqT/4UDYGlQbJDZb/FE1DVQu2yhAq4jU0QZlBydRP56yRRA9LxPtqS8Bm508K6ja+ec1y4MZM1 Q/ZcvCPWZvDr+0qaz8hzx5rqlJosaAw0gxug1WzI1v7J4hECnTlVE0ir32pLDwZoJ12UtfnU/zl xreh3uLzNWBegCW2pWxvdtZwy35WdFebWIc3VsRB0bsfrpPI6T/LTDsmJmg= 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: Wed, 21 Jun 2017 11:45:34 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, Verified that BDS has been updated to support HTTP RAM disk boot. And able = to download SUSE iso (>3 GB) from the HTTP server. But the install stops in= middle. I've checked SUSE iso image could support RAM disk boot or NOT with below s= teps 1. Go to "RAM Disk Configuration" form setup browser. 2. Change the disk memory type to "Reserved" 3. Choose "Create from file" and select the SUSE iso image from a local US= B 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. =20 When I tries to boot from it, installation stops in middle. Note: Tried with SLE-12-SP2-Server-DVD-x86_64-GM-DVD1.iso If there anything else I've missed please let me know. Could you please help which ISO images supports this RAM Disk boot? Have you verified HTTP boot with any iso image? =20 Thanks, karunakar -----Original Message----- From: Fu, Siyuan [mailto:siyuan.fu@intel.com]=20 Sent: Wednesday, June 14, 2017 11:34 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, 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=20 > ; 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=20 > (>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=20 > 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=20 > an HTTP error. The HTTP error code is placed in=20 > 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=20 > boot file inside it according UEFI 2.7 section 3.5.1 "Boot via the=20 > Simple File Protocol". >=20 > Best Regards, > Siyuan >=20 >=20 > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of=20 > 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=20 > .iso type >=20 > Even if we are able to download an ISO file successfully, how will=20 > 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=20 > 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=20 > 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=20 > could be mounted as a RAM disk which contains a UEFI-compliant file=20 > system (see Section 12.3)." >=20 > We're interested in exploring second scenario, when downloaded image=20 > 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=20 > RAM disk with the downloaded NBP, by appending a RamDisk device node=20 > to the device path above, like...". >=20 >=20 >=20 > HttpBootDxe is doing this.But NBP file itself failing to download in=20 > 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=20 > 00000023 >=20 >=20 >=20 > if (EFI_ERROR (Status) || EFI_ERROR (ResponseData->Status)) { >=20 > if (EFI_ERROR (ResponseData->Status)) { >=20 > StatusCode =3D=20 > 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=20 > contain privileged, confidential, or proprietary information that is=20 > exempt from disclosure under law. If you have received this message in=20 > error, please inform us promptly by reply e-mail, then delete the=20 > 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