From nobody Thu Aug 05 12:53:48 2021 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 9518B7C9FAB for ; Thu, 5 Aug 2021 12:54:14 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f169.google.com (mail-oi1-f169.google.com [209.85.167.169]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GgT863kS1z51rs; Thu, 5 Aug 2021 12:54:14 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f169.google.com with SMTP id 21so7176905oin.8; Thu, 05 Aug 2021 05:54:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=R8SK7TYyZi6v0uSytv3Ms9kmkfgsdUJnyyPyNNdgSSU=; b=d9t4E1Vza04lt0Kk+0ix9l8ARLBc+SpvreXRnbRLih7rGiS4TQ2oedQ4q3edd2sVrX CbCaYiuDmAqJ8BBgJDVvAEIKtt51hk26Youo43BluKpL3kEbfiWPWj2nEueZeMS6phjA UESPE40WfplRFEy6/WSKM3nKLL7LABc3XAefrNUKcpYwUw4scKEWUCBxgZQI/O3/37/v KAxuwtw4tC1h7xji0WD2WIOqr6FOG9a0AAFNJOcCpC74iLqaLWE60hL7bAxNLoPEdWVH +mdC1TwOySvuEIat4QXj6efHgcAYNEB//0ipVAOR74OmKNyylO5D6/d2IHPdiuYdhAAl qTNA== X-Gm-Message-State: AOAM530jtOhdfyBStLEcuTi8fX7mLo6iv7/fjbzB04pj9H89NI3obhEV OkdVtTEtytBXDGrBrJcrBQx1MNGWMwrZWjKehnjSmFir X-Google-Smtp-Source: ABdhPJzB/OWzhs99vDxJDegnGrOwTV4HWgho1Zn7lWH4WJPcldGKvjDgnB3+dzXg6uxc8fGUH5Sj1BlTnZPraTmehRY= X-Received: by 2002:a05:6808:188a:: with SMTP id bi10mr3481278oib.73.1628168047603; Thu, 05 Aug 2021 05:54:07 -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: <16473d5f-1727-233a-7a95-a21c5b48b9ce@FreeBSD.org> In-Reply-To: <16473d5f-1727-233a-7a95-a21c5b48b9ce@FreeBSD.org> From: Alan Somers Date: Thu, 5 Aug 2021 07:53:48 -0500 Message-ID: Subject: Re: Building ZFS disk images To: David Chisnall Cc: freebsd-current Content-Type: multipart/alternative; boundary="0000000000001cb39b05c8cf6a52" X-Rspamd-Queue-Id: 4GgT863kS1z51rs X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000001cb39b05c8cf6a52 Content-Type: text/plain; charset="UTF-8" I don't know of any way to do it using the official release scripts either. One problem is that every ZFS pool and file system is supposed to have a unique GUID. So any kind of ZFS release builder would need to re-guid the pool on first boot. On Thu, Aug 5, 2021, 6:41 AM David Chisnall wrote: > Hi, > > Does anyone know how to build ZFS disk images from any existing tooling? > > I haven't used UFS for over a decade now and the official cloud images > are all UFS, so I end up doing an install from the CD ISO into Hyper-V > locally and then exporting the VHD, but that can't be the most efficient > way of getting a FreeBSD VHD with ZFS. > > I haven't been able to find any documentation and reading the release > scripts they seem to hard-code UFS. > > David > > --0000000000001cb39b05c8cf6a52--