Specify location where volatile clones are spawned

[thandlovsky]

Is your feature request related to a problem? Please describe.
We have a very large image and will have many users, but only 8 drive slots. To accommodate this large SSDs are used for the image pool. When in production I anticipate a large amount of wear on the drives causing many failures.
To help mitigate wear, storing the volatile clone images that are created for the users in tempfs or a separate pool with cheaper drives, may help.

Describe the solution you'd like
A checkbox to turn feature on or off in machines settings for base image.
When on, a text input to specify directory where volatile vm will be spawned

Describe alternatives you've considered
At startup, coping the large VM image into a tempfs and editing the necessary config files, so that the clones are also spawned there.

Thank you!