Automatically adding anon-vm
tag to
Qubes ticket:
(Source code: GitHub - QubesOS/qubes-core-admin-addon-whonix)
Untested.
This might work.
sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable qubes-core-admin-addon-whonix
Automatically adding anon-vm
tag to
Qubes ticket:
(Source code: GitHub - QubesOS/qubes-core-admin-addon-whonix)
Untested.
This might work.
sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable qubes-core-admin-addon-whonix
Just for information, this was raised in
https://phabricator.whonix.org/T534#15388
After installing qubes-core-admin-addon-whonix
, I created a new (fifth) anon VM that shows in sdwdate-gui-qubes
without adding a tag in dom0. Great.
But the output of qvm-tags anon-test
(latest anon-vm) is still showing only created-by-dom0
.
I’m missing something.
Creating a new vm using the GUI with
template := whonix-ws-14
netvm := sys-whonix (whonix 14 based)
doesn’t get the anon-vm tag applied automatically. Was that the intention / is there a specific VM creation procedure I should have followed?
According to /usr/share/doc/qubes-core-admin-addon-whonix/README,md, the template has to be given the feature whonix-ws = 1:
qvm-features whonix-ws-14 whonix-ws 1
Afterwards, new VMs based whonix-ws-14 do get the anon-vm tag and have dispvm set to whonix-ws-14-dvm.
In addition, VMs created using qvm-create
get netvm set to sys-whonix. Those created from the GUI get whatever netvm was set in the GUI.
2 posts were split to a new topic: Whonix 14 release blockers - status of Whonix 14 development
Related: