Date: Sun, 21 Apr 2019 14:12:26 -0500 From: Dustin Marquess <dmarquess@gmail.com> To: FreeBSD virtualization mailing list <freebsd-virtualization@freebsd.org>, "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Subject: Re: bhyve, sparse disk image and trim support? Message-ID: <7adb331c-7563-4d8d-a6bc-e616c6ff4299@Spark> In-Reply-To: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> References: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Using a sparse zvol and either the ahci-hd or nvme drivers should support= TRIM. -Dustin On Apr 21, 2019, 12:02 PM -0500, Bjoern A. Zeeb <bzeeb-lists=40lists.zabb= adoz.net>, wrote: > Hi, > > I have been wondering about this with other (commercial) virtualisation= > solutions in the past. If running on a =E2=80=9Cdisk image=E2=80=9D ide= ally I=E2=80=99d > love that image to be a sparse file and ideally I=E2=80=99d love for > bhyve/underlying virtualisation for the disk to understand TRIM so in > case one deletes huge junks inside the VM the disk image can actually > shrink again. > > Examples might be: you do a buildworld or an OS update in the guest and= > then want to delete the obj tree or temporary files after that. Now the= > disk image on the host has been bloated up, and could massively shrink > again saving space on the host. > > Do we support this=3F Has anyone worked on this=3F How do people deal w= ith > these problems=3F > > > /bz > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > freebsd-virtualization=40freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to =22freebsd-virtualization-unsubscribe=40= freebsd.org=22
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7adb331c-7563-4d8d-a6bc-e616c6ff4299>