691a6f4d8c
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 |
||
---|---|---|
ci | ||
contrib | ||
doc | ||
etc | ||
linux | ||
qubes | ||
qubes-rpc | ||
qubes-rpc-policy | ||
qubespolicy | ||
qvm-tools | ||
relaxng | ||
rpm_spec | ||
templates | ||
test-packages | ||
tests | ||
.coveragerc | ||
.gitignore | ||
.pylintrc | ||
.travis.yml | ||
installer.wxs | ||
LICENSE | ||
Makefile | ||
Makefile.builder | ||
README.md | ||
run-tests | ||
setup.cfg | ||
setup.py | ||
version |
Qubes core, version 3
This is development branch of the Qubes OS core. This branch is subject to rebase without warning until further notice.
API documentation is available: https://qubes-core-admin.readthedocs.org/en/latest/.