> Victor Sudakov 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 aka source code thet implements efivars stored in nvram. > they recommend using startup.nsh instead. I wonder if bhyve's efi > implementation supports startup.nsh. I believe that is how the alternate boot selector someone pointed at gets hooked in. > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49@fidonet http://vas.tomsk.ru/ -- Rod Grimes rgri...@freebsd.org _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"