mossy: > 'awokd' via qubes-users: >> Think I got it working with the -14 templates from unstable. In dom0: >> >> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable >> qubes-template-whonix-gw-14 >> qvm-create sys-whonix-14 --class AppVM --template whonix-gw-14 --label black >> qvm-prefs sys-whonix-14 provides_network True >> >> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable >> qubes-template-whonix-ws-14 >> qvm-features whonix-ws-14 whonix-ws 1 >> qvm-create whonix-ws-dvm-14 --class AppVM --template whonix-ws-14 --label >> green >> qvm-features whonix-ws-14-dvm appmenus-dispvm 1 >> qvm-prefs whonix-ws-dvm-14 template_for_dispvms true >> qvm-prefs whonix-ws-dvm-14 netvm sys-whonix-14 >> qvm-prefs whonix-ws-dvm-14 default_dispvm whonix-ws-dvm-14 >> >> I suspect once these templates get released to stable, the salt command >> will take care of all that for us. >> > > Plus, to ensure updates will work, run the following as well in dom0: > > qvm-tags whonix-gw-14 a whonix-updatevm > qvm-tags whonix-ws-14 a whonix-updatevm > > And thanks for this, I was not aware of qvm-features or some of those > the qvm-prefs flags. Whonix 13 to 14 upgrade worked for me on R4_rc5 > but not final R4.0, but installing fresh templates from unstable did the > trick. > > -m0ssy >
also, if you want whonix updates to go through the new sys-whonix-14, in dom0 edit the file: /etc/qubes-rpc/policy/qubes.UpdatesProxy modify the top line: $tag:whonix-updatevm $default allow,target=sys-whonix to become: $tag:whonix-updatevm $default allow,target=sys-whonix-14 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/065ee013-76df-6866-50a5-f1a123acce9d%40riseup.net. For more options, visit https://groups.google.com/d/optout.
