From owner-freebsd-virtualization@freebsd.org Wed Feb 8 06:36:25 2017 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2472BCC7AF3 for ; Wed, 8 Feb 2017 06:36:25 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id D53C597D for ; Wed, 8 Feb 2017 06:36:24 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 092562052E02 for ; Wed, 8 Feb 2017 16:35:55 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 025A82809E1 for ; Wed, 8 Feb 2017 16:35:55 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Ewj3Nk9p03J0 for ; Wed, 8 Feb 2017 16:35:54 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (c-67-180-92-13.hsd1.ca.comcast.net [67.180.92.13]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 71C222809D3; Wed, 8 Feb 2017 16:35:52 +1000 (AEST) Subject: Re: Ubuntu UEFI Won't Reboot To: Vincent Olivier References: <23FEB7AF-5CE5-4CAA-B920-E4260FDEF4FA@up4.com> Cc: FreeBSD virtualization From: Peter Grehan Message-ID: <478af3ec-1e22-5031-dce4-36cf8f6c4a0d@freebsd.org> Date: Tue, 7 Feb 2017 22:36:11 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <23FEB7AF-5CE5-4CAA-B920-E4260FDEF4FA@up4.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=YJDv8VOx c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=IkcTkHD0fZMA:10 a=n2v9WMKugxEA:10 a=6I5d2MoRAAAA:8 a=n7CAqfBY4TCReaRMAVYA:9 a=QEXdDO2ut3YA:10 a=MaZOG54Q8MAA:10 a=IjZwj45LgO3ly-622nXo:22 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 08 Feb 2017 06:36:25 -0000 Hi Vincent, > So after a minute or two, I get the UEFI Shell and when I exit, I get > something that appears to be the bhyve BIOS (?) when I go from there > to the Boot Maintenance Manager, and then =C2=AB Boot From File =C2=BB = I can > select the block device, then , then , then grubx64.efi > and then I get the Grub menu from which I can select Ubuntu, which in > turn boots the OS just fine. Now, the question is, can I configure > bhyve to look for that file instead of whatever it is currently > looking for and not finding? Or do I have to modify the ESP? This is a known issue in that UEFI nvvars aren't written to permanent=20 storage (e.g. see=20 https://lists.freebsd.org/pipermail/freebsd-virtualization/2016-September= /004808.html).=20 A number of guest o/s's use nvvars to handle boot order/non-standard=20 boot loader names etc, and expect changes to these to be persistent. There is a fix that just needs to be comitted (to both bhyve and=20 UEFI/bhyve). Hope to get to that soon. later, Peter.