default_fw_netvm - wrong default value (set to None) (should be set to sys-net) (was: qubes-vm-settings settings bug - failed to change NetVM of sys-whonix)

[adrelanos]

failed to change NetVM of sys-whonix using qubes-vm-settings

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

start menu -> sys-whonix -> vm settings -> set NetVM to default (sys-firewall).

(Did last action because of #3189.)

Expected behavior:

sys-whonix's NetVM set to default (sys-firewall).

Actual behavior:

sys-whonix's NetVM setting gets reset to none.

General notes:

Might be related to (or even a follow-up issue?) #3188?

Maybe it is because sys-whonix was already running. But even if sys-whonix was running, changing the NetVM using qubes-vm-settings (started from start menu -> sys-whonix -> vm settings) should be possible?

qvm-shutdown sys-whonix followed by qvm-prefs --set sys-whonix netvm sys-firewall worked for me.

After restarting sys-whonix, to provide further debug output, I set sys-whonix NetVM from default (sys-firewall) to sys-firewall, clicked okay. Restarted qubes-vm-settigns for sys-whonix. Expected: set to sys-friewall. Actual result: set to (none) (current).

Using qubes-vm-settings sys-whonix while sys-whonix has been shutdown (and confirmed using qvm-ls) doesn't help either. The only way to change sys-whonix NetVM setting for me currently is the command line.

---

Related issues:

#2157
#2954

[marmarek]

Does qvm-prefs --default sys-whonix netvm work?

[marmarek]

Does qvm-prefs --default sys-whonix netvm work?

[adrelanos]

Did run qvm-prefs --default sys-whonix netvm. Then did run qvm-prefs sys-whonix netvm. It did output:

None

[adrelanos]

Did run qvm-prefs --default sys-whonix netvm. Then did run qvm-prefs sys-whonix netvm. It did output:

None

[marmarek]

Maybe you have None as default netvm? Check qubes-prefs.

[marmarek]

Maybe you have None as default netvm? Check qubes-prefs.

[adrelanos]

No, qubes-prefs shows default_netvm is set to sys-firewall. (It's a fresh installation of Qubes R4 RC1 with upgrades from Qubes testing repository. Very few changes otherwise.)

[adrelanos]

No, qubes-prefs shows default_netvm is set to sys-firewall. (It's a fresh installation of Qubes R4 RC1 with upgrades from Qubes testing repository. Very few changes otherwise.)

[marmarek]

What is value of default_fw_netvm?

[marmarek]

What is value of default_fw_netvm?

[adrelanos]

None

[adrelanos]

None

[marmarek]

Ok, so here is the problem. When VM itself is a ProxyVM (aka have provides_network=True), it use default_fw_netvm instead of default_netvm. And apparently the former isn't properly set.

[marmarek]

Ok, so here is the problem. When VM itself is a ProxyVM (aka have provides_network=True), it use default_fw_netvm instead of default_netvm. And apparently the former isn't properly set.

[adrelanos]

I.e. not a user error? The Qubes default default_fw_netvm value is set wrong here? (I swear I didn't change the defaults. :)

[adrelanos]

I.e. not a user error? The Qubes default default_fw_netvm value is set wrong here? (I swear I didn't change the defaults. :)

[marmarek]

Yup. Same problem on my system.

[marmarek]

Yup. Same problem on my system.

[qubesos-bot]

Automated announcement from builder-github

The package pykickstart-2.32-4.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 pykickstart-2.32-4.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 pykickstart-2.32-4.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package pykickstart-2.32-4.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update