Date: Mon, 30 Dec 2024 10:59:47 -0700 From: Warner Losh <imp@bsdimp.com> To: FreeBSD FS <freebsd-fs@freebsd.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: "Loader needs to be updated" (azure guest context) Message-ID: <CANCZdfrhd4uXdSosaE434g_eveXxd82t8oAEHrNEWQ_icY38fQ@mail.gmail.com> In-Reply-To: <Z3LAJ7WN41vO0sl_@int21h> References: <Z3LAJ7WN41vO0sl_@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000b62454062a809441 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 (have > 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 actually updated the loader, it will fail safe for loaders installed from FreeBSD 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 release revision is murky at best. The host vs guest issue you highlighted is a different thing and applies only to bhyve. Warner > --000000000000b62454062a809441 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 Mon, Dec 30, 2024, 8:45=E2=80= =AFAM void <<a href=3D"mailto:void@f-m.fm">void@f-m.fm</a>> wrote:<br= ></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-= left:1px #ccc solid;padding-left:1ex">Hi,<br> <br> context is<br> <br> freebsd amd64 vm on Azure (initially installed via azure marketplace severa= l <br> years ago (12-releng)), and has been upgraded as updates became available <= br> with freebsd-update over the years all the way up to 13.4-p1 now.<br> System updates/upgrades have *always* been managed with freebsd-update.<br> <br> Latest upgrade from 13.3-p6 to 13.4-p1 shows "loader needs to be updat= ed" <br> in the beastie menu in the console now. This is new.<br> <br> # zfs --version<br> zfs-2.1.14-FreeBSD_gd99134be8<br> zfs-kmod-2.1.15-FreeBSD_gd99134be8<br> <br> (perhaps side issue - different version numbers, same -FreeBSD_gd99134be8 ?= !!)<br> <br> This system is *not* root-on-zfs. There is zfs, but it's data on <br> a non-boot virtual disk.<br> <br> "zpool status" invites me to upgrade the pool. I've not done = this (have <br> never done it with this vm, either), and don't want to unless I'm<b= r> absolutely certain upgrading the pool won't break everything.<br> <br> I note from a (similar, but different context) thread last September<br> <a href=3D"https://lists.freebsd.org/archives/freebsd-current/2024-Septembe= r/006378.html" rel=3D"noreferrer noreferrer" target=3D"_blank">https://list= s.freebsd.org/archives/freebsd-current/2024-September/006378.html</a><br> that FreeBSD uses "the guest's boot loader and the host's /boo= t/lua files"<br> but I'm clueless how this would apply in an amd64 context with Azure<br= > as the host.<br> <br> What do i have to do? Also, is the warning safe to ignore in this context?<= br></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">I= n 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 had= n't actually updated the loader, it will fail safe for loaders installe= d from FreeBSD 11 and newer (though not relevant to your use case). It shou= ld be in the release notes for 13.4 as a known issue, but the process for p= ost release revision is murky at best.</div><div dir=3D"auto"><br></div><di= v dir=3D"auto">The host vs guest issue you highlighted is a different thing= and applies only to bhyve.</div><div dir=3D"auto"><br></div><div dir=3D"au= to">Warner</div><div dir=3D"auto"><div class=3D"gmail_quote gmail_quote_con= tainer"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border= -left:1px #ccc solid;padding-left:1ex"> </blockquote></div></div></div> --000000000000b62454062a809441--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrhd4uXdSosaE434g_eveXxd82t8oAEHrNEWQ_icY38fQ>