Date: Fri, 21 Jul 2017 20:50:54 -0400 From: Zaphod Beeblebrox <zbeeble@gmail.com> To: Peter Grehan <grehan@freebsd.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) Message-ID: <CACpH0Mc44CaQXvXqctm2MdJpifbbjFpbDQO9D%2BQP8RD-QYmMfw@mail.gmail.com> In-Reply-To: <792ad5df-9e03-a332-c9a1-0b04ba69786a@freebsd.org> References: <CACpH0MewKeeif2egxD=hjwiXYa5tNV0ACTz6PrM=%2BZ3=7Nfryg@mail.gmail.com> <CACpH0MeozpUFakVg9z68hwyT9Ewx3sn1P6KorgzHPvoH7kcFdg@mail.gmail.com> <CACpH0Md4Dxq9jOSrzs9N7PbEG9F5mAsYaTjz3s%2BOfKCFkDQ2%2BQ@mail.gmail.com> <792ad5df-9e03-a332-c9a1-0b04ba69786a@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
remember that the quoted problem is spit out by the guest, not the host. That said, the 'top' line on the frozen bhyve was: 29380 root 22 20 0 1060M 928M kqread 5 218:32 399.30% bhyve ... indicating that the bhyve had almost all it's memory... and the system had also 500M free when I checked it. On Fri, Jul 21, 2017 at 7:03 PM, Peter Grehan <grehan@freebsd.org> wrote: > oh ... and ... the console spit out: >> >> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4522, size: 8192 >> >> (swap is on a separate zVol). >> > > Ok - you may have hit a separate issue. Is ZFS ARC limited on your setup > ? If bhyve and ZFS (and other consumers) end up fighting for memory, > everyone loses :( A general rule of thumb is to limit ARC to less than the > bhyve VM usage + a few additional gig for the base system. > > The FreeBSD default of giving ZFS all memory minus 1GB doesn't work too > well when running VMs. > > later, > > Peter. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACpH0Mc44CaQXvXqctm2MdJpifbbjFpbDQO9D%2BQP8RD-QYmMfw>