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 200 1060M 928M kqread 5 218:32 399.30%
bhyve
... indicating that the bhyve had almost all it's m
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 200 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
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 200 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 w
I tried the -p 0:1 -p 1:2 -p 2:3 -p 3:4 bit. If I may say, it felt a
little "chunky" ... but that could have just been a perception.
Anyways... still hung the guest.
On Fri, Jul 21, 2017 at 6:58 PM, Peter Grehan wrote:
> Hi,
>
> What should be next steps here? This is repeatable. The host is
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 lo
oh ... and ... the console spit out:
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4522, size: 8192
(swap is on a separate zVol).
On Fri, Jul 21, 2017 at 6:59 PM, Zaphod Beeblebrox
wrote:
> ... curiously, top running on the guest reveals (the point at which the
> bhyve wedges):
>
> 887
... curiously, top running on the guest reveals (the point at which the
bhyve wedges):
88722 root 1 520 109M 105M pfault 3 0:03 42.37%
llvm-tblgen
88687 root 1 520 374M 347M pfault 2 0:04 38.24%
llvm-tblgen
88668 root 1 520 236M 225M pf
Hi,
What should be next steps here? This is repeatable. The host is stable
(it can makeworld -j32 in about 25 minutes ... so it's hardware seems
good). Is this an AMD bug? Is it bad to use ZFS ZVols?
ZVols are fine. Is the guest panic a spinlock timeout ?
I believe this is a bug in bhyv
Since I found out that I can't run a Samba directory server in a jail, I've
had the setup of a bhyve on my list. I had toyed with Bhyve 6 or 8 months
ago, and still had the images, so I zfs cloned one and set about a source
upgrade.
This ignomineously hung.
So... I upgraded the host to 11.1-RC3,
