Keep certain VM's running without array started


Recommended Posts

Hmm.. I‘m sorry I have only „tested“ this behaviour with the power outage I had. I did not stop the array with the GUI or anything. I thought the array is offline during a parity check which is definitely not right.

I forgot I had my array in „auto start“.

 

Nevertheless, it would be really a good idea to be able to run VMs from unassigned devices or cache drives with the array offline.

 

Sorry again = (

Link to comment

Allowing access to array members (cache included) while the array is stopped is probably not going to happen, for various reasons Tom has stated before.

 

However...

 

I see no real reason that we couldn't allow VM's that aren't on the array to operate. It's not like you couldn't set up a VM configuration where all the required elements were on a non array device, but it wouldn't be able to easily share those elements with the VM's currently configured. You would need a separate XML storage location, and an iso location for install media.

 

Maybe a GUI section for array limited VM's, and another for VM's on unassigned devices?

 

As soon as limetech actually takes control of UD instead of relying on dlandon to maintain it, I see no reason why we can't have 2 VM types. However, as long as limetech doesn't actively manage unassigned devices, it's probably not going to happen unless someone writes a plugin.

Link to comment
  • 8 months later...

Unraid noob here, but it looks like this feature is something that I need as well.  Specifically, I have a Zerotier docker running that only uses the cache drive.  If I make a change on the server that requires stopping and starting the array then the docker shuts down and I lose access to the server.  I only have remote access to the server so this is a huge issue.

Link to comment

+1

I'd also like to see the ability to start specific docker containers. If the data lives entirely on cache would be the condition to allow this. I.E. anything mapped to /mnt/user* would immediately disable this capability. 

 

I think RegEx could probably handle checking VM XML and Docker config for any reference to a non cache directory.

Link to comment
  • 5 months later...
  • 1 month later...

+1 from me as well. It's really the only thing giving me pause for pulling the trigger on actually purchasing once the trial is up - all my vms/containers/shares are on zfs anyway, so all having an array does for me in the first place is allow me to actually use all the things that have nothing to do with it.

 

... Which is probably why this will unfortunately never happen. If there's no array requirement, then with the current design, there's nothing stopping someone from just making a new bootable usb each time (copying over the config files from the last one) and never ponying up. Then there'd be nothing prodding folks to actually pay for a license, in the same tangible way at least (imo).

Link to comment
  • 2 months later...
  • 4 weeks later...
  • 2 months later...
1 minute ago, Interstellar said:

 

Surely the same way that you do now for a path that doesn't exist? 

A path that doesn't exist currently is created in RAM when written to, and if you try to read from it, returns file not found.

 

I was asking for a way forward, as in how to accomplish what you are asking for.

Link to comment
26 minutes ago, jonathanm said:

A path that doesn't exist currently is created in RAM when written to, and if you try to read from it, returns file not found.

 

I was asking for a way forward, as in how to accomplish what you are asking for.

 

Really? Seems a bit odd to create a dir/file in RAM rather than say "does not exist"?

 

Alternatively, given that as far as I'm aware there is a fixed list of potential paths to the array(s). Therefore something like if the path contains "/mnt/user" or "/mnt/diskX" or "/mnt/cache" then it is an array dependent VM/docker and will be skipped at initial docker/VM starts.

 

Then when you start the array you can see which dockers/VMs haven't been started due to having an array dependency and start them then.

 

Given only one of the 20 odd VMs/Dockers I currently run depend on the array (and is actually the only reason I have a "cache" drive (I don't use the array cache feature because of performance reasons) and some would benefit from not being array dependent, then its a fairly key feature for me going forward and actually the only one I can currently think of that I need from UnRAID.

 

Edited by Interstellar
Link to comment
  • 2 weeks later...

+1

 

I could definitely see this as a very useful feature.  I would prefer that it go to unassigned drives or extra pools when they're available.  I'd prefer not to put them on my cache drives.  As I add network necessary VMs like pihole, I hadn't really thought about all DNS services being down while my array was down.

Link to comment
  • 4 weeks later...

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.