Date: Tue, 19 Mar 2019 01:49:10 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> To: freebsd-virtualization@freebsd.org, FreeBSD <freebsd-stable@freebsd.org> Subject: Re: bhyve zfs resizing Message-ID: <49d8d837-b734-0770-20fd-a439c6436a4d@quip.cz> In-Reply-To: <20190319002325.GD91631@rpi3.zyxst.net> References: <20190318150404.GB91631@rpi3.zyxst.net> <CAOtMX2j55KCrwSgoPUmGfgsRYdL4ivwC0kf=ODqHf7gwe6H3Gg@mail.gmail.com> <20190318152525.GC91631@rpi3.zyxst.net> <f7b4a7d7-4c07-22f2-8d56-9a62c685ea5c@quip.cz> <20190319002325.GD91631@rpi3.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
tech-lists wrote on 2019/03/19 01:23: > Am I correct? In that I should have used UFS in the guest rather than > zfs? Or was it the encryption? As Alan already wrote - you can use ZFS inside of the guest but I would never choose ZFS in zvol backed guest. I prefere UFS. It is faster and does not need so much memory as ZFS does. My VirtualBox and Bhyve guests are small. Sometimes <1GB of RAM. Sometimes 2GB of RAM and that is very small for ZFS. May be you can try to limit ZFS ARC size in /etc/sysctl.conf or in /boot/loader.conf vfs.zfs.arc_max Choose about 1/4 of your guest's RAM size and test it again. Kind regards Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49d8d837-b734-0770-20fd-a439c6436a4d>