From nobody Sat Sep 16 11:55: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 4RnqJ55fGFz4sWPJ for ; Sat, 16 Sep 2023 11:55:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 4RnqJ50MxCz3SVZ for ; Sat, 16 Sep 2023 11:55:33 +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=1uybr2Xh; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2a00:1450:4864:20::629) smtp.mailfrom=wlosh@bsdimp.com; dmarc=none Received: by mail-ej1-x629.google.com with SMTP id a640c23a62f3a-9936b3d0286so394723866b.0 for ; Sat, 16 Sep 2023 04:55:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1694865331; x=1695470131; 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=wtiujuOLHHgpsJyQ5JLY3ELxHl4FcFrZlbdhD97Xh3I=; b=1uybr2XhLjhOVH9X52P6nPozCqlN+Xh/ZZUF2zkEDag4bZ4Lvv10RiuASFUYPn4CRp q5uIRW6GeM85wDnt79xgtdR/OhATo2FPskrvEYaJ57KuL7/1Lfh/M7X4qiiTPH+f1csA VxXpQFUaHW5SBwQOKzPLjj6HztosOBQUTNMUsp2NAM0K44mS48KZcSYp2v6jnuFbTion Tf9iMj+ItqwiKkdXrQZVIRUJu5brZGG/BHlIuBXv6DpcfAgiBKvGuW4BX6i44kWIbEHC cUCWfJz7ruDxf89u/CaJziFxuoVyCk67LZ7+ltAX1WYkx11bUHLfqjRdlHHam6doUOFq X2Ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694865331; x=1695470131; 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=wtiujuOLHHgpsJyQ5JLY3ELxHl4FcFrZlbdhD97Xh3I=; b=Rj5MgxtWrsJ0UZQuJ9DEhnO+NyL0cb9H8S7lOkG6cT5ZpgrNEe7nu0toikmXRbNb75 imHZJ99fDDX35lHALmk+FVS3uwCnrwq5J4JSuFhUr5N9SHGqcvr7WD88WYIiMRrbh/zj yf/snM4WAWR8K2MxJiasRD+9P7EHlhKR/kVR33Cao9nUtwcbfiimXCSO5nlS6bs3mhuN v59QcBACJ8lWG8dCyCLCQ7XsbJE/rNSuQ14Rmh+RTo083QF/StvnRSbTkYE7FDc2+Dlb FBsNXKkK/2j1qDDC2qB+BnMPxx3sX/leqyqho4usa30xtj4WtA2oOOuz+JcxRlWgrdXo tlDg== X-Gm-Message-State: AOJu0YxsNcQE5XVNf4huDyHkxKkg1u2ZUjP3UWzSkRNHj/YWykZrG2fg GlH94NzqDw3QfY1HE2ufbxi9uiOFehR149LYgb1Rz3ufyMeTTGyQqg0= X-Google-Smtp-Source: AGHT+IHxK6V1SC4B12lFEBlERb2+8EFELw/BN3vg3Ml2sw9fNrXM1zY+O3cLx4TxOhyvHqJ163oppAjW2o90Iltqq2s= X-Received: by 2002:a17:906:18a1:b0:9a5:c401:85e9 with SMTP id c1-20020a17090618a100b009a5c40185e9mr3560233ejf.27.1694865331233; Sat, 16 Sep 2023 04:55:31 -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> In-Reply-To: From: Warner Losh Date: Sat, 16 Sep 2023 12:55:19 +0100 Message-ID: Subject: Re: CURRRENT snapshot won't boot due missing ZFS feature To: FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000002c4a506057896bb" X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-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]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::629:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ONE(0.00)[1]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[bsdimp.com]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com] X-Rspamd-Queue-Id: 4RnqJ50MxCz3SVZ --00000000000002c4a506057896bb Content-Type: text/plain; charset="UTF-8" On Sat, Sep 16, 2023, 12:06 PM void 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. > > This is still happening in the following context: > > host: stable/13-n256033 > bhyve guest was installed from FreeBSD-14.0-BETA2-amd64-bootonly.iso > > error on booting the guest > ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 > ERROR: cannot open /boot/lua/loader.lua: no such file or directory. > > This used to work with earlier -current (14-current) bhyve guests. > Is there a workaround? > > Does this mean that any bhyve host needs to be either at or above > the guest version in future? In other words, is having host > version less than guest not meant to work? > Yes. The boot loader comes from the host. It must know how to read ZFS. So either your bootable partitions must not have com.klarasystems:vdev_zaps_v2 in your BEs or you must have a new user boot. I think you can just install the one from 14, but haven't tried it. Warner -- > > --00000000000002c4a506057896bb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Sep 16, 2023, 12:06 PM void <void@f-m.fm> 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:
>
>=C2=A0 ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2
>
>(booting stops at this point)
>
>Seems like the boot loader is missing this recently added feature.

This is still happening in the following context:

host: stable/13-n256033
bhyve guest was installed from FreeBSD-14.0-BETA2-amd64-bootonly.iso

error on booting the guest
ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2
ERROR: cannot open /boot/lua/loader.lua: no such file or directory.

This used to work with earlier -current (14-current) bhyve guests.
Is there a workaround?

Does this mean that any bhyve host needs to be either at or above
the guest version in future? In other words, is having host
version less than guest not meant to work?

Yes. The boot loader comes from t= he host. It must know how to read ZFS. So either your bootable partitions m= ust not have com.klarasystems:vdev_zaps_v2 in your BEs or you must have a n= ew user boot. I think you can just install the one from 14, but haven't= tried it.

Warner=C2=A0<= /div>


--

--00000000000002c4a506057896bb--