So basically you can put any folder where you want, you just have to be clear about your structure. What you want to do here would be an action within the VM, which also means that your VM has to communicate with CEPH. This can open up security gaps again, as the hypervisor and CEPH network are usually not exposed to the outside world.
What you should do here is create a separation at the hypervisor level. To do this, create your VM and put one disk on the local storage and a second on the CEPH. During the OS installation you can then select the paths of the directories and, for example, move /mnt to the CEPH disk. Of course, this can also be done when it is already installed, but it may require more effort or a few hurdles here and there. It really depends on what you're moving from where to where.
Personally, I would always advise against such a constellation. A VM should reside entirely on a single storage. This makes backups or migrations much easier and doesn't cause any problems.
If you were to divide important system folders of your operating system between the two storages and, for example, the CEPH fails, then the VM will no longer do it either.
What is the reason for this wish? There may be a simpler or better alternative.
What you should do here is create a separation at the hypervisor level. To do this, create your VM and put one disk on the local storage and a second on the CEPH. During the OS installation you can then select the paths of the directories and, for example, move /mnt to the CEPH disk. Of course, this can also be done when it is already installed, but it may require more effort or a few hurdles here and there. It really depends on what you're moving from where to where.
Personally, I would always advise against such a constellation. A VM should reside entirely on a single storage. This makes backups or migrations much easier and doesn't cause any problems.
If you were to divide important system folders of your operating system between the two storages and, for example, the CEPH fails, then the VM will no longer do it either.
What is the reason for this wish? There may be a simpler or better alternative.
