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
..
mix	qubes: port core to python3	2017-01-20 16:42:51 +01:00
__init__.py	app: do not create 'default' storage pool	2017-07-25 06:20:42 +02:00
adminvm.py	tests: fix AdminVM test	2017-07-29 05:07:45 +02:00
appvm.py	storage: move volume_config['source'] filling to one place	2017-07-26 03:26:11 +02:00
dispvm.py	vm/dispvm: add auto_cleanup property, unify creating new DispVM	2017-08-06 20:54:09 +02:00
init.py	vm: improve sending events for tags and features	2017-06-14 10:44:23 +02:00
qubesvm.py	vm/qubesvm: do not assign all host vCPUs to a qube	2017-07-17 12:33:52 +02:00