Date: Fri, 21 Jul 2017 20:48:33 -0400 From: Zaphod Beeblebrox <zbeeble@gmail.com> To: Peter Grehan <grehan@freebsd.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) Message-ID: <CACpH0MdtPWZWaF52JLziwvSs1MdBcKpXBTY3u_4N2X0j09hHHw@mail.gmail.com> In-Reply-To: <490d70e2-ff8b-2a60-2eb7-669dadbcc2a9@freebsd.org> References: <CACpH0MewKeeif2egxD=hjwiXYa5tNV0ACTz6PrM=%2BZ3=7Nfryg@mail.gmail.com> <490d70e2-ff8b-2a60-2eb7-669dadbcc2a9@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACpH0MdtPWZWaF52JLziwvSs1MdBcKpXBTY3u_4N2X0j09hHHw>