Date: Sun, 19 Aug 2018 11:54:51 -0400 From: Joe Maloney <jmaloney@ixsystems.com> To: Warner Losh <imp@bsdimp.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: LUA loader: bhyve now doesn't? Message-ID: <CAFvkmYPhREMQA41NkazFJWrvfZPqf35HZ6aDUD6ht8i_L7X--A@mail.gmail.com> In-Reply-To: <20180819153526.7ruovrpmdsimkmfj@ler-imac.local> References: <20180819152253.bbcrefdvynl7y5ka@ler-imac.local> <CANCZdfqHV7Fy%2BbJAuMv5gfJmPJqh1QmKqjGz-bVH2wh6NyqeVQ@mail.gmail.com> <20180819153526.7ruovrpmdsimkmfj@ler-imac.local>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Joe Maloney QA Manager / iXsystems Enterprise Storage & Servers Driven By Open Source On Sun, Aug 19, 2018 at 11:38 AM Larry Rosenman <ler@freebsd.org> 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 <ler@freebsd.org> 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 root@borg.lerctr.org) > > > Startup error in /boot/lua/loader.lua: > > > LUA ERROR: cannot open /boot/lua/loader.lua: no such file or directory. > > > > > > /boot/kernel/kernel text=0x1063d88 data=0x12e930+0x283970 > > > syms=[0x8+0x14cf28+0x8+0x163e57] > > > Hit [Enter] to boot immediately, or any other key for command prompt. > > > Booting [/boot/kernel/kernel]... > > > > > > These VM's have been running for MONTHS. > > > > > > Ideas? > > > > > > > There's no boot/lua/loader.lua. > > > > You can either fix that, or you can recompile with > > LOADER_DEFAULT_INTERP=4th for the moment. > actually on the host there is: > borg.lerctr.org /home/ler $ ls -l /boot/lua/ > total 131 > -r--r--r-- 1 root wheel 3895 Aug 19 09:46 cli.lua > -r--r--r-- 1 root wheel 3204 Aug 19 09:46 color.lua > -r--r--r-- 1 root wheel 14024 Aug 19 09:46 config.lua > -r--r--r-- 1 root wheel 10302 Aug 19 09:46 core.lua > -r--r--r-- 1 root wheel 9986 Aug 19 09:46 drawer.lua > -r--r--r-- 1 root wheel 3324 Aug 19 09:46 hook.lua > -r--r--r-- 1 root wheel 2543 Aug 19 09:46 loader.lua > -r--r--r-- 1 root wheel 2431 Aug 19 09:46 logo-beastie.lua > -r--r--r-- 1 root wheel 2203 Aug 19 09:46 logo-beastiebw.lua > -r--r--r-- 1 root wheel 1958 Aug 19 09:46 logo-fbsdbw.lua > -r--r--r-- 1 root wheel 2399 Aug 19 09:46 logo-orb.lua > -r--r--r-- 1 root wheel 2119 Aug 19 09:46 logo-orbbw.lua > -r--r--r-- 1 root wheel 12010 Aug 19 09:46 menu.lua > -r--r--r-- 1 root wheel 3941 Aug 19 09:46 password.lua > -r--r--r-- 1 root wheel 2381 Aug 19 09:46 screen.lua > borg.lerctr.org /home/ler $ > > This is when booting the vm, and it's not on the vm's disk. > > So the bhyveload behavior *CHANGED*. > > POLA? > > > > > > Warner > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > -- > 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFvkmYPhREMQA41NkazFJWrvfZPqf35HZ6aDUD6ht8i_L7X--A>