From owner-freebsd-virtualization@freebsd.org Fri Mar 22 16:04:50 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60FDE1549F76 for ; Fri, 22 Mar 2019 16:04:50 +0000 (UTC) (envelope-from d.scott.phillips@intel.com) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "orsmga106.jf.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B3E9B890E1 for ; Fri, 22 Mar 2019 16:04:48 +0000 (UTC) (envelope-from d.scott.phillips@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Mar 2019 09:04:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,256,1549958400"; d="scan'208";a="154842341" Received: from dsp-dsk1.jf.intel.com (HELO localhost) ([10.54.70.10]) by fmsmga004.fm.intel.com with ESMTP; 22 Mar 2019 09:04:45 -0700 From: D Scott Phillips To: Rebecca Cran , freebsd-virtualization@freebsd.org Subject: Re: Updating uefi-edk2-bhyve In-Reply-To: <1fe3ca3f-be70-99db-e7c0-35c9194c97e4@bluestop.org> References: <86muln68ld.fsf@intel.com> <1fe3ca3f-be70-99db-e7c0-35c9194c97e4@bluestop.org> Date: Fri, 22 Mar 2019 09:04:45 -0700 Message-ID: <86r2ayao9u.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: B3E9B890E1 X-Spamd-Bar: -------- Authentication-Results: mx1.freebsd.org; dmarc=pass (policy=none) header.from=intel.com; spf=pass (mx1.freebsd.org: domain of d.scott.phillips@intel.com designates 134.134.136.126 as permitted sender) smtp.mailfrom=d.scott.phillips@intel.com X-Spamd-Result: default: False [-8.79 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:134.134.136.126/32]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[126.136.134.134.list.dnswl.org : 127.0.9.2]; MX_GOOD(-0.01)[cached: mga04.intel.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.99)[-0.989,0]; DMARC_POLICY_ALLOW(-0.50)[intel.com,none]; IP_SCORE(-1.79)[ipnet: 134.134.136.0/24(-4.94), asn: 4983(-3.96), country: US(-0.07)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4983, ipnet:134.134.136.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; WHITELIST_SPF_DKIM(-3.00)[intel.com:s:+] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Mar 2019 16:04:50 -0000 Rebecca Cran writes: > This is awesome! Updating to a newer edk2 has been on my todo list for > a while. > > However I don=E2=80=99t see a BhyvePkg in the first link you posted. And = could > you confirm that you got HTTP boot working on FreeBSD as well as Linux > and Windows? I thought loader changes were needed for that to work, to > enable the kernel to be fetched via http. Sorry, I didn't write that very clearly, what I meant was that I tested local boot with those 3 os's, and then I also tested HTTP Boot and it was working well enough to fetch and start loader_lua.efi. So I haven't fully booted FreeBSD over HTTP, just got the loader running. Just using the loader's nfs support will probably be good enough for my use, so I don't plan on looking at http support for the loader at the moment. > On 3/21/19 6:44 PM, D Scott Phillips wrote: > > Hi freebsd-virtualization, > > > > Recently I wanted to be able to do UEFI HTTP Boot in bhyve, so I've > > rebased the bhyve firmware up to the latest upstream tag, > > edk2-stable201903. You can find the firmware here: > > > > https://gitlab.com/scott-ph/edk2/tree/wip/2019-03/v2-bhyve-rebase-edk2-= stable201903 > > > Thanks! I realized you've removed BhyvePkg and ported OvmfPkg to run > under Bhyve, which is perfect. I've successfully built OvmfPkgX64 with > your changes and can boot Bhyve to the UEFI Shell. Right, my understanding from looking at the history is that BhyvePkg started life as a copy of the OvmfPkg directory. So I rewrote the patches to be deltas against OvmfPkg so that rebasing would be tractable. In the end I chose to leave them that way to make the life of the next rebaser easier.