Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Jul 2017 19:01:08 -0400
From:      Zaphod Beeblebrox <zbeeble@gmail.com>
To:        "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject:   Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?)
Message-ID:  <CACpH0Md4Dxq9jOSrzs9N7PbEG9F5mAsYaTjz3s%2BOfKCFkDQ2%2BQ@mail.gmail.com>
In-Reply-To: <CACpH0MeozpUFakVg9z68hwyT9Ewx3sn1P6KorgzHPvoH7kcFdg@mail.gmail.com>
References:  <CACpH0MewKeeif2egxD=hjwiXYa5tNV0ACTz6PrM=%2BZ3=7Nfryg@mail.gmail.com> <CACpH0MeozpUFakVg9z68hwyT9Ewx3sn1P6KorgzHPvoH7kcFdg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <zbeeble@gmail.com>
wrote:

> ... curiously, top running on the guest reveals (the point at which the
> bhyve wedges):
>
> 88722 root          1  52    0   109M   105M pfault  3   0:03  42.37%
> llvm-tblgen
> 88687 root          1  52    0   374M   347M pfault  2   0:04  38.24%
> llvm-tblgen
> 88668 root          1  52    0   236M   225M pfault  0   0:04  35.11%
> llvm-tblgen
> 88743 root          1  52    0 55460K 26392K pfault  3   0:00  10.23% cc
>
> ... where top on the host just shows 100% bhyve 100% busy on 4 threads.
>
>
> On Fri, Jul 21, 2017 at 6:43 PM, Zaphod Beeblebrox <zbeeble@gmail.com>
> wrote:
>
>> 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, and I reinstalled a fresh guest
>> from the 11.1-RC3 install CD.  The guest uses UFS2 on a 40G disk, the
>> server is an AMD 9590 with 32G RAM and a 40T ZFS array.
>>
>> After installation, I started the guest again with 1G ram, 4 processors
>> (of the 8 on the source CPU) and tried a buildworld again.  This time the
>> guest crashed and rebooted.
>>
>> 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?
>>
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACpH0Md4Dxq9jOSrzs9N7PbEG9F5mAsYaTjz3s%2BOfKCFkDQ2%2BQ>