Updating uefi-edk2-bhyve
D Scott Phillips
d.scott.phillips at intel.com
Fri Mar 22 16:04:50 UTC 2019
Rebecca Cran <rebecca at bluestop.org> writes:
> This is awesome! Updating to a newer edk2 has been on my todo list for
> a while.
>
> However I don’t 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.
More information about the freebsd-virtualization
mailing list