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
