Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 3 Jan 2025 10:21:16 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        "Edward Sanford Sutton, III" <mirror176@hotmail.com>
Cc:        FreeBSD Stable ML <stable@freebsd.org>
Subject:   Re: "Loader needs to be updated" (azure guest context)
Message-ID:  <CANCZdfpw=ONQvqw_nF=YNWyXnOk_Wq8mgfrzwF%2BA_LO=YOm_dw@mail.gmail.com>
In-Reply-To: <PH0PR11MB4776DEDE7955D809D0F02F9FE6152@PH0PR11MB4776.namprd11.prod.outlook.com>
References:  <Z3LAJ7WN41vO0sl_@int21h> <CANCZdfrhd4uXdSosaE434g_eveXxd82t8oAEHrNEWQ_icY38fQ@mail.gmail.com> <PH0PR11MB4776DEDE7955D809D0F02F9FE6152@PH0PR11MB4776.namprd11.prod.outlook.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000486e26062ad08289
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 3, 2025, 10:15=E2=80=AFAM Edward Sanford Sutton, III <
mirror176@hotmail.com> wrote:

> On 12/30/24 10:59, Warner Losh wrote:
> > On Mon, Dec 30, 2024, 8:45=E2=80=AFAM void <void@f-m.fm> wrote:
> >
> >> Hi,
> >>
> >> context is
> >>
> >> freebsd amd64 vm on Azure (initially installed via azure marketplace
> >> several
> >> years ago (12-releng)), and has been upgraded as updates became
> available
> >> with freebsd-update over the years all the way up to 13.4-p1 now.
> >> System updates/upgrades have *always* been managed with freebsd-update=
.
> >>
> >> Latest upgrade from 13.3-p6 to 13.4-p1 shows "loader needs to be
> updated"
> >> in the beastie menu in the console now. This is new.
> >>
> >> # zfs --version
> >> zfs-2.1.14-FreeBSD_gd99134be8
> >> zfs-kmod-2.1.15-FreeBSD_gd99134be8
> >>
> >> (perhaps side issue - different version numbers, same
> -FreeBSD_gd99134be8
> >> ?!!)
> >>
> >> This system is *not* root-on-zfs. There is zfs, but it's data on
> >> a non-boot virtual disk.
> >>
> >> "zpool status" invites me to upgrade the pool. I've not done this (hav=
e
> >> never done it with this vm, either), and don't want to unless I'm
> >> absolutely certain upgrading the pool won't break everything.
> >>
> >> I note from a (similar, but different context) thread last September
> >>
> >>
> https://lists.freebsd.org/archives/freebsd-current/2024-September/006378.=
html
> >> that FreeBSD uses "the guest's boot loader and the host's /boot/lua
> files"
> >> but I'm clueless how this would apply in an amd64 context with Azure
> >> as the host.
> >>
> >> What do i have to do? Also, is the warning safe to ignore in this
> context?
> >>
> >
> > In this context, it's a known false positive. It's too risky to fix in =
a
> pX
> > for 13.4, so will be in 13.5 since the fix is already in stable/13. It'=
s
> > just cosmetic, there's no bug it exposes. And even if you hadn't actual=
ly
> > updated the loader, it will fail safe for loaders installed from FreeBS=
D
> 11
> > and newer (though not relevant to your use case). It should be in the
> > release notes for 13.4 as a known issue, but the process for post relea=
se
> > revision is murky at best.
>
> Why is there no errata entry for it?
>


I don't know how to create that. If someone reminds me I'll add it.

Warner

> > The host vs guest issue you highlighted is a different thing and applie=
s
> > only to bhyve.
> >
> > Warner
> >
> >>
> >
>
>
>

