New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

occasional "qvm-prefs: error: no such property: 'netvm'" #3528

Open
dncohen opened this Issue Feb 4, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@dncohen

dncohen commented Feb 4, 2018

Qubes OS version:

4.0-rc4

Affected TemplateVMs:

fedora-26, I don't believe the problem is related to the template


Steps to reproduce the behavior:

not sure.

It happened to me after connecting a laptop to network in one location, closing the lid allowing laptop to sleep, open lid in another location.

Then, appvms are unable to connect to network, even though sys-net shows that it is connected.

Expected behavior:

I would expect qvm-prefs -s sys-firewall netvm sys-net possibly to solve the problem. Instead it gets an error...

Actual behavior:

[dave@dom0 Desktop]$ qvm-prefs -s sys-firewall netvm sys-net
usage: qvm-prefs [-h] [--verbose] [--quiet] [--help-properties] [--get]
                 [--set] [--default]
                 VMNAME [PROPERTY] [VALUE]
qvm-prefs: error: no such property: 'netvm'

General notes:

Under normal circumstances, I can run qvm-prefs -s sys-firewall netvm sys-net without errors. This problem has happened only a couple of times. When it does, I haven't found a way to recover short of rebooting. (I haven't had 4.0 installed for long. I expect this is a real bug)

Here are some things I've tried (without success):

[dave@dom0 Desktop]$ qvm-prefs -s sys-firewall netvm sys-net
usage: qvm-prefs [-h] [--verbose] [--quiet] [--help-properties] [--get]
                 [--set] [--default]
                 VMNAME [PROPERTY] [VALUE]
qvm-prefs: error: no such property: 'netvm'
[dave@dom0 Desktop]$ qvm-shutdown sys-net
sys-net: Shutdown error: There are other VMs connected to this VM: sys-firewall
[dave@dom0 Desktop]$ qvm-kill sys-net
[dave@dom0 Desktop]$ qvm-start sys-net
[dave@dom0 Desktop]$ qvm-prefs -s sys-firewall netvm sys-net
usage: qvm-prefs [-h] [--verbose] [--quiet] [--help-properties] [--get]
                 [--set] [--default]
                 VMNAME [PROPERTY] [VALUE]
qvm-prefs: error: no such property: 'netvm'

Note that qvm-prefs -g sys-firewall does show netvm in the output.

[dave@dom0 Desktop]$ qvm-prefs -g sys-firewall
autostart             -  True
backup_timestamp      U
debug                 D  False
default_dispvm        D  fedora-26-dvm
default_user          D  user
gateway               D  10.137.0.6
gateway6              D
include_in_backups    D  True
installed_by_rpm      D  False
ip                    D  10.137.0.6
ip6                   D
kernel                D  4.14.13-2
kernelopts            D  nopat
klass                 D  AppVM
label                 -  green
mac                   D  00:16:3E:5E:6C:00
maxmem                D  4000
memory                -  500
name                  -  sys-firewall
netvm                 -  sys-net
[snip]

Related issues:

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Feb 4, 2018

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 5, 2018

Member

I can confirm that when setting netvm fails, sometimes it result in "no such property" error, instead of real reason.

Member

marmarek commented Feb 5, 2018

I can confirm that when setting netvm fails, sometimes it result in "no such property" error, instead of real reason.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 5, 2018

Member

Actual message can be seen using journalctl in dom0.

Member

marmarek commented Feb 5, 2018

Actual message can be seen using journalctl in dom0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment