Regarding shared storage, both sshfs & nfs turned out to be less of a fit for my usage, nor is copying (qvm-copy) or moving (qvm-move) files) a desirable solution (because of storage size limits, aka budget-limit).
My usage being a (mis)use of qubes for restraining software.
I find qubes very easy to:
- restrain resource usage (“normally” w/ something like cgroup, ulimit) &
- prevent software from affecting the operations of other software (“normally” w/ something like chroot/jail).
I was looking into suggestions mentioned in “Shared folders (perhaps over qrexec?)”: Rudd-O’s shared folders (continued in “Design questions for the next steps of the Qubes shared folders service”) and: qvm-mount, qubes-sync, qubes-intervmfs, detaching and attaching an image to a vm. Concluded my text would be less of a fit for github, went to (and reluctantly joined) this forum and found this topic “Best Way To Setup A Global Share Folder?” where “folders” are mentioned specifically. But using folders does not seem to be a requirement though, so a ‘network attached storage’ of a ‘distributed file system’ also seems fitting. And found the topic “Attach USB device to multiple Qubes at once?”, which implies that read-only access is easy to accomplish.
But for now, I have turned to looking into ‘shared-disk file system’, and into how qubes determines certain device-names and/or the paths for the mount-points (for instance by doing a github search for xvdb). Thinking that such shared storage will need to be network-able from the vm/qube-side, considering a long term goal of qubes-air/-in-the-cloud.
In short, for me, it would be nice, if there was an option for a configurable (rw,ro) shared storage among the storage options in the management interfaces (api, vm manager-vm details).