Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 Apr 2019 00:39:01 -0700 (PDT)
From:      "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>
To:        Victor Sudakov <vas@mpeks.tomsk.su>
Cc:        freebsd-virtualization@freebsd.org
Subject:   Re: running FreePBX SNG7 Official Distro
Message-ID:  <201904080739.x387d1T9054124@gndrsh.dnsmgr.net>
In-Reply-To: <20190408050144.GA56879@admin.sibptus.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
> 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                                                 rgrimes@freebsd.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201904080739.x387d1T9054124>