Date: Tue, 10 Oct 2017 21:06:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 222916] [bhyve] Debian guest kernel panics with message "CPU#0 stuck for Xs!" Message-ID: <bug-222916-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222916 Bug ID: 222916 Summary: [bhyve] Debian guest kernel panics with message "CPU#0 stuck for Xs!" Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: karihre@gmail.com Created attachment 187061 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187061&action= =3Dedit Syslog output of Debian guest leading up to hanging Dear all, I've been having a fair amount of crashes on a Debian 9 (kernel 4.9.0) guest running under the bhyve hypervisor on FreeBSD 11.1-RELEASE-p1 (GENERIC). The general pattern is that the guest stays up for 2-6 days before completely hanging, at which point it must be hard restarted. This appears to happen under some load (often following the start of some c= ron jobs) and be preceded some hours of kernel warnings on the guest side. I fi= nd nothing out of the ordinary on the host side with logs not appearing to rev= eal much of anything. CPU is Intel Xeon E3-1275 v6 Kaby Lake and motherboard is Supermicro MBD-X11SSH-LN4F-O. Bhyve startup command line is: bhyve -AHP \ -s 0:0,hostbridge \ -s 1:0,lpc \ -s 2:0,virtio-net,tap0 \ -s 3:0,virtio-net,tap1 \ -s 4:0,virtio-blk,/dev/zvol/tank/vms/strokkur-root \ -s 5:0,virtio-blk,/dev/zvol/tank/vms/strokkur-scratch \ -s 6:0,virtio-blk,/dev/zvol/tank/vms/strokkur-temp \ -s 29,fbuf,tcp=3D127.0.0.1:5900,w=3D800,h=3D600 \ -l com1,stdio \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \ -c 4 \ -m 32G strokkur A logged in user will see "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [apache2:18004]" or a similar message, however this message is not log= ged to syslog. The relevant Debian syslog entries leading up to the most recent crash are attached. In total, each crash produges roughly 600MB of log entries, so I'= ve cut out a lot.=20 If I can provide any more information please let me know. Thank you, Kari Hreinsson --=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-222916-8>