Qube Manager: Create dvm-templates

[RefinedSoftwareLLC]

Qubes OS version:

R4.0

Affected component(s):

dom0 Qube Manager, DVM-Template Qubes

---

Steps to reproduce the behavior:

Create Qube.
Use console to change Qube into dvm-template.

Expected behavior:

1. qvm-features <vmname> appmenus-dispvm 1 shouldn't exist and is not needed.

• Instead if qvm-prefs <vmname> template_for_dispvms true then show in applications menu under both Disposable: and Template: (not Domain: but alternatively DTemplate: or DVMTemplate:)
• Template: is used for permanent updates but not app use.
• No where else does Qube Manager let you hide qubes from the applications menu. If it did, the feature shouldn't be tied to hiding an individual Disposable VM Template from permanent updates, but instead be a global setting that hides all services, templates, and dvm-templates. One way to implement this would be #4005.

2. "is a Disposable VM Template" setting:
   Open "Qube Manager", right click a qube, "Qube Settings", Tab "Advanced".

• Add this setting as a checkbox: "is a Disposable VM Template" which runs:
• qvm-prefs <vmname> template_for_dispvms true (or false)
• If step 1 isn't implemented then qvm-features <vmname> appmenus-dispvm 1 (or 0)
• Maybe run qvm-prefs <vmname> default_dispvm <vmname> (to itself, not system default even if they are currently the same) then disable changing 'Default DispVM' from itself. This may be needed if it is too confusing for a dvm-template, when not manually instructed to, to spawn DispVM's from another dvm-template.

3. Create "AppVM (Disposable VM Template)" qube:
   Open "Qube Manager", Menu "Qube", "Create new qube".

• Add this option to Type dropdown, "AppVM (Disposable VM Template)" which runs:
• qvm-prefs <vmname> template_for_dispvms true
• If step 1 isn't implemented then qvm-features <vmname> appmenus-dispvm 1
• Maybe run qvm-prefs <vmname> default_dispvm <vmname> (to itself, not system default even if they are currently the same) then disable changing 'Default DispVM' from itself. This may be needed if it is too confusing for a dvm-template, when not manually instructed to, to spawn DispVM's from another dvm-template.

Actual behavior:

See "Steps to reproduce the behavior"

General notes:

---

Related issues:

[RefinedSoftwareLLC]

Displaying both "Disposable:" and "Template:/DVMTemplate:" are needed for easy GUI management of updates to the dvm-template while also able to easily open apps in DispVMs.

[RefinedSoftwareLLC]

Displaying both "Disposable:" and "Template:/DVMTemplate:" are needed for easy GUI management of updates to the dvm-template while also able to easily open apps in DispVMs.