Date: Thu, 1 Mar 2018 09:02:02 -0800 From: Peter Grehan <grehan@freebsd.org> To: Mike Tancsa <mike@sentex.net> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?) Message-ID: <f3aa32cd-6f3e-9e81-eb2c-0ba3a506893e@freebsd.org> In-Reply-To: <7fa0b7a0-492e-6ded-3b5c-1edeff54d746@sentex.net> References: <a687883a-b2a8-5b18-f63e-754a2ed445c0@sentex.net> <bbcc09cf-0072-8510-156f-5c20c301d43f@sentex.net> <92a60e14-f532-2647-d45d-b500fc59ba88@sentex.net> <CAMgUhpo1C_0L86Xkzmuz5%2Be3C3zk5RNkVS9aEBEwF-2XZ4d1sQ@mail.gmail.com> <425be16f-9fdc-9ed6-72b1-02e28bfd130f@sentex.net> <2f2b6f96-d6ef-8e02-966d-dcbbfb0c92fb@freebsd.org> <48768738-e699-fd06-9154-9b5be1bbabcc@sentex.net> <a7ede219-73a6-80a3-87be-ce27769cfcd1@freebsd.org> <36c062e4-352b-eebe-5f08-1af250d98eee@sentex.net> <7fa0b7a0-492e-6ded-3b5c-1edeff54d746@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>> On the Epyc it seemed to take a longer, but eventually the box locked >> up and the watchdog ended up rebooting the server. I started 3, vCPU >> guests all with separate CPU's pinned. It lasted 9hrs. > > The Ryzen board also locked up with just 2 VMs running, and all vCPUs > pinned to separate cores. Thanks for that Mike - it rules out any issues related to vCPUs moving around on physical cores. I'd like to now see if there's a way to get this to happen quicker - perhaps running the test with increasing numbers of guest vCPUs ? From what I've seen, the network test only really uses 2 vCPUs so it's probably ok to even go to oversubscribing. I'll get this going on my Ryzen. later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f3aa32cd-6f3e-9e81-eb2c-0ba3a506893e>