libvirtError: virDomainLookupByName() failed

[hdevalence]

While using Qubes, I got a dom0 popup telling me "libvertError: virDomainLookupByName() failed", with the following log data:

----
line: if ret is None:raise libvirtError('virDomainLookupByName() failed', conn=self)
func: lookupByName
line no.: 4066
file: /usr/lib64/python2.7/site-packages/libvirt.py
----
line: self._libvirt_domain = vmm.libvirt_conn.lookupByName(self.name)
func: libvirt_domain
line no.: 750
file: /usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py
----
line: if self.libvirt_domain.isActive():
func: is_running
line no.: 902
file: /usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py
----
line: if not vm.is_running():
func: measure_cpu_usage
line no.: 234
file: /usr/lib64/python2.7/site-packages/qubes/qubes.py
----
line: self.last_measure_time)
func: update_table
line no.: 768
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py

[marmarek]

I assume Qubes R3.1-rc1, right?

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]

I assume Qubes R3.1-rc1, right?

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?

[hdevalence]

Yes, sorry for not specifying.

[hdevalence]

Yes, sorry for not specifying.

[marmarek]

Do you know any specific steps to reproduce this issue? Was it during starting some VM? Or maybe creating, stopping, launching some application? After restoring backup?

[marmarek]

Do you know any specific steps to reproduce this issue? Was it during starting some VM? Or maybe creating, stopping, launching some application? After restoring backup?

[hdevalence]

Nope, unfortunately I've been unable to reproduce it, so I'm afraid it's not a very helpful bug report :(

[hdevalence]

Nope, unfortunately I've been unable to reproduce it, so I'm afraid it's not a very helpful bug report :(

[marmarek]

Above logging finally caught this error. The error code is... None. Looks like a bug in libvirt library/python bindings.

[marmarek]

Above logging finally caught this error. The error code is... None. Looks like a bug in libvirt library/python bindings.

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-3.1.12-1.fc20 has been pushed to the r3.1 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

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-3.1.12-1.fc20 has been pushed to the r3.1 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

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-3.1.12-1.fc20 has been pushed to the r3.1 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

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-3.1.12-1.fc20 has been pushed to the r3.1 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

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-3.0.28-1.fc20 has been pushed to the r3.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

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-3.0.28-1.fc20 has been pushed to the r3.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

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-3.0.28-1.fc20 has been pushed to the r3.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

[marmarek]

Automated announcement from builder-github

The package qubes-core-dom0-3.0.28-1.fc20 has been pushed to the r3.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