From owner-freebsd-current@freebsd.org Sun Aug 19 16:05:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA703106E10F for ; Sun, 19 Aug 2018 16:05:04 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9FCDA7D1E2; Sun, 19 Aug 2018 16:05:04 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from ler-imac.local (unknown [IPv6:2600:1700:210:b18f:1840:43d6:4770:35e0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 3FD951A140; Sun, 19 Aug 2018 16:05:04 +0000 (UTC) (envelope-from ler@FreeBSD.org) Date: Sun, 19 Aug 2018 11:05:03 -0500 From: Larry Rosenman To: Joe Maloney Cc: Warner Losh , freebsd-current Subject: Re: LUA loader: bhyve now doesn't? Message-ID: <20180819160503.nlns5pz6rnt7afzo@ler-imac.local> Mail-Followup-To: Joe Maloney , Warner Losh , freebsd-current References: <20180819152253.bbcrefdvynl7y5ka@ler-imac.local> <20180819153526.7ruovrpmdsimkmfj@ler-imac.local> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="txw55ze4olmz6eii" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2018 16:05:05 -0000 --txw55ze4olmz6eii Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > https://www.freebsd.org/cgi/man.cgi?query=3Dbhyveload&sektion=3D8 >=20 > 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. >=20 > https://github.com/churchers/vm-bhyve/blob/d4532f6da3e155a4430acbb9138e59= c0d5abfc39/sample-templates/config.sample >=20 > 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).=20 This default change is a POLA violation for bhyve/vm-bhyve users.=20 [snip] --=20 Larry Rosenman https://people.FreeBSD.org/~ler/ Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 --txw55ze4olmz6eii Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQHBBAABCgCrFiEEHjgknedhWzvJgwVzaXyZsatIp30FAlt5lS8tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3JnbGVyQEZyZWVCU0Qub3JnXxSAAAAAAC4AKGlz c3Vlci1mcHJAbm90YXRpb25zLm9wZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxRTM4 MjQ5REU3NjE1QjNCQzk4MzA1NzM2OTdDOTlCMUFCNDhBNzdEAAoJEGl8mbGrSKd9 iuMH/R3VRKZcy4D5+Nr2zfgULwcKMhr/2HDnaLZo+ooKiy3HUgTma4fsxSU9jKrk H++GJxYuS1RX/Kak64SYfjaAOMKjcJTjjD2H//sTlke5A9rtbz8385Nag2ib/Lfs qAUKV6dJMreQlzPL8JQ/wCnRyBLOFFK3ttbYraPYqApwA0GBmMKmW70qH/8Psq8a zTzDT6tm2XwW01yvNONw6QddOqZzFhAQG9YmjmAKD++nQmAxOIKv37ouy+uR6TNn aDNHlfNIbp1/VZeBIXVageg36ifGek5o9ZOFaViQj3zodS4TclxSAHUxd2oSYud4 9U8Po5qPegLa+pRFenDt7HPk5s8= =6eqV -----END PGP SIGNATURE----- --txw55ze4olmz6eii--