qvm-remove sys-whonix error - QubesException: domain is in use "sys-whonix"

[adrelanos]

Qubes OS version:

Qubes R4 with all Qubes testing repositories

Affected TemplateVMs:

Dom0

---

Steps to reproduce the behavior:

Install Qubes R4 with all Qubes testing repositories.

Enable Qubes community templates repository in /etc/yum.repos.d/qubes-templates.repo.

sudo qubes-dom0-update qubes-template-whonix-gw qubes-template-whonix-ws

(Did last command because of #3188.)

sudo qubesctl state.sls qvm.sys-whonix
sudo qubesctl state.sls qvm.sys-whonix
sudo qubesctl state.highstate

qvm-prefs --set sys-whonix netvm sys-firewall

qvm-start sys-whonix

qvm-kill sys-whonix
qvm-remove sys-whonix

Expected behavior:

sys-whonix removed.

Actual behavior:

Error message

QubesException: domain is in use "sys-whonix"

Checked using qvm-ls that sys-whonix is not running, it's halted, whonix-gw and whonix-ws are halted as well and anon-whonix does not exist. No other VM using sys-whonix. I wonder what may be using sys-whonix?

[marmarek]

See journalctl in dom0 for details where exactly it is used. You can't remove it if it's netvm of some other VM, even if not running. You need to change netvm first.

[marmarek]

See journalctl in dom0 for details where exactly it is used. You can't remove it if it's netvm of some other VM, even if not running. You need to change netvm first.

[adrelanos]

Right.

whonix-ws-dvm is using sys-whonix.

And qvm-remove whonix-ws-dvm is also refused, because it is being used by whonix-ws-dvm.default_dispvm.

The required commands are:

qvm-prefs --set whonix-ws-dvm netvm ""
qvm-prefs --set whonix-ws-dvm default_dispvm ""
qvm-remove whonix-ws-dvm
qvm-remove sys-whonix

So this is not a core, but more a documentation or usability issue.

[adrelanos]

Right.

whonix-ws-dvm is using sys-whonix.

And qvm-remove whonix-ws-dvm is also refused, because it is being used by whonix-ws-dvm.default_dispvm.

The required commands are:

qvm-prefs --set whonix-ws-dvm netvm ""
qvm-prefs --set whonix-ws-dvm default_dispvm ""
qvm-remove whonix-ws-dvm
qvm-remove sys-whonix

So this is not a core, but more a documentation or usability issue.

[adubois]

From an end user point of view, whonix-ws-dvm is visible from qvm-ls, so it make sense for him to naturally delete it before it's netvm.
However what is not obvious is qvm-remove whonix-ws-dvm -> Domain in use.
qvm-prefs --set whonix-ws-dvm default_dispvm "" as mentioned above fixed it.

If there is no real dependency (AFAIK this property is a property of the object itself, so should not be a blocker) -> so rather than doc update, should this ticket be tagged as bug in qvm-remove?

otherwise, happy to do the PR for the doc update of qvm-remove instructing that:

• --force should be used because of that qvm-prefs value
• that qvm-prefs should be cleared <-- my preferred solution

[adubois]

From an end user point of view, whonix-ws-dvm is visible from qvm-ls, so it make sense for him to naturally delete it before it's netvm.
However what is not obvious is qvm-remove whonix-ws-dvm -> Domain in use.
qvm-prefs --set whonix-ws-dvm default_dispvm "" as mentioned above fixed it.

If there is no real dependency (AFAIK this property is a property of the object itself, so should not be a blocker) -> so rather than doc update, should this ticket be tagged as bug in qvm-remove?

otherwise, happy to do the PR for the doc update of qvm-remove instructing that:

• --force should be used because of that qvm-prefs value
• that qvm-prefs should be cleared <-- my preferred solution

[adubois]

Created QubesOS/qubes-doc#610
Problem is not limited to qvm-prefs of DVM itself.

[adubois]

Created QubesOS/qubes-doc#610
Problem is not limited to qvm-prefs of DVM itself.

[qubesos-bot]

Automated announcement from builder-github

The package python2-qubesadmin-4.0.19-0.1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package python2-qubesadmin-4.0.19-0.1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package core-admin-client has been pushed to the r4.0 testing repository for the CentOS centos7 template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r4.0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package core-admin-client has been pushed to the r4.0 testing repository for the CentOS centos7 template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r4.0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-core-admin-client_4.0.19-1+deb9u1 has been pushed to the r4.0 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing stretch-testing (or appropriate equivalent for your template version), then use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-core-admin-client_4.0.19-1+deb9u1 has been pushed to the r4.0 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing stretch-testing (or appropriate equivalent for your template version), then use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component core-admin-client (including package python2-qubesadmin-4.0.19-0.1.fc26) has been pushed to the r4.0 testing repository for the Fedora template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r4.0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component core-admin-client (including package python2-qubesadmin-4.0.19-0.1.fc26) has been pushed to the r4.0 testing repository for the Fedora template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r4.0-current-testing

Changes included in this update