Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?)
Zaphod Beeblebrox
zbeeble at gmail.com
Sat Jul 22 00:48:36 UTC 2017
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 <grehan at freebsd.org> wrote:
> 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 bhyve/SVM. It appears somewhat related to
> processor speed (I can't repro on a 2.3GHz 8 CPU Opteron 6320, but can hit
> it after 15 mins or so on a Ryzen 1700, with/without SMT).
>
> Anish and I are currently chasing this and have repros. An experiment you
> could try is to run with the vCPUs pinned i.e. for a 4 vCPU guest, add the
> options "-p 0:1 -p 1:2 -p 2:3 -p 3:4".
>
> later,
>
> Peter.
>
More information about the freebsd-virtualization
mailing list