From nobody Sun Sep 8 00:23:02 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4X1W0941Yqz5V93v for ; Sun, 08 Sep 2024 00:23:21 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X1W084Vtdz4SMC for ; Sun, 8 Sep 2024 00:23:20 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-21-232.area1b.commufa.jp [123.1.21.232]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 4880N2sf052846; Sun, 8 Sep 2024 09:23:03 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1725754984; bh=QZBaQzHh6JVpFRs79zKhSu0DWKyM1h7BgConh4tKByg=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=ShX4TnP967VuEae+qa+1wvV4NzCo8a4Rte3UMWHvkADyFKJjydPWJbjAvV9d8++00 YvVMh7ig3kslCZPcVy/e1716npsdXArEnxmgt+SSZ4Y5ba1hj3zML2xMqaScDe6bCJ ELr+RwY3gc6LzDFalkIto9gf4Xoo3R0dw/PJ44QI= Date: Sun, 8 Sep 2024 09:23:02 +0900 From: Tomoaki AOKI To: Warner Losh Cc: freebsd-current@freebsd.org, void Subject: Re: Loader needs to be updated message Message-Id: <20240908092302.caa9f655693f71e03ee6b030@dec.sakura.ne.jp> In-Reply-To: References: <9494862A-E445-43AC-8887-FACC84A74435.ref@yahoo.com> <9494862A-E445-43AC-8887-FACC84A74435@yahoo.com> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.1) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Queue-Id: 4X1W084Vtdz4SMC On Sat, 7 Sep 2024 17:07:23 -0600 Warner Losh wrote: > On Sat, Sep 7, 2024 at 12:24 PM void wrote: > > > On Sat, Sep 07, 2024 at 11:47:12AM -0600, Warner Losh wrote: > > >Wait. On the guest? > > > > > >Then what's the VM system you're using? > > > > > >Warner > > > > Bhyve. > > > > The server is freebsd-current. The guest is 13.2-stable. > > I see the error in the ascii beastie menu when booting the guest > > with vmrun.sh > > > > Hmmm, So somehow we're using the guest's boot loader and > the host's /boot/lua files then, I think. Uggg. > > Warner Can it be in reverse? I've not read (even if it's already provided somewhere or attached) the vmrun.sh script, but isn't there any possibility that it somehow uses loader on bare-metal (regardless on /boot/ or on ESP) to kick the guests? If so, version mismatch happenes, but newer kicks older. But yes, usually it is not at all the problem, as newer loader codes in same interpreter (lua/4th) is keeping backward compatibilities, I guess. Another case is that void already stated that >>In such a case, you might need something like: >> >># cp -a /boot/loader.efi /boot/efi/efi/BOOT/bootx64.efi > >and the error is gone!!! TYVM in another mail in this thread [1]. This could mean that efi/freebsd/loader.efi in ESP is not called by the UEFI firmware and efi/BOOT/efi/bootx64.efi is used instead. [1] https://lists.freebsd.org/archives/freebsd-current/2024-September/006372.html -- Tomoaki AOKI