Date: Tue, 23 Apr 2019 08:56:24 +0200 From: "Patrick M. Hausen" <hausen@punkt.de> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: FreeBSD virtualization mailing list <freebsd-virtualization@freebsd.org> Subject: Re: bhyve, sparse disk image and trim support? Message-ID: <9E907736-8F90-4600-853C-7C2F7AF166BA@punkt.de> In-Reply-To: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> References: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net>
index | next in thread | previous in thread | raw e-mail
Hi! > Am 21.04.2019 um 19:01 schrieb Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net>: > Do we support this? Has anyone worked on this? How do people deal with these problems? I’m actually surprised this is supported for some configurations - thanks for starting the thread. As for how others deal with this - e.g. VMware files never shrink, but there is a „vacuuming“ function that compresses the virtual disk while the VM is offline in the workstation products. For ESXi I think the only way is to actually copy the image file to a new one with vmkfstools. Used to use defrag and sdelete a lot in Windows VMs in the past, then ran the compaction … Kind regards Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe info@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egelinghelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9E907736-8F90-4600-853C-7C2F7AF166BA>