From owner-freebsd-xen@freebsd.org Mon Aug 7 12:14:12 2017 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B36ADCF6D4 for ; Mon, 7 Aug 2017 12:14:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6993367DBD for ; Mon, 7 Aug 2017 12:14:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v77CECrf088444 for ; Mon, 7 Aug 2017 12:14:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces Date: Mon, 07 Aug 2017 12:14:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: john@keates.nl X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Aug 2017 12:14:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221220 --- Comment #7 from John --- The VM is booting in EFI mode so removing ovmf wouldn't work. I haven't tri= ed this issue in BIOS mode, so it may be EFI-only. I can access the dom0, but = it's not built with debug=3Dy. I do have serial console, so I can access the Xen= debug menu. I have attached the xl dmesg. Regarding the underlying hardware: it's a Dell R730xd with 2x E5-2630 v4 (t= otal of 40 threads IIRC). It is a test setup with nothing else running on it, on= ly the dom0 and FreeBSD 11.0 (pfSense 2.4). There is no CPU or vCPU pinning. T= he reason I'm using OVMF is to have the EFI console available over the virtual serial console (as well as the bootloader and of course the first tty). Underlying disk is a ZVOL for the domU, there is 192GB RAM, so it shouldn't= be resource constrained. --=20 You are receiving this mail because: You are the assignee for the bug.=