Qubes/core-admin
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
0c43329188
core-admin/qubes/storage
History
Marek Marczykowski-Górecki 01aedb7f18
storage: fix handling snap_on_start=True file volumes 
Use the right cow image and apply the second layer to provide read-write
access. The correct setup is:
 - base image + base cow -> read-only snapshot (base changes "cached"
   until committed)
 - read-only snapshot + VM cow -> read-write snapshot (changes discarded
   after VM shutdown)

This way, even VM without Qubes-specific startup scripts will can
benefit from Template VMs, while VMs with Qubes-specific startup scripts
may still see original root.img content (for possible signature
verification, when storage domain got implemented).

QubesOS/qubes-issues#2256
2017-02-14 23:59:07 +01:00
..
__init__.py misc python3 fixes 2017-02-07 17:07:52 +01:00
domain.py qubes: port core to python3 2017-01-20 16:42:51 +01:00
file.py storage: fix handling snap_on_start=True file volumes 2017-02-14 23:59:07 +01:00
kernels.py qubes: port core to python3 2017-01-20 16:42:51 +01:00
lvm.py misc python3 fixes 2017-02-07 17:07:52 +01:00
README.md Merge remote-tracking branch 'marmarek/master' into core3-devel 2016-03-03 01:13:51 +01:00

README.md

WNI File storage

Before v3.1 there existed a draft wni storage. You can find it in the git history

(it was in /core/storage directory, now gone)