From owner-freebsd-xen@freebsd.org  Mon Aug  7 11:50:24 2017
Return-Path: <owner-freebsd-xen@freebsd.org>
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 17C5FDCDBC2
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon,  7 Aug 2017 11:50:24 +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 0635966E31
 for <freebsd-xen@FreeBSD.org>; Mon,  7 Aug 2017 11:50:24 +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 v77BoMLZ075754
 for <freebsd-xen@FreeBSD.org>; Mon, 7 Aug 2017 11:50:23 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 11:50:23 +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: royger@freebsd.org
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: cc
Message-ID: <bug-221220-23905-pohKV7Z14e@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221220-23905@https.bugs.freebsd.org/bugzilla/>
References: <bug-221220-23905@https.bugs.freebsd.org/bugzilla/>
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
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Aug 2017 11:50:24 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221220

Roger Pau Monn=C3=83=C2=A9 <royger@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |royger@freebsd.org

--- Comment #5 from Roger Pau Monn=C3=83=C2=A9 <royger@freebsd.org> ---
I've been trying to reproduce this, but so far I'm unable to do so. Have you
tried if removing bios=3Dovmf solves the problem?

Also, do you know anything about the underlying host? Number of physical CP=
Us
and number of vCPUs assigned to Dom0?

--=20
You are receiving this mail because:
You are the assignee for the bug.=