From nobody Thu Jun 8 17:32:19 2023 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 4QcWW42BrVz4c7wX for ; Thu, 8 Jun 2023 17:32:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QcWW40WRxz3p53 for ; Thu, 8 Jun 2023 17:32:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62b.google.com with SMTP id a640c23a62f3a-977ed383b8aso157567566b.3 for ; Thu, 08 Jun 2023 10:32:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1686245550; x=1688837550; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QBtibLup0uETIsqYBKWu/L8lD8kM/QluDhAoDacViLs=; b=Qu9bfWJBZjxCZKkU50svkenCAB3L4Ei5MFkTX/CHFXzCYhrulq6Ntva+iKONETUEV9 /SX2Y9qCXtUqByjK0Ct+oBKN7lIILRrg9acuFeb2sPTuY/YI7Y9GxuW8+rfn0rZtt5tr scIDEjFmtAH8W+QWYI4c/+zDMxdSrzlO2b5su+Gi1XTPWSWKc73IQc3QqNU99RHkAtc3 M+az+GISrgn5hcsrim/6wxhpKNo562TTucDHwki0/d/LJ8ZWRJ1nVqyXIcrrDXgOI4EG 9lTejKmci5QOPmZRZU399W65Kq0QOG0ncp0itXmCMALsUrDFAkrYZqTmVErc15mOQh1p H6FA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686245550; x=1688837550; h=cc: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=QBtibLup0uETIsqYBKWu/L8lD8kM/QluDhAoDacViLs=; b=idQU0FJKNoL+qnu1N1o136IB+2rhyVjeVLBDRW/Bh9vrpvPL3/cbw3lYSh49UKZnS1 YnJXWqFysNYPnyUsEn+G+En7vWYKEYdz9m/3t6584Ao8g8+eSd0dQ1ov1JVNk0XFsM+t QxOXeTCJZSPPbI1XOPvJNG9laYqahP4NqigFrhakEsqJa11UR/0WVneK8E2bhgViQ2db VI/tSQgLh5fjpWMF5DBgFh2gwWeWKLdp8No7MdwY5d9w2wfO68dHfP1tB2gQiFhrM6nG PvlZ4o91mlDhftJCWrEWiKXmMMgpJQzKaSPFJ97t5sQ5R94UXB/rhK+al6PVQGmaAZub 2Jkg== X-Gm-Message-State: AC+VfDzkjmi1FjEpK16931lO/o14Uv9w9XBTT7KZsZLaBIUbFbH17Y5O 3QArG7vAAMeTDbkyCVF12XRyT1Ir1+p6m6er2Iy3NpdAu6Jy7Oga X-Google-Smtp-Source: ACHHUZ5KxH4rRZHus92qkxupcF9pfVB+M+iO1WnGrbf0C1ByIHbGQxTvBb3SYkfQG42iutZAS2IevrLZwfrecgp48cw= X-Received: by 2002:a17:906:db0e:b0:974:6026:a315 with SMTP id xj14-20020a170906db0e00b009746026a315mr296172ejb.44.1686245550404; Thu, 08 Jun 2023 10:32:30 -0700 (PDT) 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 References: <20230608181115.7c97ea19.grembo@freebsd.org> <20230608162012.GV1219@FreeBSD.org> <20230608190623.14ab4ba8.grembo@freebsd.org> <20230608191637.21101c39.grembo@freebsd.org> In-Reply-To: <20230608191637.21101c39.grembo@freebsd.org> From: Warner Losh Date: Thu, 8 Jun 2023 11:32:19 -0600 Message-ID: Subject: Re: CURRRENT snapshot won't boot due missing ZFS feature To: Michael Gmelin Cc: Glen Barber , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000094fb105fda1a332" X-Rspamd-Queue-Id: 4QcWW40WRxz3p53 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000094fb105fda1a332 Content-Type: text/plain; charset="UTF-8" On Thu, Jun 8, 2023, 11:18 AM Michael Gmelin wrote: > > > On Thu, 8 Jun 2023 19:06:23 +0200 > Michael Gmelin wrote: > > > On Thu, 8 Jun 2023 16:20:12 +0000 > > Glen Barber wrote: > > > > > On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote: > > > > Hi, > > > > > > > > I didn't dig into this yet. > > > > > > > > After installing the current 14-snapshot (June 1st) in a > > > > bhyve-vm, I get this on boot: > > > > > > > > ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 > > > > > > > > (booting stops at this point) > > > > > > > > Seems like the boot loader is missing this recently added feature. > > > > > > > > > > Can you try today's snapshot? They are propagated to most mirrors > > > now. > > > > > > > Tried today's snaphot, same problem. > > > > # reboot > > Waiting (max 60 seconds) for system process `vnlru' to stop... done > > Waiting (max 60 seconds) for system process `syncer' to stop... > > Syncing disks, vnodes remaining... 0 0 0 0 done > > All buffers synced. > > Uptime: 4m14s > > Consoles: userboot > > > > FreeBSD/amd64 User boot lua, Revision 1.2 > > ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 > > ERROR: cannot open /boot/lua/loader.lua: no such file or directory. > > > > > > Type '?' for a list of commands, 'help' for more detailed help. > > OK > > > > > > That's after installing CURRENT in a fresh vm managed by vm-bhyve > > using bsdinstall's automatic ZFS option. > > > > Thinking about this, it's possible that vm-bhyve is using the zfs boot > loader from the host machine. > > Please consider this noise, unless you hear from me again. > Yes. It does. This can be an unfortunate design choice at times. Warner Best > Michael > > -- > Michael Gmelin > > --000000000000094fb105fda1a332 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jun 8, 2023, 11:18 AM Michael Gmelin <grembo@freebsd.org> wrote:


