Rodney W. Grimes wrote: > > > > > > > > As I stated earlier bhyve is missing percistant efi variables, > > > > and that is most likely the reason that VirtualBox just works > > > > and bhyve does not. > > > > > > > > Probably you well find in your VirtualBox directory a > > > > file that is used to store efivars, that is where the > > > > > > I'll look into the VirtualBox directory tomorrow and report here. > > > > I searched through my disk and was unable to find a persistant efivars > > storage in my VirtualBox 6.0 installation. > > > > A Google search reveals some articles (rather dated I must admit) > > stating that VirtualBox does not support NVRAM emulation for storing efi > > variables: > > > > https://www.virtualbox.org/ticket/14279 > > https://forums.virtualbox.org/viewtopic.php?t=61970 > > My quick search turns up: > https://www.virtualbox.org/svn/vbox/trunk/src/VBox/Devices/EFI/DevEFI.cpp
My quick search turns up that it's there in the code but it is not used, or it is not enabled by default, whatever (it's written in https://forums.virtualbox.org/viewtopic.php?p=402022&sid=02333b87a8a2bba99383449fc08ca317#p402022 ) > > aka source code thet implements efivars stored in nvram. Anyway, I could not find a file in my virtualbox directory which would look like a storage with NVRAM data. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/
signature.asc
Description: PGP signature
