Created attachment 231002 [details]
Panic while rebooting guest
My FreeBSD bhyve host running 1 FreeBSD guest (both 14.0-CURRENT) is sporadically panicing with spinlock held too long. I have attached photos of the two panic messages I have seen.
The first panic happened when the guest was rebooting, the second when I was running a disk perf measurement in the vm.
I will set up better remote access when I am a the machine tomorrow so I can interact with it once it has paniced.
host: FreeBSD pokeitwithastick 14.0-CURRENT FreeBSD 14.0-CURRENT #8 main-n252356-01cad731921: Tue Jan 11 10:13:27 UTC 2022 tj@pokeitwithastick:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
Created attachment 231003 [details]
Panic while running disk test
Host is a AMD Ryzen 7 3700X 8-Core Processor, full dmesg is here:
Tom, could you find guilty commit from the list below (manually or by usage 'git bisect') ? How regularly did you run your tests last two-thee months?
$ git l sys/amd64/vmm/
6171e026be11 bhyve: add support for MTRR
c72e914cf108 vmm: vlapic resume can eat 100% CPU by vlapic_callout_handler
e2650af157bc Make CPU_SET macros compliant with other implementations
4c812fe61b7c vlapic: Schedule callouts on the local CPU
de8554295b47 cpuset(9): Add CPU_FOREACH_IS(SET|CLR) and modify consumers to use it
bcdc599dc2a1 Revert "cpuset(9): Add CPU_FOREACH_IS(SET|CLR) and modify consumers to use it"
9068f6ea697b cpuset(9): Add CPU_FOREACH_IS(SET|CLR) and modify consumers to use it
Yeah can do, but not until wednesday the com cable I have was 2mm and the headers on the motherboard are 2.54mm.