Date: Tue, 27 Sep 2016 06:37:56 +1000 From: Peter Grehan <grehan@freebsd.org> To: Stephan CHEDLIVILI <stephan@theched.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: UEFI bhyve and EFI shell at boot Message-ID: <c929bfa8-7f88-df32-ba8d-e37653fd50bd@freebsd.org> In-Reply-To: <3257247.Qm6eVUophb@panda.test.me> References: <9276239.oRRSstIAVb@panda.test.me> <CY4PR12MB14478911B5A62D9C8FB8F86FA3CD0@CY4PR12MB1447.namprd12.prod.outlook.com> <20160926123157.GO97879@e-new.0x20.net> <3257247.Qm6eVUophb@panda.test.me>
next in thread | previous in thread | raw e-mail | index | archive | help
>> That's also true for Ubuntu 16.04 > > But this problem does not happen with Fedora 4.7 It's guest-specific. Recent Fedora has the same issue, though RHEL/Centos, FreeBSD, and Windows don't since they place the bootloader in a standard location. There is a fix in progress for this to write out the UEFI nvvars to file so they can be preserved across a bhyve VM power cycle. later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c929bfa8-7f88-df32-ba8d-e37653fd50bd>