On Thu, 8 Jun 2023 19:06:23 +0200
Michael Gmelin <grembo@freebsd.org> wrote:

> On Thu, 8 Jun 2023 16:20:12 +0000
> Glen Barber <gjb@freebsd.org> wrote:
>
> > On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote:= =C2=A0
> > > Hi,
> > >
> > > I didn't dig into this yet.
> > >
> > > After installing the current 14-snapshot (June 1st) in a
> > > bhyve-vm, I get this on boot:
> > >
> > >=C2=A0 =C2=A0ZFS: unsupported feature: com.klarasystems:vdev_= zaps_v2
> > >
> > > (booting stops at this point)
> > >
> > > Seems like the boot loader is missing this recently added fe= ature.
> > >=C2=A0 =C2=A0 =C2=A0
> >
> > Can you try today's snapshot?=C2=A0 They are propagated to mo= st mirrors
> > now.
> >=C2=A0 =C2=A0
>
> Tried today's snaphot, same problem.
>
>=C2=A0 =C2=A0# reboot
>=C2=A0 =C2=A0Waiting (max 60 seconds) for system process `vnlru' to= stop... done
>=C2=A0 =C2=A0Waiting (max 60 seconds) for system process `syncer' t= o stop...
>=C2=A0 =C2=A0Syncing disks, vnodes remaining... 0 0 0 0 done
>=C2=A0 =C2=A0All buffers synced.
>=C2=A0 =C2=A0Uptime: 4m14s
>=C2=A0 =C2=A0Consoles: userboot=C2=A0
>
>=C2=A0 =C2=A0FreeBSD/amd64 User boot lua, Revision 1.2
>=C2=A0 =C2=A0ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 >=C2=A0 =C2=A0ERROR: cannot open /boot/lua/loader.lua: no such file or d= irectory.
>
>
>=C2=A0 =C2=A0Type '?' for a list of commands, 'help' fo= r more detailed help.
>=C2=A0 =C2=A0OK
>
>
> That's after installing CURRENT in a fresh vm managed by vm-bhyve<= br> > using bsdinstall's automatic ZFS option.
>

Thinking about this, it's possible that vm-bhyve is using the zfs boot<= br> loader from the host machine.

Please consider this noise, unless you hear from me again.
=

Yes. It does. Thi= s can be an unfortunate design choice at times.=C2=A0

Warner

Best
Michael

--
Michael Gmelin

--000000000000094fb105fda1a332--