Hello, This is stable/13-n254707-dc1ba2a432ff bhyve guest on stable/13-n250910-fb231965f9b host. This was at the console. Have rebooted it, seems ok so far. Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xa fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff8236750d stack pointer = 0x28:0xfffffe00933c6bd0 frame pointer = 0x28:0xfffffe00933c6bd0 code segment = base rx0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 62897 (postgres) trap number = 12 panic: page fault cpuid = 0 time = 1677640772 KDB: stack backtrace: #0 0xffffffff80c55435 at kdb_backtrace+0x65 #1 0xffffffff80c07e51 at vpanic+0x151 #2 0xffffffff80c07cf3 at panic+0x43 #3 0xffffffff810c1fa7 at trap_fatal+0x387 #4 0xffffffff810c1fff at trap_pfault+0x4f #5 0xffffffff810994b8 at calltrap+0x8 #6 0xffffffff8250e228 at zil_commit_impl+0x848 #7 0xffffffff8250a24f at zfs_fsync+0x7f #8 0xffffffff80cf75f7 at kern_fsync+0x127 #9 0xffffffff810c289c at amd64_syscall+0x10c #10 0xffffffff81099dcb at fast_syscall_common+0xf8 Uptime: 10m20s Dumping 433 out of 8150 MB:..4%..12%..23%..34%..41%..52%..63%..71%..82%..93% Dump complete Consoles: userboot
(In reply to void from comment #0) > … stable/13-n254707-dc1ba2a432ff bhyve guest > on stable/13-n250910-fb231965f9b host. … Respectively: <https://cgit.freebsd.org/src/log/?h=stable%2F13&qt=range&q=dc1ba2a432ff> (2023-02-28) <https://cgit.freebsd.org/src/log/?h=stable%2F13&qt=range&q=fb231965f9b> (2022-05-21) Given the version bumps in March 2022 <https://docs.freebsd.org/en/books/porters-handbook/versions/#freebsd-versions-table-13>, have you considered updating the host?
Interesting, thanks. I think the crash may have been down to overcommitment of resources to bhyve on the host. Since reporting, haven't observed a crash (so far) on any guest. But yes, freebsd on the host needs to be updated when the downtime can be scheduled.