--000000000000486e26062ad08289
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote gmail_quote_contai=
ner"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 3, 2025, 10:15=E2=80=
=AFAM Edward Sanford Sutton, III &lt;<a href=3D"mailto:mirror176@hotmail.co=
m">mirror176@hotmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">On 12/30/24 10:59, Warner Losh wrote:<br>
&gt; On Mon, Dec 30, 2024, 8:45=E2=80=AFAM void &lt;<a href=3D"mailto:void@=
f-m.fm" target=3D"_blank" rel=3D"noreferrer">void@f-m.fm</a>&gt; wrote:<br>
&gt; <br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; context is<br>
&gt;&gt;<br>
&gt;&gt; freebsd amd64 vm on Azure (initially installed via azure marketpla=
ce<br>
&gt;&gt; several<br>
&gt;&gt; years ago (12-releng)), and has been upgraded as updates became av=
ailable<br>
&gt;&gt; with freebsd-update over the years all the way up to 13.4-p1 now.<=
br>
&gt;&gt; System updates/upgrades have *always* been managed with freebsd-up=
date.<br>
&gt;&gt;<br>
&gt;&gt; Latest upgrade from 13.3-p6 to 13.4-p1 shows &quot;loader needs to=
 be updated&quot;<br>
&gt;&gt; in the beastie menu in the console now. This is new.<br>
&gt;&gt;<br>
&gt;&gt; # zfs --version<br>
&gt;&gt; zfs-2.1.14-FreeBSD_gd99134be8<br>
&gt;&gt; zfs-kmod-2.1.15-FreeBSD_gd99134be8<br>
&gt;&gt;<br>
&gt;&gt; (perhaps side issue - different version numbers, same -FreeBSD_gd9=
9134be8<br>
&gt;&gt; ?!!)<br>
&gt;&gt;<br>
&gt;&gt; This system is *not* root-on-zfs. There is zfs, but it&#39;s data =
on<br>
&gt;&gt; a non-boot virtual disk.<br>
&gt;&gt;<br>
&gt;&gt; &quot;zpool status&quot; invites me to upgrade the pool. I&#39;ve =
not done this (have<br>
&gt;&gt; never done it with this vm, either), and don&#39;t want to unless =
I&#39;m<br>
&gt;&gt; absolutely certain upgrading the pool won&#39;t break everything.<=
br>
&gt;&gt;<br>
&gt;&gt; I note from a (similar, but different context) thread last Septemb=
er<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://lists.freebsd.org/archives/freebsd-current/2024=
-September/006378.html" rel=3D"noreferrer noreferrer" target=3D"_blank">htt=
ps://lists.freebsd.org/archives/freebsd-current/2024-September/006378.html<=
/a><br>
&gt;&gt; that FreeBSD uses &quot;the guest&#39;s boot loader and the host&#=
39;s /boot/lua files&quot;<br>
&gt;&gt; but I&#39;m clueless how this would apply in an amd64 context with=
 Azure<br>
&gt;&gt; as the host.<br>
&gt;&gt;<br>
&gt;&gt; What do i have to do? Also, is the warning safe to ignore in this =
context?<br>
&gt;&gt;<br>
&gt; <br>
&gt; In this context, it&#39;s a known false positive. It&#39;s too risky t=
o fix in a pX<br>
&gt; for 13.4, so will be in 13.5 since the fix is already in stable/13. It=
&#39;s<br>
&gt; just cosmetic, there&#39;s no bug it exposes. And even if you hadn&#39=
;t actually<br>
&gt; updated the loader, it will fail safe for loaders installed from FreeB=
SD 11<br>
&gt; and newer (though not relevant to your use case). It should be in the<=
br>
&gt; release notes for 13.4 as a known issue, but the process for post rele=
ase<br>
&gt; revision is murky at best.<br>
<br>
Why is there no errata entry for it?<br></blockquote></div></div><div dir=
=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto">I don&#39=
;t know how to create that. If someone reminds me I&#39;ll add it.</div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">Warner=C2=A0</div><div dir=3D"au=
to"><div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
&gt; The host vs guest issue you highlighted is a different thing and appli=
es<br>
&gt; only to bhyve.<br>
&gt; <br>
&gt; Warner<br>
&gt; <br>
&gt;&gt;<br>
&gt; <br>
<br>
<br>
</blockquote></div></div></div>

--000000000000486e26062ad08289--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpw=ONQvqw_nF=YNWyXnOk_Wq8mgfrzwF%2BA_LO=YOm_dw>