Thanks for explaining.
IIUC (please correct me if I am wrong), this approach has the following specifics:
- It requires pre-writing of dummy data before writing the actual one
- Access to such volume requires a running qube hosting it
- There is a limit of 64 volumes (per hosting qube)
- All volumes created this way will show up in Qubes Devices menu
Is there a way to avoid those specifics?
My XY goal is to create a minimalist non-duplicating modular system (a split template of sorts) in which individual packages reside on separate volumes (modules) that can be attached selectively to particular AppVMs (similar to the way we currently have the root.img of the template attached). IOW, I am looking for possible workarounds of this.