From owner-freebsd-virtualization@freebsd.org Sat Apr 6 04:34:27 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0D57156BD4B for ; Sat, 6 Apr 2019 04:34:26 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0DF058D3F7 for ; Sat, 6 Apr 2019 04:34:25 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=1BK4A59RaQF+sBeyuaWU7JGn1nyOijGZb3xKqISwqtQ=; b=Ix3U/r1wNyVpGDnq090YBTKFjs q+LdL82o1l9gd2Fo2V9WeoaZSzWu2eJqf9KVgrZdpkvFaR6SmgpHbAottnJdoqN8qBBmdQbY00sAV XPERoYfG1IXp3YmPjubehEL3x1DfqZ+u6SUvcJDFUC26hKb4uX9ZYpCnFFR5llDlyn14=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hCd28-000Fwc-KC for freebsd-virtualization@freebsd.org; Sat, 06 Apr 2019 11:34:24 +0700 Date: Sat, 6 Apr 2019 11:34:24 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: running FreePBX SNG7 Official Distro Message-ID: <20190406043424.GA59075@admin.sibptus.ru> References: <20190405161227.GA73383@admin.sibptus.ru> <201904051920.x35JKKGL040719@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <201904051920.x35JKKGL040719@gndrsh.dnsmgr.net> X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Apr 2019 04:34:27 -0000 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Rodney W. Grimes wrote: [dd] > >=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" and > > 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 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). Moreover, I waited (for a long time!) for the EFI interactive shell prompt and with a few commands: Shell> fs0 FS0:\> cd \EFI\centos FS0:\EFI\centos\> grubx64.efi =20 I also managed to boot the guest OS all right. 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. 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. > That would also tell us that we have > what is actually a common efi system failure problem in that > stuff looks in the wrong place. It seems so. > I have read many an install > instruction that just says copy this file to these too places > as some bioses look for it in one place and others look for it > someplace else. I would very much appreciate a link to some such instruction about uefi-edk2-bhyve: namely how and where it looks for what on boot, and if I can create a menu for example, or change its startup procedure. 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 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcqCxQAAoJEA2k8lmbXsY0X9wIAIURyqCsKD03TytqspB8XQBs vdB86y4SEzndbRcFctYMp0dadZiouvJnaCM4uIwVrZ1A/IIc3wVuNVQp2YixDU2D h81AEBOh5DaiREsmkHhM3EMENPCvKNq7/d6EscktiwZydjUtzJEumkoKzq92NMBE JMrblazvmJB/g+7hUpQ6Z3XfGMNqNQy35z4i3DKJy0nz5Jq9u5DndNjwOUTNhyXu 3WDy+OwU9+6JAPmb0eQiQitKkbQmOYX3v2hsGnJs2X63A+aqJHTrcbj4Ts7EuHsR VEVAfBvZKOsQJxyxGt0kZKU7mrCGNuMHzW0TELivXIffJvFRv/PJGKYLJPAfiuc= =z84A -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC--