Marek Marczykowski-Górecki 759fafea63 tools/qvm-create: properly create template-based StandaloneVM ... By definition StandaloneVM is not linked to the template. Creating one from a template is a clone operation. It's already possible using qvm-clone tool, but it's logical to do that using qvm-create tool too. This was the case in R3.2 too. While adding this special case, skip cloning private volume, to preserve behaviour of TemplateBaseVMs which do not inherit private volume either. Fixes QubesOS/qubes-issues#3793		2018-10-18 03:24:15 +02:00
..
backup	tests: dom0 backup restore, both v3 and v4	2018-02-14 04:28:23 +01:00
tools	tools/qvm-create: properly create template-based StandaloneVM	2018-10-18 03:24:15 +02:00
vm	Merge remote-tracking branch 'qubesos/pr/51'	2018-01-15 03:23:54 +01:00
__init__.py	Always use QubesVM objects, instead of AppVM/TemplateVM etc	2017-10-02 21:12:16 +02:00
app.py	tests: fix tests after dropping unnecessary admin.label.List call	2017-12-05 22:56:37 +01:00
devices.py	devices: drop DeviceInfo.options	2018-09-18 21:54:51 +02:00
errors.py	Improve QubesDaemonNoResponseError error message	2017-08-12 15:15:52 +02:00
events.py	events: deserialize DeviceInfo class in device-* events	2018-09-27 14:52:53 +02:00
features.py	features: serialize True as '1'	2017-07-28 13:56:05 +02:00
firewall.py	firewall: drop GetPolicy/SetPolicy calls	2017-07-05 14:16:30 +02:00
label.py	base: make WrapperObjectsCollection behave like a dict	2018-01-12 05:29:40 +01:00
storage.py	base: make WrapperObjectsCollection behave like a dict	2018-01-12 05:29:40 +01:00
tags.py	tags support	2017-06-20 01:34:16 +02:00
utils.py	Name change of vm dependencies helper function	2018-07-19 21:24:28 +02:00