Date: Fri, 28 Jul 2017 05:35:46 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 215972] Bhyve crash more then 1 cpu AMD Message-ID: <bug-215972-27103-aELeYOGj3H@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215972-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-215972-27103@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=215972 --- Comment #21 from Peter Grehan <grehan@FreeBSD.org> --- (In reply to dgilbert from comment #20) Sorry, didn't know that was you. There are 2 other things to try here: - when the guest is hung, on the host issue bhyvectl --get-rip --cpu=0 --vm=<your vm name> bhyvectl --get-rip --cpu=1 --vm=<your vm name> bhyvectl --get-rip --cpu=2 --vm=<your vm name> bhyvectl --get-rip --cpu=3 --vm=<your vm name> You can look at what the resulting RIP values correspond to by restarting the guest, and within the guest, kgdb /boot/kernel/kernel x/i <rip value> - Run the same test with a 12-current guest. With luck, it will panic and drop into ddb. If it hangs but doesn't panic, for the guest to drop into ddb from the host by issuing bhyvectl --inject-nmi --vm=<your vm name> From within ddb you can issue a backtrace. -- 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-215972-27103-aELeYOGj3H>