Max Herrgård wrote: > Max Herrgård <[EMAIL PROTECTED]> added the comment: > > Patch not committed. Feature added through a different approach though, see > http://leaf.dragonflybsd.org/mailarchive/commits/2007-05/msg00228.html . >
This patch should't be committed - it's messy and not the way Matt suggested I clean it up, but the commit referenced is absolutely not the same thing so this shouldn't be marked resolved - unless people don't want the feature anymore, in which case I'll continue to maintain the patch for as long as I'm interested in it. The functionality implemented for this issue (#647), the *host* system is able to signal the *guest* VKERNEL to shut down cleanly (e.g. when the host does a halt and forgets to shut down the guest VK's), With the committed code above, the VK is able to shut -itself- down cleanly, but the host continues to have no way of doing so - Signals from outside will kill the VK and leave the VKD's in an inconsistant state, possibly resulting in a loss of data within the VK system I responded to Matt's commit because I had a second patch in mind that did the same thing (vkernel *self*-initiated shutdown/reboot) - was probably going to tackle that later... as I see it, the two compliment each other.. In any case, hoping to clean up / resubmit this weekend, more than likely with a second signal handler to take advantage of Matt's new reboot code. Thanks, - Chris
