Date: Mon, 26 Sep 2016 05:56:59 +0000 From: Justin Holcomb <me@justinholcomb.me> To: Stephan CHEDLIVILI <stephan@theched.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: UEFI bhyve and EFI shell at boot Message-ID: <CY4PR12MB14478911B5A62D9C8FB8F86FA3CD0@CY4PR12MB1447.namprd12.prod.outlook.com> In-Reply-To: <9276239.oRRSstIAVb@panda.test.me> References: <9276239.oRRSstIAVb@panda.test.me>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: owner-freebsd-virtualization@freebsd.org <owner-freebsd-virtualizat= ion@freebsd.org> on behalf of Stephan CHEDLIVILI <stephan@theched.org> > Sent: Saturday, September 24, 2016 12:50 AM > To: freebsd-virtualization@freebsd.org > Subject: UEFI bhyve and EFI shell at boot > =A0 =20 > Hi gents, >=20 > I was giving a try to the UEFI-GOP on a FreeBSD 11.0-RC3. Launching the=20 > install of, let's say a Debian works fine and I can attach a VNC viewer f= or the=20 > progress. >=20 > All is fine , even rebooting after the installation is finished I can log= in=20 > Debian. >=20 > However, when I do a bhyvectl --destroy --vm=3Dxxxxxxx and I try to reboo= t the=20 > VM and it greets me with the error message "Boot failed, EFI Harddrive" a= t=20 > boot and sends me to the EFI shell.=20 >=20 > I then have to manually use the shell menu to launch the boot via the ad-= hoc=20 > file (/boot/efi/efi/debian/grubx64.efi) and it boot flawlessly. >=20 > And of course, the same error happens after I reboot the FreeBSD host mac= hine >=20 > Is there somethign I am missing here ?=20 >=20 > Thanks for this admirable piece of work ! >=20 > -Stephan Stephan, I have also experienced this as well. My scriptable work around was to star= t 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 reclaime= d 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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CY4PR12MB14478911B5A62D9C8FB8F86FA3CD0>