From owner-freebsd-virtualization@freebsd.org Mon Sep 26 14:21:52 2016 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 54989BE954B for ; Mon, 26 Sep 2016 14:21:52 +0000 (UTC) (envelope-from stephan@theched.org) Received: from mail.theched.org (theched.org [91.121.195.242]) by mx1.freebsd.org (Postfix) with ESMTP id 22FE8636 for ; Mon, 26 Sep 2016 14:21:51 +0000 (UTC) (envelope-from stephan@theched.org) Received: from panda.test.me (42-98-98-155.static.netvigator.com [42.98.98.155]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.theched.org (Postfix) with ESMTPSA id 6B8751744AA for ; Mon, 26 Sep 2016 14:22:40 +0000 (UTC) From: Stephan CHEDLIVILI To: "freebsd-virtualization@freebsd.org" Subject: Re: UEFI bhyve and EFI shell at boot Date: Mon, 26 Sep 2016 22:21:48 +0800 Message-ID: <3257247.Qm6eVUophb@panda.test.me> User-Agent: KMail/4.14.10 (FreeBSD/11.0-RC3; KDE/4.14.10; amd64; ; ) In-Reply-To: <20160926123157.GO97879@e-new.0x20.net> References: <9276239.oRRSstIAVb@panda.test.me> <20160926123157.GO97879@e-new.0x20.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Mon, 26 Sep 2016 14:21:52 -0000 On Monday 26 September 2016 14:31:57 Lars Engels wrote: > On Mon, Sep 26, 2016 at 05:56:59AM +0000, Justin Holcomb wrote: > > > From: owner-freebsd-virtualization@freebsd.org > > > on behalf of Stephan > > > CHEDLIVILI Sent: Saturday, September 24, 2016 > > > 12:50 AM > > > To: freebsd-virtualization@freebsd.org > > > Subject: UEFI bhyve and EFI shell at boot > > > > > > Hi gents, > > > > > > I was giving a try to the UEFI-GOP on a FreeBSD 11.0-RC3. Launching the > > > install of, let's say a Debian works fine and I can attach a VNC viewer > > > for the progress. > > > > > > All is fine , even rebooting after the installation is finished I can > > > log in Debian. > > > > > > However, when I do a bhyvectl --destroy --vm=xxxxxxx and I try to reboot > > > the VM and it greets me with the error message "Boot failed, EFI > > > Harddrive" at boot and sends me to the EFI shell. > > > > > > I then have to manually use the shell menu to launch the boot via the > > > ad-hoc file (/boot/efi/efi/debian/grubx64.efi) and it boot flawlessly. > > > > > > And of course, the same error happens after I reboot the FreeBSD host > > > machine > > > > > > Is there somethign I am missing here ? > > > > > > Thanks for this admirable piece of work ! > > > > > > -Stephan > > > > Stephan, > > > > I have also experienced this as well. My scriptable work around was to > > start the guest with a rEFInd ISO[1] instead a 'null.iso'. rEFInd sees > > the Debian installation on the image/volume and will boot from it after > > the 15 seconds timeout elapses. > > > > As for the why... my rudimentary understanding is the Debian installation > > creates and relies on the UEFI boot entry it creates during installation. > > However that entry is forgotten once the guest's VMM resources are > > reclaimed as the UEFI environment is not saved and is reloaded exactly > > from the UEFI ROM file (not from the previous state). > > > > -Justin D Holcomb > > > > [1] http://www.rodsbooks.com/refind/getting.html > > That's also true for Ubuntu 16.04 But this problem does not happen with Fedora 4.7