Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 11:10 AM, Warner Losh wrote: > > I think including both loaders in userboot is probably a no-start >> based on the current interface. >> > > Yea, it would be a challenge... Sadly, we have POLA violations either way > we jump here. > Just to summarize the IRC conversation:

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 11:03 AM, Kyle Evans wrote: > On Sun, Aug 19, 2018 at 11:58 AM, John Baldwin wrote: > > On 8/19/18 5:28 PM, Kyle Evans wrote: > >> On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: > >>> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman > wrote: > >>> > On Sun, Au

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 11:04 AM, Larry Rosenman wrote: > so it still looks forth'ish, but it's using lua. > It will always look forthish becuase it's unused in loader_lua. Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 10:58 AM, John Baldwin wrote: > On 8/19/18 5:28 PM, Kyle Evans wrote: > > On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: > >> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman > wrote: > >> > >>> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: > On

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 05:58:43PM +0100, John Baldwin wrote: > On 8/19/18 5:28 PM, Kyle Evans wrote: > > On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: > >> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: > >> > >>> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: >

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 11:58 AM, John Baldwin wrote: > On 8/19/18 5:28 PM, Kyle Evans wrote: >> On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: >>> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: >>> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: > On Sun, Aug

Re: LUA loader: bhyve now doesn't?

On 8/19/18 5:28 PM, Kyle Evans wrote: > On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: >> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: >> >>> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: > With t

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 11:35 AM, Larry Rosenman wrote: > On Sun, Aug 19, 2018 at 11:28:10AM -0500, Kyle Evans wrote: >> > filesystem? >> > >> >> (CC'ing jhb@ and tychon@, who might have better insight) >> >> If we can swing it, I think the best model here should have always >> been that userboot

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 11:28:10AM -0500, Kyle Evans wrote: > > filesystem? > > > > (CC'ing jhb@ and tychon@, who might have better insight) > > If we can swing it, I think the best model here should have always > been that userboot uses the host's scripts but the guest's > loader.conf. The curre

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: > On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: > >> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: >> > On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: >> > >> > > With today's change to LUA as the loader, I seem

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 10:05 AM, Larry Rosenman 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

Re: LUA loader: bhyve now doesn't?

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

Re: LUA loader: bhyve now doesn't?

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&sektio

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 09:42:05AM -0600, Warner Losh wrote: > On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: > > > On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: > > > On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: > > > > > > > With today's change to LUA as the lo

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: > On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: > > On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: > > > > > With today's change to LUA as the loader, I seem to have an issue with > > > bhyhve: > > > > > > Consoles: us

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: > On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: > > > With today's change to LUA as the loader, I seem to have an issue with > > bhyhve: > > > > Consoles: userboot > > > > FreeBSD/amd64 User boot, Revision 1.1 > > (Thu Nov 16 1

Re: LUA loader: bhyve now doesn't?

On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: > With today's change to LUA as the loader, I seem to have an issue with > bhyhve: > > Consoles: userboot > > FreeBSD/amd64 User boot, Revision 1.1 > (Thu Nov 16 15:04:02 CST 2017 r...@borg.lerctr.org) > Startup error in /boot/lua/loader.lua:

LUA loader: bhyve now doesn't?

With today's change to LUA as the loader, I seem to have an issue with bhyhve: Consoles: userboot FreeBSD/amd64 User boot, Revision 1.1 (Thu Nov 16 15:04:02 CST 2017 r...@borg.lerctr.org) Startup error in /boot/lua/loader.lua: LUA ERROR: cannot open /boot/lua/loader.lua: no such file or directory