Date: Sat, 18 Oct 2025 21:35:16 +0000 From: Jonathan Vasquez <jon@xyinn.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: virtualization@freebsd.org Subject: Re: bhyve exists with 0 booting a custom main kernel - how to debug? Message-ID: <R1N9RuHF5bdlLKuBVEVFT9hl4smjMHD1sxgdY1GT2Uf1b5bo6noGODSta92BLJZcLpaeM1439Msybo6GR94ZzcJ2Br12Cg0iV53equ14GqQ=@xyinn.org> In-Reply-To: <8655o8r6-2or9-821o-qq85-r9187s8sq582@mnoonqbm.arg> References: <8655o8r6-2or9-821o-qq85-r9187s8sq582@mnoonqbm.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
Hey Bjoern, Yea I also sometimes get some crashes (seldomly) with my bhyve gaming virtual machine and I also don't really get much info. The only info I have is doing "bhyvectl --vm=<name of your vm> --get-exit-reason" and that's basically it, which it isn't the most helpful. You can also do "--get-all" in the previous command to get all of the stats for that vm (even if it already crashed, as long as it's still in /dev/vmm/<name of your vm>". Someone did mention before I could try and use dtrace and see what happens but yea. It would be nice to have more documentation on how to debug bhyve for a variety of different cases. Jonathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?R1N9RuHF5bdlLKuBVEVFT9hl4smjMHD1sxgdY1GT2Uf1b5bo6noGODSta92BLJZcLpaeM1439Msybo6GR94ZzcJ2Br12Cg0iV53equ14GqQ=>