19:14:33 <jdt> I'm exercising my Ansible playbooks for creating my microk8s cluster in Triton and deleted the server I was working with to recreate and rebuild. That's a bhyve VM using a PCI passthrough network interface. The delete operation caused the CN to crash and reboot.
19:14:45 <jdt> Is there a process I should go through to guard against that in the future?
19:15:13 <jdt> I didn't do anything special - it was running and a I just issued a "delete" command. I imagine if I shut it down nicely, maybe that would have been better?
19:22:38 <jdt> the hard reboot also left the VM in a weird state ("incomplete") and it took a couple of tries from the command line using vmadm to delete it. The first try timed out and left the vm in a "configured" stated. The second try deleted it successfully.
21:08:58 <danmcd> Can you share the kernel dump?
21:09:23 <danmcd> You shouldn't be able to panic a machine doing that.
21:33:38 <jdt> I do have global core dumps enabled, but it looks like my /cores (linked to /zones/global/cores) directory is empty.
21:34:24 <jbk> a kernel dump would be in /var/crash/volatile
21:34:30 <jbk> see if there's anything in there
21:34:47 <jdt> I do have a vmdump.0 file there from today.
21:35:00 <jdt> (and METRICS.csv and bounds)
21:35:18 <jbk> that would be it
21:35:42 <jdt> Cool. Let me know where to send it and I'll pass it along. The dump file is 2.61G
21:37:09 <jbk> i don't have a good place to receive it, but hopefully since dan,cd was interested he'll be able to provide something for you once he's back around
21:37:16 <jbk> err danmcd
21:37:21 <jdt> sounds good.