Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 10:05 AM, Larry Rosenman <ler_at_freebsd.org> wrote:

> On Sun, Aug 19, 2018 at 11:54:51AM -0400, Joe Maloney wrote:
> > I ran into this as well months ago.  To workaround it I extracted
> > userboot.so for the VM's, and launched bhyve with the alternate
> > userboot.so.  You can use a flag as described in the manpage to start
> > userboot.so from an alternate location.
> >
> > https://www.freebsd.org/cgi/man.cgi?query=bhyveload&sektion=8
> >
> > Also support was recently added for vm-bhyve to specify alternate
> > userboot.so location for one that is compatible with 4th.  You just need
> to
> > extract that somewhere onto the host, and specify it to load when
> starting
> > the VM.
> >
> > https://github.com/churchers/vm-bhyve/blob/
> d4532f6da3e155a4430acbb9138e59c0d5abfc39/sample-templates/config.sample
> >
> > Alternatively you could just use UEFI, or UEFI-CSM firmware.
> Ok, so pulling /boot/userboot.so from my non-upgraded 12 system and
> putting it in /boot/userboot-4th.so on the host allows the VM's to boot
> after changing the config files to point bhyveload_loader to it (yes,
> I'm using vm-bhyve).
>
> This default change is a POLA violation for bhyve/vm-bhyve users.


OK. We're on it. Thanks for the heads up. We were unaware of the issue when
we flipped the switch.

Warner