Subbsd wrote:
> On Sun, Apr 7, 2019 at 11:15 AM Victor Sudakov wrote:
>
> > I'll look into the VirtualBox directory tomorrow and report here. I was
> > under the impression that efivars are stored in a configuration file in
> > the EFI partition but I was probably wrong, they are kept in NVRAM
>
Victor Sudakov wrote:
> > > > 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
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
> 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
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
> On Sun, Apr 7, 2019 at 11:15 AM Victor Sudakov wrote:
>
> > I'll look into the VirtualBox directory tomorrow and report here. I was
> > under the impression that efivars are stored in a configuration file in
> > the EFI partition but I was probably wrong, they are kept in NVRAM
> > somewhere,
On Sun, Apr 7, 2019 at 11:15 AM Victor Sudakov wrote:
> I'll look into the VirtualBox directory tomorrow and report here. I was
> under the impression that efivars are stored in a configuration file in
> the EFI partition but I was probably wrong, they are kept in NVRAM
> somewhere, like BIOS
Rodney W. Grimes wrote:
> > > > > > > I can guess that it looks for a FAT16 partition in the GPT with
> > > > > > > the type
> > > > > > > "efi" but the rest is a mystery for me. Why is it trying to find
> > > > > > > "grubx64.efi" and not the default "boot64.efi" (which is
> > > > > > >
Rodney W. Grimes wrote:
> > > > >
> > > > > You can usually use the host by doing mdconfig -f
> > > >
> > > > Unfortunately mdconfig does not work with zvols:
> > > >
> > > > root@vas:~ # mdconfig -a -f /dev/zvol/d02/vm/freepbx/disk0
> > > > mdconfig: /dev/zvol/d02/vm/freepbx/disk0 is not a
> Victor Sudakov wrote:
> > > > > > I can guess that it looks for a FAT16 partition in the GPT with the
> > > > > > type
> > > > > > "efi" but the rest is a mystery for me. Why is it trying to find
> > > > > > "grubx64.efi" and not the default "boot64.efi" (which is present),
> > > > > > for
> >
> Rodney W. Grimes wrote:
> > > >
> > > > You can usually use the host by doing mdconfig -f
> > >
> > > Unfortunately mdconfig does not work with zvols:
> > >
> > > root@vas:~ # mdconfig -a -f /dev/zvol/d02/vm/freepbx/disk0
> > > mdconfig: /dev/zvol/d02/vm/freepbx/disk0 is not a regular file
Victor Sudakov wrote:
> > > > > I can guess that it looks for a FAT16 partition in the GPT with the
> > > > > type
> > > > > "efi" but the rest is a mystery for me. Why is it trying to find
> > > > > "grubx64.efi" and not the default "boot64.efi" (which is present), for
> > > > > example?
> > > >
Rodney W. Grimes wrote:
> > >
> > > You can usually use the host by doing mdconfig -f
> >
> > Unfortunately mdconfig does not work with zvols:
> >
> > root@vas:~ # mdconfig -a -f /dev/zvol/d02/vm/freepbx/disk0
> > mdconfig: /dev/zvol/d02/vm/freepbx/disk0 is not a regular file
>
> If its a
> Rodney W. Grimes wrote:
> > >
> > > [dd]
> > >
> > > > >
> > > > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi
> > > > > /mnt/EFI/centos/grubx64.efi
> > > > >
> > > > > Who is to blame, bhyve or FreePBX's installer?
> > > > >
> > > > > How can I tell bhyve's UEFI loader to look for
Rodney W. Grimes wrote:
> >
> > [dd]
> >
> > > >
> > > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi
> > > > /mnt/EFI/centos/grubx64.efi
> > > >
> > > > Who is to blame, bhyve or FreePBX's installer?
> > > >
> > > > How can I tell bhyve's UEFI loader to look for grubx64.efi in a
> > > >
-- Start of PGP signed section.
> Rodney W. Grimes wrote:
>
> [dd]
>
> > >
> > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi
> > > /mnt/EFI/centos/grubx64.efi
> > >
> > > Who is to blame, bhyve or FreePBX's installer?
> > >
> > > How can I tell bhyve's UEFI loader to look for grubx64.efi in
Rodney W. Grimes wrote:
[dd]
> >
> > root@mfsbsd:~ # find /mnt/ -name grubx64.efi
> > /mnt/EFI/centos/grubx64.efi
> >
> > Who is to blame, bhyve or FreePBX's installer?
> >
> > How can I tell bhyve's UEFI loader to look for grubx64.efi in a
> > different place? Or look for a different loader?
-- Start of PGP signed section.
> Victor Sudakov wrote:
> >
> > Has anyone tried to run FreePBX under bhyve? That's what I get trying to
> > start the vm after a successful automatic install from the ISO image:
> >
> > Boot Failed. EFI DVD/CDROM
> > Failed to set MokListRT: Invalid Parameter
> >
Victor Sudakov wrote:
>
> Has anyone tried to run FreePBX under bhyve? That's what I get trying to
> start the vm after a successful automatic install from the ISO image:
>
> Boot Failed. EFI DVD/CDROM
> Failed to set MokListRT: Invalid Parameter
> Failed to open \EFI\BOOT\grubx64.efi - Not
Dear Colleagues,
Has anyone tried to run FreePBX under bhyve? That's what I get trying to
start the vm after a successful automatic install from the ISO image:
Boot Failed. EFI DVD/CDROM
Failed to set MokListRT: Invalid Parameter
Failed to open \EFI\BOOT\grubx64.efi - Not Found
Failed to load
20 matches
Mail list logo
