Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 07 Aug 2017 12:14:12 +0000
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
Message-ID:  <bug-221220-23905-0V01nP8rWs@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/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221220

--- Comment #7 from John <john@keates.nl> ---
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.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221220-23905-0V01nP8rWs>