16:57:04 Anyone else playing around with propolis? 17:08:31 propolis-cli -s 127.0.0.1 state run just reboots the host 17:11:32 * aru looks up what is propolis apart from the bee goo 17:58:35 It generated a panic? 17:59:09 elwisp: What host are you running on? The version of propolis/bhyve from illumos generally need to be fairly in sync. 18:04:07 i run it on helios which runs in a VM 18:04:31 Did the helios vm panic or the guest inside? 18:04:37 Hard to say what happens because as soon as i run the "state run" it just reboots the machine 18:04:44 Does the hypervisor you're running helios in provide nested guest? 18:04:47 *nested virt 18:04:51 ah, that might be it! 18:04:54 lemme check 18:05:47 And what's rebooting? The VM or the hypervisor? 18:06:48 I've got to step out for a while, but knowing which of those is rebooting is going to change our next steps a lot. Specifically not your propolis guest, but the helios VM or the hypervisor running the helios VM. 18:11:35 the VM 18:12:01 i enabled nesting now, going to try again 18:12:13 but doing a get of state shows that the vm is just "creating" 18:12:52 nesting wasnt the issue :) 18:32:52 cheers, got a question on SMF, in case I missed something in the past year or two: did it by chance grow any way to execute installable late-shutdown logic? (like rc.6/* scripts allowed, or systemd-shutdown hooks)? 18:33:47 namely I want to integrate the NUT ability to call the UPS driver when the system is otherwise quiesced, to tell the device to cut the power (when shutdown conditions call for that) 18:34:22 which needs a way to either let certain daemons to survive past the killall phase, or for the shutdown scripts to 18:34:48 call the nutshutdown script perhaps after they remounted R/O and lost most of the filesystem that way