ntrlsur Posted September 30, 2014 Share Posted September 30, 2014 I didn't see it in a quick browse of the forums so thought I would ask.. It seems that whenever I stop the array my VM's get shutdown as well. I am running B10. Is this designed behavior? I don't remember this being the case with earlier beta versions but I could be wrong. The reason I ask is that I run a domain controller with dhcp and a few other VM's that effect the network connectivity. I would hate to have to shutdown VM's just to add a disk to the array.. Quote Link to comment
dmacias Posted September 30, 2014 Share Posted September 30, 2014 I didn't see it in a quick browse of the forums so thought I would ask.. It seems that whenever I stop the array my VM's get shutdown as well. I am running B10. Is this designed behavior? I don't remember this being the case with earlier beta versions but I could be wrong. The reason I ask is that I run a domain controller with dhcp and a few other VM's that effect the network connectivity. I would hate to have to shutdown VM's just to add a disk to the array.. I take it you're using xen? You could edit /usr/local/emhttp/plugins/xenMan/events/unmounting_disks. Then have your go script copy your edits at boot also you would need a shutdown script to shutdown your vm's when you shutdown unRAID. Same goes it your using KVM and virtMan plugin. You could just move that to a k script if using powerdown plugin. Quote Link to comment
ntrlsur Posted October 1, 2014 Author Share Posted October 1, 2014 I am using Xen.. Thanks for the information dmacias.. Quote Link to comment
ntrlsur Posted October 1, 2014 Author Share Posted October 1, 2014 I ended up renaming the scripts to _bak and added an entry to my go file to do that on boot before the array starts.. Thanks again.. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.