Date: Mon, 11 Mar 2019 13:35:39 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: "Patrick M. Hausen" <hausen@punkt.de> Cc: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, Shawn Webb <shawn.webb@hardenedbsd.org>, freebsd-virtualization@freebsd.org Subject: Re: bhyve: Detecting that a guest kernel has booted Message-ID: <201903112035.x2BKZd0a011550@gndrsh.dnsmgr.net> In-Reply-To: <DAE0486F-B7F3-49E0-B1C1-AA4E6FFE2BBC@punkt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi all, > > > Am 11.03.2019 um 19:09 schrieb Rodney W. Grimes <freebsd-rwg@gndrsh.dnsmgr.net>: > > I have no love for them either, but until we get our UEFI updated > > it is a rather sad state of affairs. > > I routinely boot FreeBSD, Ubuntu and Windows 10 with > UEFI, so I don?t see much that I would consider broken. All 64 bit oses, afaik we can not boot anything 32 bit with our current uefi, which is: This branch is 8930 commits behind tianocore:master. And depends on an external git belonging to Peter Grehan, who is now gone from the project. > > Missing persistence of boot variables (correct term?) is > the only thing that I know of - what else makes it a > sad state, currently? Our GOP code frequently blows up vnc clients is another issue, not sure if that is in the uefi stuff, or if we just have bad vnc layered on top of it. It throws recs that are out of bounds. The embeded PXE code is also rather dated. > Patrick -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201903112035.x2BKZd0a011550>