From owner-freebsd-virtualization@freebsd.org  Sat Jul 22 01:21:14 2017
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13008C78E40
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Sat, 22 Jul 2017 01:21:14 +0000 (UTC)
 (envelope-from grehan@freebsd.org)
Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12])
 by mx1.freebsd.org (Postfix) with ESMTP id C5E7664BAC
 for <freebsd-virtualization@freebsd.org>; Sat, 22 Jul 2017 01:21:13 +0000 (UTC)
 (envelope-from grehan@freebsd.org)
Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au
 [203.13.68.150])
 by alto.onthenet.com.au (Postfix) with ESMTPS id 2C0A2204042B
 for <freebsd-virtualization@freebsd.org>;
 Sat, 22 Jul 2017 11:21:12 +1000 (AEST)
Received: from localhost (iredmail.onthenet.com.au [127.0.0.1])
 by iredmail.onthenet.com.au (Postfix) with ESMTP id 23DB1280F8B
 for <freebsd-virtualization@freebsd.org>;
 Sat, 22 Jul 2017 11:21:12 +1000 (AEST)
X-Amavis-Modified: Mail body modified (using disclaimer) -
 iredmail.onthenet.com.au
Received: from iredmail.onthenet.com.au ([127.0.0.1])
 by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id MHciA1-uV-ED for <freebsd-virtualization@freebsd.org>;
 Sat, 22 Jul 2017 11:21:12 +1000 (AEST)
Received: from Peters-MacBook-Pro-2.local
 (96-82-80-65-static.hfc.comcastbusiness.net [96.82.80.65])
 by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 22A972809A2;
 Sat, 22 Jul 2017 11:21:10 +1000 (AEST)
Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?)
From: Peter Grehan <grehan@freebsd.org>
To: Zaphod Beeblebrox <zbeeble@gmail.com>
Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
References: <CACpH0MewKeeif2egxD=hjwiXYa5tNV0ACTz6PrM=+Z3=7Nfryg@mail.gmail.com>
 <CACpH0MeozpUFakVg9z68hwyT9Ewx3sn1P6KorgzHPvoH7kcFdg@mail.gmail.com>
 <CACpH0Md4Dxq9jOSrzs9N7PbEG9F5mAsYaTjz3s+OfKCFkDQ2+Q@mail.gmail.com>
 <792ad5df-9e03-a332-c9a1-0b04ba69786a@freebsd.org>
 <CACpH0Mc44CaQXvXqctm2MdJpifbbjFpbDQO9D+QP8RD-QYmMfw@mail.gmail.com>
 <a58776f3-2712-0a7c-4f2f-98cfe3815d92@freebsd.org>
Message-ID: <50047e9f-de8d-e94a-35d1-e3a7bcf7a0fd@freebsd.org>
Date: Fri, 21 Jul 2017 18:21:06 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0)
 Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <a58776f3-2712-0a7c-4f2f-98cfe3815d92@freebsd.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.2 cv=XKlAcUpE c=1 sm=1 tr=0
 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17
 a=IkcTkHD0fZMA:10 a=G3gG6ho9WtcA:10 a=fkTWZIAttzpCodc6tDkA:9
 a=QEXdDO2ut3YA:10 wl=host:3
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2017 01:21:14 -0000

On 7/21/17 5:54 PM, Peter Grehan wrote:
>> 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.
> 
>   Are you using a "-j" option to buildworld in the guest ? You'd need at 
> least 1G for each vCPU when doing parallel builds (and preferably a bit 
> more) or you will swap heavily.

  I should add: I'm not saying this will fix the problem, but if it is 
an issue with the guest swapping, giving the guest more RAM is a workaround.

later,

Peter.