From owner-freebsd-virtualization@freebsd.org Thu Mar 1 13:00:24 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1727F27766 for ; Thu, 1 Mar 2018 13:00:23 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9841183352; Thu, 1 Mar 2018 13:00:23 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w21D0MoO080100 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 1 Mar 2018 08:00:22 -0500 (EST) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.net [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w21D0K8s053861; Thu, 1 Mar 2018 08:00:21 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?) To: Peter Grehan Cc: "freebsd-virtualization@freebsd.org" References: <92a60e14-f532-2647-d45d-b500fc59ba88@sentex.net> <425be16f-9fdc-9ed6-72b1-02e28bfd130f@sentex.net> <2f2b6f96-d6ef-8e02-966d-dcbbfb0c92fb@freebsd.org> <48768738-e699-fd06-9154-9b5be1bbabcc@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <36c062e4-352b-eebe-5f08-1af250d98eee@sentex.net> Date: Thu, 1 Mar 2018 08:00:19 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2018 13:00:24 -0000 On 2/27/2018 6:30 PM, Peter Grehan wrote: >  i.e. for a configuration that will lock up, run the same configuration > but with vCPUs pinned. For example, a 4 vCPU guest that will have vCPUs > 0-3 pinned to host physical CPUs 7-10 would look like: > >  -c 4 -p 0:7 -p 1:8 -p 2:9 -p 3:10 Hi Peter, 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. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada