Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 8 Sep 2024 09:23:02 +0900
From:      Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
To:        Warner Losh <imp@bsdimp.com>
Cc:        freebsd-current@freebsd.org, void <void@f-m.fm>
Subject:   Re: Loader needs to be updated message
Message-ID:  <20240908092302.caa9f655693f71e03ee6b030@dec.sakura.ne.jp>
In-Reply-To: <CANCZdfocFaqYLKU0zdPuHQaAK_CACad7A8CK0bm3B5=d2RVXMQ@mail.gmail.com>
References:  <9494862A-E445-43AC-8887-FACC84A74435.ref@yahoo.com> <9494862A-E445-43AC-8887-FACC84A74435@yahoo.com> <ZtyM5OkDRntXe1Ru@int21h> <CANCZdfoFCZJzQJJDqk8WWSUc7LKj=JjiCUsD=t=BRnYQwCEYXg@mail.gmail.com> <ZtyaOO2a3L84tAuT@int21h> <CANCZdfocFaqYLKU0zdPuHQaAK_CACad7A8CK0bm3B5=d2RVXMQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 7 Sep 2024 17:07:23 -0600
Warner Losh <imp@bsdimp.com> wrote:

> On Sat, Sep 7, 2024 at 12:24 PM void <void@f-m.fm> 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    <junchoon@dec.sakura.ne.jp>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240908092302.caa9f655693f71e03ee6b030>