Date: Fri, 4 May 2018 06:41:26 -0700 From: Peter Grehan <grehan@freebsd.org> To: Mike Gerdts <mike.gerdts@joyent.com>, Michael Reifenberger <mike@reifenberger.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: Centos7 uefi boot problem with bhyve after update Message-ID: <96b7bc92-a766-b9b7-ba65-2c24e3b99177@freebsd.org> In-Reply-To: <CAAxFYUEmnVYEzbr8gkpMZ%2BwQyB85=sOREkOUkVh3oY7tk4hv9w@mail.gmail.com> References: <20180502095855.Horde.pnF1J3CvBGrJMXFBiwHibZM@app.eeeit.de> <CACLnyC%2BZKqMY4Kxu%2B6Rmo22ORUge%2Bk1H0eHn2YKgpKm9AVA01A@mail.gmail.com> <20180504122635.Horde.BLpo7EULCvCbMZLSMErcHAh@app.eeeit.de> <CAAxFYUEmnVYEzbr8gkpMZ%2BwQyB85=sOREkOUkVh3oY7tk4hv9w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mike, > the fault here could be that of bootrom not reading the files it should That is exactly the issue. The current UEFI code does not save non-volatile variables to persistent storage. Guest o/s's are increasingly writing their efi loaders to non-standard locations and using nv vars to direct UEFI to boot from these locations. I'm (very slowly) merging a fix from Leon for this in both UEFI and bhyve which directs nv var writes to a file on the host, providing a persistent store. later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96b7bc92-a766-b9b7-ba65-2c24e3b99177>