Whats up with that ?? Does it do more then just list the VM's , maybe some actual file checks etc ?  When in the morning i select my VM tab, it only comes up after 30 seconds or so. When investigating , it seems to do a spinup of my array drives, which are enjoying their sleep .

That should not happen right ? Regardless if the VM's on the list have anything on array drives or not. Even more so when they are off.

 

Also in my case have 3 active VM's only (the rest off) and these have all their files on dedicated UD.

 

Running on latest rc4

Where is the libvirt.img file located?  I can see the VM tab wanting to access that, and if it's stored on the array, then in order to locate it drive(s) may have to spin up. 

 

Possible resolutions

• If it's stored in system and it's a cache-only share, set the libvirt image location to be /mnt/cache/system/... instead of /mnt/user
• Install Dynamix Folder Caching

Nope, all my VM, libvirt , docker, appdata are on a dedicated btrfs UD SSD mirror.

So no reason for it to spin up the drives.

Seems it also scans for non running VM's and its vdisks apparently. I had 2 that where pointing to data on the array, but where dummy templates and not running so was wierd and easily overlooked. But never mind. Its not that important, was just wondering if it was me