qubes-vm-settings fails for restored VMs

[kulinacs]

Qubes OS version (e.g., R3.2):

R4.0-rc1

Expected behavior:

qubes-vm-settings loads for restored VMs

Actual behavior:

Error causes failure

Steps to reproduce the behavior:

• Restore VMs from backup (in my case, R3.2)
• Run qubes-vm-settings on a restored vm

General notes:

Fix

BE CAREFUL EDITING /var/lib/qubes/qubes.xml by hand!

Replace

<features>
  <feature name="services.meminfo-writer">1</feature>
</features>

with:

<features/>

for all restored VMs in /var/lib/qubes/qubes.xml and restart.

Error

TypeError: setChecked(self, bool): argument 1 has unexpected type 'str'
at line 9
of file /usr/bin/qubes-vm-settings.

---

line: self.vm.features.get('services.meminfo-writer', True))
func: init_advanced_tab
line no.: 454
file: /usr/lib/python3.5/site-packages/qubesmanager/settings.py

---

line: self.init_advanced_tab()
func: init
line no.: 89
file: /usr/lib/python3.5/site-packages/qubesmanager/settings.py

---

line: settings_window = VMSettingsWindow(vm, qapp, args.tab)
func: main
line no.: 999
file: /usr/lib/python3.5/site-packages/qubesmanager/settings.py

---

line: load_entry_point('qubesmanager==4.0.4', 'console_scripts', 'qubes-vm-settings')()
func:
line no.: 9
file: /usr/bin/qubes-vm-settings

---

Related issues:

[marmarek]

About workaround - use qvm-features tool for this.

[marmarek]

About workaround - use qvm-features tool for this.

[ktmdan]

Quick workaround for a lot of vms

for qube in `qvm-ls --format simple | cut -f1 -d ' '`; do qvm-features $qube services.meminfo-writer -D; done

[ktmdan]

Quick workaround for a lot of vms

for qube in `qvm-ls --format simple | cut -f1 -d ' '`; do qvm-features $qube services.meminfo-writer -D; done

[marmarek]

On Mon, Oct 02, 2017 at 08:15:30AM -0700, Dan wrote: Quick workaround for a lot of vms for qube in `qvm-ls --format simple | cut -f1 -d ' '`; do qvm-features $qube services.meminfo-writer -D; done

Pro tip: `qvm-ls -O name` for just VM names (and a "NAME" header...).

…

-- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

[marmarek]

On Mon, Oct 02, 2017 at 08:15:30AM -0700, Dan wrote: Quick workaround for a lot of vms for qube in `qvm-ls --format simple | cut -f1 -d ' '`; do qvm-features $qube services.meminfo-writer -D; done

Pro tip: `qvm-ls -O name` for just VM names (and a "NAME" header...).

…

-- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

[qubesos-bot]

Automated announcement from builder-github

The package qubes-manager-4.0.7-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 qubes-manager-4.0.7-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 qubes-manager-4.0.8-1.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 qubes-manager-4.0.8-1.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