Date: Sat, 6 Apr 2019 15:54:58 +0700 From: Victor Sudakov <vas@mpeks.tomsk.su> To: freebsd-virtualization@freebsd.org Subject: Re: running FreePBX SNG7 Official Distro Message-ID: <20190406085458.GA89832@admin.sibptus.ru> In-Reply-To: <201904060805.x3685J6G043781@gndrsh.dnsmgr.net> References: <20190406043424.GA59075@admin.sibptus.ru> <201904060805.x3685J6G043781@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Rodney W. Grimes wrote: > >=20 > > [dd] > >=20 > > > >=20 > > > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi > > > > /mnt/EFI/centos/grubx64.efi > > > >=20 > > > > Who is to blame, bhyve or FreePBX's installer? > > > >=20 > > > > How can I tell bhyve's UEFI loader to look for grubx64.efi in a > > > > different place? Or look for a different loader? > > > >=20 > > > > Who says that the image to load should be "\EFI\BOOT\grubx64.efi" a= nd > > > > not "\EFI\BOOT\BOOTX64.EFI" for example? > > >=20 > > > I can not quickly answer that, but lets try the short quick fix > > > and simply copy this file to the right place and see if that > > > gets you up and running.=20 > >=20 > > Yes, copying grubx64.efi to "\EFI\BOOT\" does get the guest up and > > running (I used mfsbsd from a different VM to manipulate the EFI > > partition). >=20 > You can usually use the host by doing mdconfig -f <path+to+diskimage> Unfortunately mdconfig does not work with zvols: root@vas:~ # mdconfig -a -f /dev/zvol/d02/vm/freepbx/disk0=20 mdconfig: /dev/zvol/d02/vm/freepbx/disk0 is not a regular file > > Moreover, I waited (for a long time!) for the EFI interactive shell > > prompt and with a few commands: >=20 > 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? > > Shell> fs0 > > FS0:\> cd \EFI\centos > > FS0:\EFI\centos\> grubx64.efi =20 > >=20 > > I also managed to boot the guest OS all right. > >=20 > > But naturally, the latter fix worked till next reboot only, I don't know > > how to save the new EFI setup in the guest's configuration. >=20 > My recommedation at this time would be to simply copy grubx64.efi > to the right place and leave it there so that it just boots without > any other change. That's what I have done for now. > >=20 > > The hardware UFI BIOSes I've seen so far (not many, I must admit) > > permitted me to save which efi binary I would prefer to boot next time. >=20 > That is done with an efivar, as it stands right now bhyve efi has > no persistant variable storage, a feature that needs to be implemented. I see. [dd] >=20 > > 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? >=20 > 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? --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcqGliAAoJEA2k8lmbXsY0MbMIAINlLEzRMZZ+0gK1E1xAX4BL KHWOMpXkqjEBMwpcehkR3NvB/wUos3v4eq/Zxo9x73fJ7i7qGCVQgHBYJtXH0gZ7 82B64pNL+JUbo2YSrT2BgzsVlRZF9/BPjFlpCwItDqZ3WNgCIiLS9SpK1O7ClVXH Jm4sbwm+7Pkfc6/UCYFYhnoNIwuEWlF7vR3nlmJsXIVGJZl5I/9lBI3xUPVYB0zN sjhz8HMe4sOR9dpOajb4tpx7xTVj/IP8KMJl7Q9HMAj+COr03c6F7Cwlr4w4gqm5 uAL3QdRY1vdIbhY/zeU6uO5uv+NMHCy+ZbWA/mYPuYoJhz592dfZNywv8PJ+7xE= =st07 -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190406085458.GA89832>