So from a layman’s perspective, going over that documentation:
I edit: storage.conf in Dom0. Something like this:
[ghost_layer]
driver=xen
dir_path=/opt/ghost
I create the vm using:
qvm-create ghost --label=black --pool:ghost_layer
(Unsure if I have the syntax of pool right?)
Then I create folder:
/Users/ghost/ghost_volume
Then on Dom0 have a script that symlinks to the new folder:
#!/bin/bash
ln -s /opt/ghost /Users/ghost/ghost_volume
qvm-start ghost
Before starting the vm ghost, if I run the script ^^^, then everything for that vm will be routed to the ghost_volume.
If I don’t run the script, then start vm ghost, everything is routed to the primary drive?
Now when starting the vm ghost, without the script there would be no hard drive footprints of activity done using the vm when symlinked to ghost_volume.
Correct?
Can you see any unintended consequences as a result of state differences between overt layer state of the ghost vm, and ghost layer state of the vm?
Is there anything I would need to add to make sure file permissions translated correctly to the symlink state ghost_volume?