Marek Marczykowski-Górecki edcaed537a Always use QubesVM objects, instead of AppVM/TemplateVM etc ... Very few calls at client side really needs VM class name. So, even in non-blind mode use just QubesVM class, to avoid strange cases depending on blind mode being enabled or not. Then, have VM class name in 'klass' property. If known at object creation time, cache it, otherwise query qubesd at first access.		2017-10-02 21:12:16 +02:00
..
backup	Merge branch 'devel-6'	2017-07-29 05:28:57 +02:00
tools	tools: restore qvm-start --cdrom and similar options	2017-09-05 08:33:47 +02:00
vm	tests: add DispVM tests	2017-08-12 15:15:19 +02:00
__init__.py	Always use QubesVM objects, instead of AppVM/TemplateVM etc	2017-10-02 21:12:16 +02:00
app.py	Always use QubesVM objects, instead of AppVM/TemplateVM etc	2017-10-02 21:12:16 +02:00
devices.py	devices: client stub for DeviceCollection.update_persistent	2017-09-05 03:59:01 +02:00
errors.py	Improve QubesDaemonNoResponseError error message	2017-08-12 15:15:52 +02:00
events.py	events: fix calling mgmt.Events from VM	2017-06-25 14:01:14 +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	Rename Mgmt API to Admin API: methods names	2017-05-12 19:36:03 +02:00
storage.py	storage: drop 'internal' volume property	2017-07-21 03:10:01 +02:00
tags.py	tags support	2017-06-20 01:34:16 +02:00