Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?)

Zaphod Beeblebrox zbeeble at gmail.com
Sat Jul 22 00:50:57 UTC 2017


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 at 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.
>


More information about the freebsd-virtualization mailing list