From nobody Sat Sep 16 17:02:57 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 4Rny6t6j6jz4sc7N for ; Sat, 16 Sep 2023 17:03:02 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Rny6r5txMz3C9t for ; Sat, 16 Sep 2023 17:03:00 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=bUsK5HMN; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="VAQ8BW/i"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.29 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 729565C008B for ; Sat, 16 Sep 2023 13:02:59 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sat, 16 Sep 2023 13:02:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1694883779; x=1694970179; bh=3B v8aenFoiUIIR56NCF/Gv7wxR/qPwazxhmZ8zy9EHA=; b=bUsK5HMNKXpV2fS3xS 8g6CDTSqBtok2YlflRstCyjc3OvAQx+Fgm5jecE3auEw4mtEQpcQNsWBlU5Gr7nL M0YUl7hyZcdN5872bs35ztnPZBsDriiWXSklAB5wPyo9cGymv6d73SGnm0qiHXzd eXgwcILdHrBf7JdZODHcBpzeMT2IfIKldWmeeOI9P946VssRJ0uevL8Pn2Jrjk+K gIMuH/FSgWKey25lar859bV97AzbqCdkVT9BEo8N+RJKU1xUGUYHay50qfmyeeo7 WKlF7PcHYWSHVbUN5nEYUL7BeSLecAMSUBsq3Yg7q9pdKbM1jzuQaXu4caHStffu 4r+w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1694883779; x=1694970179; bh=3Bv8aenFoiUII R56NCF/Gv7wxR/qPwazxhmZ8zy9EHA=; b=VAQ8BW/isLyCOAx5WtvWu4dF64ohM J0fMK27Qbn3Pod6UFRM8CFlLKG4aQDgFMpO5GjRnit8Px9pgf15Ri6dFbecgNsSX Y+INpB7kpXksefYeAXAy2PECDlDA/ks0lNTBaUpIqkcTSQU4CgcWcYV+31ZE05lX waFgVYtTPQsll0k0ZxKZy0x6gZ8618PWR6xhCxKbnSSDAcnYzJCJKV/MlZRsf14K AWtsFq13U7vGMv9bsnmWPczwP3HSvZfcFjxhqrdvaeVHfpf4JO/deTiTdimpEg4M rA/tF36COWHDwGG0mi+gm7NO7dUZ6kSnD03u7r8C6aopS59gAzNsHJhqg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudejgedguddtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttd ertddttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffr rghtthgvrhhnpeekleduvdelhfeileefgffghfffkedtheellefgudfgvdegkeejjedutd ehhefgueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhm pehvohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sat, 16 Sep 2023 13:02:58 -0400 (EDT) Date: Sat, 16 Sep 2023 18:02:57 +0100 From: void To: freebsd-current@freebsd.org Subject: Re: CURRRENT snapshot won't boot due missing ZFS feature Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: <7EEF3435-064D-4C3C-98E4-2B27A788DB43.ref@yahoo.com> <7EEF3435-064D-4C3C-98E4-2B27A788DB43@yahoo.com> 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 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <7EEF3435-064D-4C3C-98E4-2B27A788DB43@yahoo.com> X-Spamd-Bar: ---- X-Spamd-Result: default: False [-5.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[66.111.4.29:from]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.29:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Rny6r5txMz3C9t On Sat, Sep 16, 2023 at 08:43:49AM -0700, Mark Millard wrote: >void wrote on >Date: Sat, 16 Sep 2023 12:12:02 UTC : > >> On Sat, Sep 16, 2023 at 12:55:19PM +0100, Warner Losh wrote: >> >> >Yes. The boot loader comes from the host. It must know how to read ZFS. >> >> It knows how to read zfs. > >I expect Warner was indicating: you have a (efi?) loader that knows >how to deal with the features listed in: What I'm astonished with is this part about the boot loader for the guest coming from the host, with respect to zfs, needing zfs properties the guest has but the host hasn't. I have some freebsd zfs guests on linux (redhat) hosts as well. They're using KVM. A few on Azure. These hosts (as I understand it) don't have zfs at all. None of the guests are root-on-zfs. So I guess the issue is with bhyve and the new zfs exposes it? If it's not happening with other hypervisors. Does the issue affect root-on-zfs guests only on freebsd zfs hosts or would it also affect those booting to ufs but then loading zfs for their data? I'm doing some testing now with a zfs-on-root 13.2 guest, will try src upgrading it to 14-stable, on this openzfs-2.1(?) host. --