Marek Marczykowski-Górecki 691a6f4d8c vm/dispvm: add auto_cleanup property, unify creating new DispVM ... Add auto_cleanup property, which remove DispVM after its shutdown - this is to unify DispVM handling - less places needing special handling after DispVM shutdown. New DispVM inherit all settings from respective AppVM. Move this from classmethod `DispVM.from_appvm()`, to DispVM constructor. This unify creating new DispVM with any other VM class. Notable exception are attached devices - because only one running VM can have a device attached, this would prevent second DispVM started from the same AppVM. If one need DispVM with some device attached, one can create DispVM with auto_cleanup=False. Such DispVM will still not have persistent storage (as any other DispVM). Tests included. QubesOS/qubes-issues#2974		2017-08-06 20:54:09 +02:00
..
integ
tools
vm	vm/dispvm: add auto_cleanup property, unify creating new DispVM	2017-08-06 20:54:09 +02:00
__init__.py	vm/dispvm: add auto_cleanup property, unify creating new DispVM	2017-08-06 20:54:09 +02:00
api_admin.py	Merge branch 'stats'	2017-07-29 05:05:32 +02:00
api_misc.py
api.py
app.py
devices_block.py
devices.py
events.py
ext.py
extra.py	When running tests clean up and remove qubesd.socket	2017-07-14 14:54:04 +02:00
firewall.py
init.py
run.py
storage_file.py
storage_kernels.py
storage_lvm.py	tests: various fixes for storage tests	2017-07-26 03:26:13 +02:00
storage.py
tarwriter.py	tarwriter: use new PAX format, instead of old GNU for sparse files	2017-07-21 03:14:06 +02:00