Re: running FreePBX SNG7 Official Distro
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 zvol cant you just do > > > gpart show /dev/zvol/d02/vm/freepbx/disk0 > > > > > > and > > > mount -t msdosfs /dev/zvol/d02/vm/freepbx/disk0p2 > > > > No I can't if the zvol is in the "volmode=dev" mode which is the default. > > > > This is the default for a reason: it's no good exposing scores of always > > coming and going guest geoms to the host system. I think you can even > > get a conflict of labels or something like that one day. > > So it may take a few more commands but it should be > possible to do this from the host side using host > side tools without having to boot a guest to make > these corrections. I'm not aware of such commands. If anyone knows them please share with us. Moreover, I already asked a similar question in February under the topic "mounting/exporting/importing a zfs volume" and nobody gave a recipe. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ signature.asc Description: PGP signature
Re: running FreePBX SNG7 Official Distro
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 > > > > > > > present), for > > > > > > > example? > > > > > > > > > > > > I suspect that what ever guest you installed installed something > > > > > > else someplace, either within the eft partition, or possibly in > > > > > > the MBR? > > > > > > > > > > Do you mean to say, the guest installing something else someplace can > > > > > influence the boot sequence of bhyve efi? > > > > > > > > The guest created all of the bits on that zvol, > > > > it can influence many things. There is probably a tiny initial > > > > stub that efi loads that has this bath to grubx64.efi codded in > > > > it and that is what is causing this issue. > > > > > > It is very important to find and debug it because Oracle VirtualBox in > > > UEFI mode installs and runs this guest just fine. So it must be some > > > issue in bhyve itself. > > > > > > Here is the complete archive of everything the guest created in the EFI > > > partition: http://admin.sibptus.ru/~vas/freepbx.tar.gz > > > can you find those confusing bits? > > > > I got it! bhyve does the right thing: it tries to boot BOOTX64.EFI, but > > BOOTX64.EFI makes it look for grubx64.efi. So BOOTX64.EFI must be some > > kind of chain loader. > > And it brobably tries to read a efivariable, and if that variable > is not set it defaults to grubx64.efi. This bootx64.efi is something > the guest installed into the EFI partition, hence my assertion that > the issue is with something the guest installed is some what valid. Do you think the guest OS installer set some efi variable during the installation process, which bhyve did not save? That would explain a lot. > > > > > > Moreover, I waited (for a long time!) for the EFI interactive shell > > > > > > prompt and with a few commands: > > > > > > > > > > Yes, the timeout is very long, and I do not know that we > > > > > document anyplace that if you wait long enough at a failed > > > > > boot you do get a EFI shell prompt eventually. > > > > > > > > Can I press some key to escape to the EFI shell? > > > Not that I am aware of. > > > > It's a major problem! There must be a well-known way to break the boot > > sequence any time and enter the EFI shell. > > Agreed, hopefully those working on edk2 take note and either > chime in with what that way is, or create a bug and track > so that someone may fix this issue. Would it be useful to create a PR in the FreeBSD bugtracker with a feature request? > > > > It is very important to find and debug it because Oracle VirtualBox in > > UEFI mode installs and runs this guest just fine. So it must be some > > issue in bhyve itself. > > 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 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 settings, and not on a disk. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ signature.asc Description: PGP signature
Re: running FreePBX SNG7 Official Distro
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 settings, and not on a disk. > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49@fidonet http://vas.tomsk.ru/ I just wanted to confirm that this is indeed an EVIVARS problem, because through CBSD (which uses Refind [1]) FreePBX 1805-2 boots without any problems. Therefore, as Rodney said, you can try using a third-party EFI boot manager. And just wait until someone finds the time to add support for UEFI VARS in bhyve. [1] - http://www.rodsbooks.com/refind/ ___ 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"
unsubscribe
> On 7 Apr 2019, at 13:00, freebsd-virtualization-requ...@freebsd.org wrote: > > Send freebsd-virtualization mailing list submissions to > freebsd-virtualization@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > or, via email, send a message with subject or body 'help' to > freebsd-virtualization-requ...@freebsd.org > > You can reach the person managing the list at > freebsd-virtualization-ow...@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-virtualization digest..." > > > Today's Topics: > > 1. Re: running FreePBX SNG7 Official Distro (Victor Sudakov) > 2. Re: running FreePBX SNG7 Official Distro (Victor Sudakov) > 3. Re: running FreePBX SNG7 Official Distro (Rodney W. Grimes) > 4. Re: running FreePBX SNG7 Official Distro (Rodney W. Grimes) > 5. Re: running FreePBX SNG7 Official Distro (Victor Sudakov) > 6. Re: running FreePBX SNG7 Official Distro (Victor Sudakov) > > > -- > > Message: 1 > Date: Sun, 7 Apr 2019 09:37:43 +0700 > From: Victor Sudakov > To: freebsd-virtualization@freebsd.org > Subject: Re: running FreePBX SNG7 Official Distro > Message-ID: <20190407023743.gb99...@admin.sibptus.ru> > Content-Type: text/plain; charset="us-ascii" > > 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 zvol cant you just do >> gpart show /dev/zvol/d02/vm/freepbx/disk0 >> >> and >> mount -t msdosfs /dev/zvol/d02/vm/freepbx/disk0p2 > > No I can't if the zvol is in the "volmode=dev" mode which is the default. > > This is the default for a reason: it's no good exposing scores of always > coming and going guest geoms to the host system. I think you can even > get a conflict of labels or something like that one day. > >>>>> Moreover, I waited (for a long time!) for the EFI interactive shell >>>>> prompt and with a few commands: >>>> >>>> Yes, the timeout is very long, and I do not know that we >>>> document anyplace that if you wait long enough at a failed >>>> boot you do get a EFI shell prompt eventually. >>> >>> Can I press some key to escape to the EFI shell? >> Not that I am aware of. > > It's a major problem! There must be a well-known way to break the boot > sequence any time and enter the EFI shell. > >>>>> 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? >>>> >>>> I suspect that what ever guest you installed installed something >>>> else someplace, either within the eft partition, or possibly in >>>> the MBR? >>> >>> Do you mean to say, the guest installing something else someplace can >>> influence the boot sequence of bhyve efi? >> >> The guest created all of the bits on that zvol, >> it can influence many things. There is probably a tiny initial >> stub that efi loads that has this bath to grubx64.efi codded in >> it and that is what is causing this issue. > > It is very important to find and debug it because Oracle VirtualBox in > UEFI mode installs and runs this guest just fine. So it must be some > issue in bhyve itself. > > Here is the complete archive of everything the guest created in the EFI > partition: http://admin.sibptus.ru/~vas/freepbx.tar.gz > can you find those confusing bits? > > The standard procedure should be as follows: > > Automated detection relies on standardized file paths to the OS > loader, with the path varying depending on the computer architecture. > The format of the file path is defined as > /EFI/BOOT/BOOT.EFI; for > example, the file path to the OS loader on an x86-64 system is > /efi/BOOT/BOOTX64.EFI and efi\boot\bootaa64.efi on ARM64 architecture. > > Nothing about grub*.efi. But only bhyve is confused, VirtualBox is not. > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/4
Re: running FreePBX SNG7 Official Distro
> 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 settings, and not on a disk. > > > > -- > > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > > 2:5005/49@fidonet http://vas.tomsk.ru/ > > I just wanted to confirm that this is indeed an EVIVARS problem, > because through CBSD (which uses Refind [1]) FreePBX 1805-2 > boots without any problems. Therefore, as Rodney said, you can try > using a third-party EFI boot manager. > And just wait until someone finds the time to add support for UEFI > VARS in bhyve. Thank you for the analysis and confirmation! > [1] - http://www.rodsbooks.com/refind/ -- 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"
Re: running FreePBX SNG7 Official Distro
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 they recommend using startup.nsh instead. I wonder if bhyve's efi implementation supports startup.nsh. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ signature.asc Description: PGP signature
