Date: Tue, 7 May 2019 09:59:47 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: New vm-image size is much smaller than previos Message-ID: <6cd1df8f-9fa6-4e7c-4146-bcff577dd78d@FreeBSD.org> In-Reply-To: <28d9446e246bcdb58f1fe48fce9900e054a5d4d3.camel@twc.com> References: <28d9446e246bcdb58f1fe48fce9900e054a5d4d3.camel@twc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/05/2019 17:10, David Boyd wrote: > The vm-image for 13.0-CURRENT > > FreeBSD-13.0-CURRENT-amd64-20190503-r347033.vmdk > > is only 4.0 GB in size. Previous images were about 31.0 GB. > > This smaller image doesn't leave much room to add packages and other > customizations. > Yes, the VM images are smaller, and deliberately so. The idea is that the image is basically shrunk to the minimum size -- just big enough to hold a standard install. Then when you deploy one of these images, you allocate a virtual drive of whatever size you need, and growfs(8) your filesystems (if using UFS) or allow your vdevs to expand to fill the space available (if using ZFS). This allows you to build a system of pretty much any feasible size and parallels the behaviour of eg. the AMIs available for AWS. Cheers, Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6cd1df8f-9fa6-4e7c-4146-bcff577dd78d>