From nobody Mon Dec 30 17:59:47 2024 X-Original-To: freebsd-fs@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 4YMP5H3mccz5hXCW for ; Mon, 30 Dec 2024 18:00:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YMP5G3fm8z40fr for ; Mon, 30 Dec 2024 18:00:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=qDp9PbyG; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::1036) smtp.mailfrom=wlosh@bsdimp.com; dmarc=none Received: by mail-pj1-x1036.google.com with SMTP id 98e67ed59e1d1-2ee8e8e29f6so10182868a91.0 for ; Mon, 30 Dec 2024 10:00:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1735581599; x=1736186399; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=O4NkPWWrK4kce+t5EFm8Nhv+F6gYFwnuc5r9CefzY/I=; b=qDp9PbyGDRxigioMvJ0nWTAirPN0xQX+b0wjeAFItY5hExuSP5zSzC9NRbW90wF8sP kui3yH0gazIrBS1Dq7NhTRtjJZ9cb0HqrBQWI6Pxz0eUSzNQ3q7P5PvR+IMj/gGbehTm s3JvReHp02MuwhjMKpwuosDFWEETkVJnkThSPA5aLO8/DCFgdACrFZFHqG/vVXLHv8rv N+NnyWamAIcE5RzofgYoeS4BylQS/fg2EQAIhRp+t7XbXlINDRCJZEQiQBPCTuk75Fkw P45NO5VxMTMy+7HEMftR7YzF6cyh8pD6Qzs+qc1yFo0IwhVoKfylEsP9xyavt+BVXwZD efow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1735581599; x=1736186399; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=O4NkPWWrK4kce+t5EFm8Nhv+F6gYFwnuc5r9CefzY/I=; b=lEoo6dPWH0u3qFIYWe26KCPx2rXKGK4UtWbmDcgnALpAcaojLuLjDVo6p81Sbjfy3R 9+8KZabOVVElJEOurHrp4k8vXCuI5riAfy0f5WGHd78hTY5oG6p6F2LJqgIHegz/AiPB c+6T2W5Zqwo7LuYzuWHveO70967K4y5Csutkl6eGpqOiL1kjXj8pTYhXzzVwXrgJqBAz lnb4c3tdB/cUPtMddog2sstv7xfcRzLBSmX8rviWJi9YFZiqgzmZvE4HrPv16vY6H2yC KgVft4DO8BB4NWKUAFiYii+3FrgA2dCJaAFos655zdOSsjpt2ZC36tbD0eqCOQ6INVv8 pqVA== X-Gm-Message-State: AOJu0YyicDDelyPCf8hXzOZg28UvK3zGKMKmzwzqqDVBNyjDLw5q0R9M ROdN5HLdZk7rg7x/n4TeHJUq31cZpQkZqUcC2jdfzW+HE1zfUBn4pqpdVJDgScXVm0x2bopyLeg StZMq9rckLMzSoX1Ug+uPLnYVyX8LBSwu4U5vKFfdQE+h+9t43ac= X-Gm-Gg: ASbGncu547n+Imkqw6bCCwWhWJLlFBF+RFlVMYv+yIlRbWxJprIwyTFqcHg1CoE9GhT pNqt3q4pDfbUQJ5t5qQlJOBqKVFZFqwf6MPVhcNQkDHTyz2ApbN8N8agH3ftqY/HZKZJa X-Google-Smtp-Source: AGHT+IGrsPO6EuCEIdAcqw9Wun8pTOS/3rMs25tKs3Ow4nO5A6ppCOzROdlP9v8/UF5IcZ1jMmq5OuCev3/r/bEVaUw= X-Received: by 2002:a17:90b:524a:b0:2ee:5edc:4b2 with SMTP id 98e67ed59e1d1-2f452e45b77mr55172957a91.20.1735581599400; Mon, 30 Dec 2024 09:59:59 -0800 (PST) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Mon, 30 Dec 2024 10:59:47 -0700 Message-ID: Subject: Re: "Loader needs to be updated" (azure guest context) To: FreeBSD FS , FreeBSD-STABLE Mailing List Content-Type: multipart/alternative; boundary="000000000000b62454062a809441" X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; DMARC_NA(0.00)[bsdimp.com]; RCPT_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1036:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4YMP5G3fm8z40fr X-Spamd-Bar: -- --000000000000b62454062a809441 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Dec 30, 2024, 8:45=E2=80=AFAM void 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


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 severa= l
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.
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 updat= ed"
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://list= s.freebsd.org/archives/freebsd-current/2024-September/006378.html
that FreeBSD uses "the guest's boot loader and the host's /boo= t/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?<= br>

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.

The host vs guest issue you highlighted is a different thing= and applies only to bhyve.

Warner
--000000000000b62454062a809441--