Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 5 Aug 2021 15:06:37 +0100
From:      David Chisnall <theraven@FreeBSD.org>
To:        Juraj Lutter <juraj@lutter.sk>, Alan Somers <asomers@freebsd.org>
Cc:        freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: Building ZFS disk images
Message-ID:  <dff637dd-fdad-358e-dc12-9faf69ddf8b5@FreeBSD.org>
In-Reply-To: <D2DD2C49-03B2-4D63-852D-5C0E9145F7C7@lutter.sk>
References:  <16473d5f-1727-233a-7a95-a21c5b48b9ce@FreeBSD.org> <CAOtMX2hxj%2Bxehjk-5QoF4ao4z3Fs7ifxTjzRsQrXz7Z8g16eVw@mail.gmail.com> <D2DD2C49-03B2-4D63-852D-5C0E9145F7C7@lutter.sk>

next in thread | previous in thread | raw e-mail | index | archive | help
On 05/08/2021 14:01, Juraj Lutter wrote:
> 
>> On 5 Aug 2021, at 14:53, Alan Somers<asomers@freebsd.org>  wrote:
>>
>> 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<theraven@freebsd.org>  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.
> Would poudriere work for you? man poudriere-image

Wow, there's a lot of stuff I didn't know poudriere could do!  It looks 
as if it can produce a GPT partition table with all of the bootable 
bits, or it can produce a ZFS disk image.  I guess it wouldn't be too 
difficult to teach it to do both?

David




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dff637dd-fdad-358e-dc12-9faf69ddf8b5>