From owner-freebsd-current@freebsd.org Sun Aug 19 17:04:37 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 EE0C8107053A for ; Sun, 19 Aug 2018 17:04:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 79A5C80240 for ; Sun, 19 Aug 2018 17:04:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x230.google.com with SMTP id v14-v6so1672447iob.4 for ; Sun, 19 Aug 2018 10:04:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=1UqnvYw7nzCtgPi8eZ/SSDNxNdNUx6cgOBRyr96XjfI=; b=RbSrUK4oHiwt2Eid7RJF3RMuh9utRN5qeh4jagVS00UVJTcwJlg0HGs+0KdaCeYhUz EvufuGb2SgzfLVTewNMoObK5Z3eSBtBk3hzBHK7z4E1nqo8Zn4iGtLeT46akefU1mAJN eEKU35lMbjK/6eu//gNgN60qVOV3MCJByb3qA9VK3Pq76n8W5LRPMY7+A0Ebhiru9L0f enR1WfcslMuvCZYTIwRNKN/IoLE6TH/TKjdcb3LLQMOi03WaJR9GXZ/r1DhQJnTpaE8e SuGlDPwnpX0mLx8rvTVZqaoFi2W0s7Wta6SbMVHJlKpnNjSLGBKD+Zh3J47dmM8qST3o FzDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=1UqnvYw7nzCtgPi8eZ/SSDNxNdNUx6cgOBRyr96XjfI=; b=WquKWHL3D6bp1HFj+boWGAZKYlJFL8f4IdxJxDeVe0IxCYotEwD2CVWL08p3dzlmpx hl1g0I/E6hxwoVJNmBKokIkJOdbKjYhEFy6J2GAkSMBBFoK/y8IJMzadd87E2/lL041h o/NWSCQMMmUeAzFtl8D5rKFsf9F9MHMQ356oILVJfyhgNzLBQMbKqI7dijAeoE++nPy7 W34WdOJTwWuwT8cS/4sgr+K+DPx8/KMGCnyfWcTUdRf5fp/SQLuBLgC2CgFwdNCwTxBD 57SCTeXGhf5PBmAqqBjMcM9JDzCcTOs8IaGToA3w92zTFq+UQX8RbR8S81+JbsskW/8d KrHw== X-Gm-Message-State: AOUpUlHY9Dh93Edtmw2aqWkYQuOOE4Hd9V7DtnYcS0VRMPr6uRB3Y15S wnCoy5/rBi7HKT6CJIHKbJHGu/7kIT+r9ACfE5Fhyg== X-Google-Smtp-Source: AA+uWPwGAtCbeQ7JuV3Pbmr7dpcJGleUn1cvPoXayW1vkqsyj7d/kTawvKATgVExA7SOBXr0H8qoPxVf9FNgQquDIU8= X-Received: by 2002:a6b:d004:: with SMTP id x4-v6mr35123370ioa.299.1534698275724; Sun, 19 Aug 2018 10:04:35 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:2806:0:0:0:0:0 with HTTP; Sun, 19 Aug 2018 10:04:35 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <167d1cb1-7232-52bb-9a73-6f109c437a63@FreeBSD.org> References: <20180819152253.bbcrefdvynl7y5ka@ler-imac.local> <20180819153526.7ruovrpmdsimkmfj@ler-imac.local> <167d1cb1-7232-52bb-9a73-6f109c437a63@FreeBSD.org> From: Warner Losh Date: Sun, 19 Aug 2018 11:04:35 -0600 X-Google-Sender-Auth: w-lO1tmkDjc5p2-mm5YPnHzZeSc Message-ID: Subject: Re: LUA loader: bhyve now doesn't? To: John Baldwin Cc: Kyle Evans , FreeBSD Current , Tycho Nightingale Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 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 17:04:37 -0000 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 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 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? > >>> > >> > >> Unlikely, but a couple of questions. Have you always used the LUA > loader, > >> or is this a change with the recent default switch? > >> > >> And to be clear, you expect the host's file to be used for this, not > the VM > >> 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 current model doesn't tolerate any mismatch between > > host and guest and looks unsustainable. > > Err, normally guests read things out of the a guest disk image (think most > VMs like VirtualBox, etc.). userboot.so is looking in the guest's disk > image. > Now, userboot isn't memory limited like the BIOS boot, so if it's > possible to have userboot just include both lua and forth perhaps with > some auto-detection based on what is in /boot/loader.rc to determine > which interpreter to use, that is really the best path forward. > You can't have both interpreters in the same image. You can't easily determine what the language to use for the interpreter. You can only determine if lua is present or not. Warner