Date: Mon, 26 Sep 2016 14:31:57 +0200 From: Lars Engels <lars.engels@0x20.net> To: Justin Holcomb <me@justinholcomb.me> Cc: Stephan CHEDLIVILI <stephan@theched.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: UEFI bhyve and EFI shell at boot Message-ID: <20160926123157.GO97879@e-new.0x20.net> In-Reply-To: <CY4PR12MB14478911B5A62D9C8FB8F86FA3CD0@CY4PR12MB1447.namprd12.prod.outlook.com> References: <9276239.oRRSstIAVb@panda.test.me> <CY4PR12MB14478911B5A62D9C8FB8F86FA3CD0@CY4PR12MB1447.namprd12.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--U2AV99o4bq1UPJQr Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 26, 2016 at 05:56:59AM +0000, Justin Holcomb wrote: > > From: owner-freebsd-virtualization@freebsd.org <owner-freebsd-virtualiz= ation@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 > > =C2=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= for the=20 > > progress. > >=20 > > All is fine , even rebooting after the installation is finished I can l= og in=20 > > Debian. > >=20 > > However, when I do a bhyvectl --destroy --vm=3Dxxxxxxx and I try to reb= oot the=20 > > VM and it greets me with the error message "Boot failed, EFI Harddrive"= at=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 a= d-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 m= achine > >=20 > > Is there somethign I am missing here ?=20 > >=20 > > Thanks for this admirable piece of work ! > >=20 > > -Stephan >=20 > Stephan, >=20 > I have also experienced this as well. My scriptable work around was to st= art 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 secon= ds > timeout elapses. >=20 > 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 reclai= med as > the UEFI environment is not saved and is reloaded exactly from the UEFI R= OM > file (not from the previous state). >=20 > -Justin D Holcomb >=20 > [1] http://www.rodsbooks.com/refind/getting.html That's also true for Ubuntu 16.04 --U2AV99o4bq1UPJQr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQF8BAEBCgBmBQJX6RU9XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1tbFAIALtBeRgnChoauzNNvutoypNy bP/W+KivvRxs37Y5dqdNb78bhaUnrVuJiXNUd/WQTzct0/w32Ym7RgNgXSn2lx4g 2D466ioKHZPs3qddmeAAkkRWWLnQrvHZIIqQ2t7y+mB2PzLysMWmJU6R8UnydFCJ 5vWFd4sB1hqVl/nV1fWkq0wTNFVQxZVwhG9L5S0xXPJcpRELj86HzoMtLIbrrQoL okxb28mYiKGF5XTUebEvyt0SXhXcmhTtmDupWScAmDR84YVTOF4tTKQI3U9mre5S vBvxVEOjDlPSBSa/uMqsqxSQbF52z1oiRuv9eYe2Kra2aZup+woQRg5uWIw4s0o= =siil -----END PGP SIGNATURE----- --U2AV99o4bq1UPJQr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160926123157.GO97879>