Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upSupport VM private block devices on any vm #3889
Comments
andrewdavidwong
added
enhancement
C: other
labels
May 10, 2018
andrewdavidwong
added this to the Release 4.1 milestone
May 10, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
starius commentedMay 10, 2018
Qubes OS version:
R4.0
Affected component(s):
Dom0 kernel/storage layer
General notes:
Usecase: I'd like to store VMs on a remote machine and "bind" them locally. When I use such a VM, its data is synchronized with the remove machine on the fly - like sshfs but for whole AppVM.
qvm-blockallows to mount a device from one VM to another, but not asxvdb(aka private.img). Probably I already can use a foreign device (e.g. asxvdi), copy /rw to it and use bind mounts or symlinks to do what I want, but it is not convenient and looks ugly. I'd like to be able to create a VM using such a device originating in an arbitrary vm as private.img for new VM. I see that Qubes R4 has a concept of storage pools - it looks we just need a pool driver to use block devices from vms.Related issues:
#3820 Support VM private block devices on external media