From nobody Sun Sep 08 01:54:28 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 4X1Y1Z126yz5VQ1X for ; Sun, 08 Sep 2024 01:54:42 +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 4X1Y1Y3RcHz4fD2 for ; Sun, 8 Sep 2024 01:54:40 +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 4881sSIP067222; Sun, 8 Sep 2024 10:54:28 +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=1725760469; bh=vrDlbnHNnbX6OuvpKOZON+6ANoQfdkwC3zU7st48TF4=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=LarC8iSrBVN33+Tqi+S+n/YFmf5qnVN0+rVbYK3sxGIAvLSspveEmjkaJuS4n1UgX rcuDCaqtW+6kNOCQuOfangvGbvqtf4ab6ZWr8LN+lJ89GJuP7nLWx5Sr6OIZWyeaYu 3fMqhvVftlkq1nJuusBva/L3ioAjMUymI8uegD04= Date: Sun, 8 Sep 2024 10:54:28 +0900 From: Tomoaki AOKI To: void Cc: freebsd-current@freebsd.org, Warner Losh Subject: Re: Loader needs to be updated message Message-Id: <20240908105428.5913d8310f2fc39b08da6ee8@dec.sakura.ne.jp> In-Reply-To: References: <9494862A-E445-43AC-8887-FACC84A74435.ref@yahoo.com> <9494862A-E445-43AC-8887-FACC84A74435@yahoo.com> <20240908092302.caa9f655693f71e03ee6b030@dec.sakura.ne.jp> 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=US-ASCII Content-Transfer-Encoding: 7bit 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: 4X1Y1Y3RcHz4fD2 On Sun, 8 Sep 2024 02:01:02 +0100 void wrote: > On Sun, Sep 08, 2024 at 09:23:02AM +0900, Tomoaki AOKI wrote: > > >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]. > > I should have made it clearer, in that other case, i did > # cp -a /boot/loader.efi /boot/efi/efi/BOOT/bootaa64.efi > as it was an arm64 context > > >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. > > In *this* amd64 case, neither the -current server running bhyve > nor the 13.4-stable guest have bootx64.efi present. > > /boot/efi is empty on both the server and the guest. If not automounted, you can mount ESP manually as msdosfs there, at least for bare-metal host. IIUC, recent installation by bsdinstall creates fstab entry for it by default. -- Tomoaki AOKI