On 3/30/19 2:22 PM, Ville Rantanen wrote:
Hey,
I am in the process of configuring Qubes, and I have one question to
save myself a bit of time in figuring it out myself.
Can a thin pool that I assign to Qubes with "qvm-pool --add" have other
logical volumes than the ones created and used by Qubes? Or does Qubes
assume the pool is dedicated to it and does it remove the existing
logical volumes when I add the pool?
Other lvs are OK to have in qubes-assigned pools. I'm not aware of any
caveats except for the obvious: Name your custom lvs something different
from what Qubes would ever use for a vm. So in general, avoid lv names
that begin with 'vm-' and end with one of the following: private, root,
snap, back, volatile.
My incremental lv backup tool creates additional lvs (snapshots) that
take a vm volume's name and append a unique suffix. Also, Qubes
currently uses dashes only for separators, so using the other 3
lvm-allowed symbols ( . _ + ) will set your names apart.
--
Chris Laprise, [email protected]
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/df11fca8-19db-f2ca-7e4a-3cd717847d44%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
