add UpdateVM setting to qubes-vm-settings

[adrelanos]

Qubes OS version:

R4

Affected TemplateVMs:

dom0

---

Steps to reproduce the behavior:

open qubes-vm-settings

Expected behavior:

Should have UpdateVM setting.

Actual behavior:

Does not have UpdateVM setting.

General notes:

Cloning a TempalteVM is a natural step, even an encouraged one. The newly introduced burden in Qubes R4 that one has to edit dom0 configuration after cloning a template is a big usability issue.

NetVM being set to none for TemplateVMs (especially Whonix TemplateVMs) is very confusing for most users. (User question: "How shall I upgrade without a network connection.") Many users will think this is wrong and will manually set a NetVM.

Users who clone their whonix-gw / whonix-ws will very likely have a clearnet leak, will have them upgrades through clearnet rather than Tor which is clearly unexpected. (#3118) It is very non-obvious and difficult to learn that one has to edit dom0 /etc/qubes-rpc/policy/qubes.UpdatesProxy.

Therefore I suggest adding to qubes-vm-settings an UpdateVM setting below its NetVM setting.

I wouldn't call it UpdatesProxy rather than UpdateVM, because UpdateVM makes more sense for users.

---

Related issues:

#3118

[adrelanos]

Should this ticket have the qubes-manager tag?
Dunno if qubes-vm-settings is considered part of QVMM.
I think this is primarily a GUI rather than core issue.

[adrelanos]

Should this ticket have the qubes-manager tag?
Dunno if qubes-vm-settings is considered part of QVMM.
I think this is primarily a GUI rather than core issue.