LUA loader: bhyve now doesn't?

[Larry Rosenman]

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. 

[snip]

-- 
Larry Rosenman                         https://people.FreeBSD.org/~ler/
Phone: +1 214-642-9640                 E-Mail: ler at FreeBSD.org
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 679 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20180819/fbc0ebb0/attachment.sig>