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
..
integ	tests: check if snap_on_start=True volumes are not persistent	2017-02-14 23:59:07 +01:00
tools	qubes: port core to python3	2017-01-20 16:42:51 +01:00
vm	qubes: port core to python3	2017-01-20 16:42:51 +01:00
__init__.py	misc python3 fixes	2017-02-07 17:07:52 +01:00
app.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
devices.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
events.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
extra.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
firewall.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
init.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
run.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
storage_file.py	storage: fix handling snap_on_start=True file volumes	2017-02-14 23:59:07 +01:00
storage_lvm.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
storage.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
tarwriter.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00