Date: Tue, 15 Nov 2022 10:00:59 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 267779] bhyve crashes host kernel: panic: rendezvous not in progress Message-ID: <bug-267779-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267779 Bug ID: 267779 Summary: bhyve crashes host kernel: panic: rendezvous not in progress Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: crash Severity: Affects Only Me Priority: --- Component: bhyve Assignee: virtualization@FreeBSD.org Reporter: bz@FreeBSD.org For testing purposes I am restarting a FreeBSD in FreeBSd bhyve instance mo= re or less in a loop. It has 1 PCI passthru in case that matters, a local file based disk. During guest boot, often while printing CPU/TLB information the host will p= anic after a few iterations; I updated main to last night and it still happens: panic: rendezvous not in progress cpuid =3D 3 time =3D 1668475188 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe011567d= 790 vpanic() at vpanic+0x151/frame 0xfffffe011567d7e0 panic() at panic+0x43/frame 0xfffffe011567d840 vm_exit_rendezvous() at vm_exit_rendezvous+0x6a/frame 0xfffffe011567d850 vmx_run() at vmx_run+0x276c/frame 0xfffffe011567d9a0 vm_run() at vm_run+0x223/frame 0xfffffe011567daa0 vmmdev_ioctl() at vmmdev_ioctl+0x507/frame 0xfffffe011567db40 devfs_ioctl() at devfs_ioctl+0xcd/frame 0xfffffe011567db90 vn_ioctl() at vn_ioctl+0x131/frame 0xfffffe011567dca0 devfs_ioctl_f() at devfs_ioctl_f+0x1e/frame 0xfffffe011567dcc0 kern_ioctl() at kern_ioctl+0x202/frame 0xfffffe011567dd30 sys_ioctl() at sys_ioctl+0x12a/frame 0xfffffe011567de00 amd64_syscall() at amd64_syscall+0x12e/frame 0xfffffe011567df30 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe011567df30 --- syscall (54, FreeBSD ELF64, ioctl), rip =3D 0x4802ffe533a, rsp =3D 0x480bf115e58, rbp =3D 0x480bf115f10 --- #11 kdb_enter (why=3D<optimized out>, msg=3D<optimized out>) at /worktrees/wireless-dev/sys/kern/subr_kdb.c:509 #12 0xffffffff80bec6b2 in vpanic (fmt=3D<optimized out>, ap=3Dap@entry=3D0xfffffe011567d820) at /worktrees/wireless-dev/sys/kern/kern_shutdown.c:967 #13 0xffffffff80bec453 in panic ( fmt=3D0xffffffff81e8de70 <cnputs_mtx> "p\336)\201\377\377\377\377") at /worktrees/wireless-dev/sys/kern/kern_shutdown.c:903 #14 0xffffffff82557f2a in vm_exit_rendezvous (vm=3D<optimized out>, vcpuid= =3D0, vcpuid@entry=3D3, rip=3D18446744071581284439, rip@entry=3D0) at /worktrees/wireless-dev/sys/amd64/vmm/vmm.c:1699 #15 0xffffffff82570b1c in vmx_run (arg=3D0xfffffe0114abf000, vcpu=3D0, rip=3D-2128267177, pmap=3D0xfffffe00e0e3e530, evinfo=3D0x1) at /worktrees/wireless-dev/sys/amd64/vmm/intel/vmx.c:3070 #16 0xffffffff82558223 in vm_run (vm=3D0xfffffe00e0502000, vmrun=3Dvmrun@entry=3D0xfffff8000437bb00) at /worktrees/wireless-dev/sys/amd64/vmm/vmm.c:1775 #17 0xffffffff8255b917 in vmmdev_ioctl (cdev=3D<optimized out>, cmd=3D<optimized out>, data=3D0xfffff8000437bb00 "\003", fflag=3D<optimized out>, td=3D<optimized out>) at /worktrees/wireless-dev/sys/amd64/vmm/vmm_dev.c:504 #18 0xffffffff80a7bd0d in devfs_ioctl (ap=3D0xfffffe011567dba8) at /worktrees/wireless-dev/sys/fs/devfs/devfs_vnops.c:933 #19 0xffffffff80cf6201 in vn_ioctl (fp=3D0xfffff8000a0cd140, com=3D<optimized out>, data=3D0xfffff8000437bb00, active_cred=3D0xfffff80428875b00, td=3D0x0) at /worktrees/wireless-dev/sys/kern/vfs_vnops.c:1699 #20 0xffffffff80a7c3be in devfs_ioctl_f (fp=3D0xffffffff81e8de70 <cnputs_mt= x>, com=3D0, data=3D0xffffffff81253857, cred=3D0x1, td=3D0x0) at /worktrees/wireless-dev/sys/fs/devfs/devfs_vnops.c:864 #21 0xffffffff80c644a2 in fo_ioctl (fp=3D0xfffff8000a0cd140, com=3D32306928= 65, data=3D0x1c200001, active_cred=3D0x1, td=3D<optimized out>) at /worktrees/wireless-dev/sys/sys/file.h:365 #22 kern_ioctl (td=3Dtd@entry=3D0xfffffe0114aefe40, fd=3D<optimized out>, com=3Dcom@entry=3D3230692865, data=3D0x1c200001 <error: Cannot access memory at address 0x1c200001>, data@entry=3D0xfffff8000437bb00 "\003") at /worktrees/wireless-dev/sys/kern/sys_generic.c:803 #23 0xffffffff80c641ea in sys_ioctl (td=3D0xfffffe0114aefe40, uap=3D0xfffffe0114af0238) at /worktrees/wireless-dev/sys/kern/sys_generic.c:711 #24 0xffffffff810d33be in syscallenter (td=3D<optimized out>) at /worktrees/wireless-dev/sys/amd64/amd64/../../kern/subr_syscall.c:189 #25 amd64_syscall (td=3D0xfffffe0114aefe40, traced=3D0) at /worktrees/wireless-dev/sys/amd64/amd64/trap.c:1200 #26 <signal handler called> #27 0x000004802ffe533a in ?? () --=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-267779-27103>