Skip to content
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

libvirtError: virDomainLookupByName() failed #1537

Closed
hdevalence opened this issue Dec 22, 2015 · 9 comments
Closed

libvirtError: virDomainLookupByName() failed #1537

hdevalence opened this issue Dec 22, 2015 · 9 comments
Assignees
Labels
C: core C: manager/widget P: major Priority: major. Between "default" and "critical" in severity. r3.0-dom0-stable r3.1-dom0-stable

Comments

@hdevalence
Copy link

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
Copy link
Member

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
Copy link
Author

Yes, sorry for not specifying.

@marmarek marmarek added bug C: core C: manager/widget P: major Priority: major. Between "default" and "critical" in severity. labels Dec 22, 2015
@marmarek
Copy link
Member

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
Copy link
Author

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

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Jan 7, 2016
Temporary add some more logging to ease debugging libvirt errors.
Unfortunatelly stack trace doesn't contain actual error.

QubesOS/qubes-issues#1537
@marmarek
Copy link
Member

marmarek commented Feb 5, 2016

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

@marmarek
Copy link
Member

marmarek commented Feb 8, 2016

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
Copy link
Member

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 added a commit to marmarek/old-qubes-core-admin that referenced this issue Feb 29, 2016
s/VIR_INTERNAL_ERROR/VIR_ERR_INTERNAL_ERROR/

Related to QubesOS/qubes-issues#1537
marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Feb 29, 2016
Temporary add some more logging to ease debugging libvirt errors.
Unfortunatelly stack trace doesn't contain actual error.

QubesOS/qubes-issues#1537

(cherry picked from commit 530a794)
marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Feb 29, 2016
In some cases libvirt doesn't report error code at all. This probably
happens in some stage of domain startup/shutdown. Threat this the same
as domain not running.

Fixes QubesOS/qubes-issues#1537

(cherry picked from commit 8ee909f)
marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Feb 29, 2016
s/VIR_INTERNAL_ERROR/VIR_ERR_INTERNAL_ERROR/

Related to QubesOS/qubes-issues#1537

(cherry picked from commit 1e411eb)
@marmarek
Copy link
Member

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 added a commit to marmarek/old-qubes-core-admin that referenced this issue Mar 7, 2016
s/VIR_INTERNAL_ERROR/VIR_ERR_INTERNAL_ERROR/

Related to QubesOS/qubes-issues#1537
Fixes QubesOS/qubes-issues#1804
@marmarek
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: core C: manager/widget P: major Priority: major. Between "default" and "critical" in severity. r3.0-dom0-stable r3.1-dom0-stable
Projects
None yet
Development

No branches or pull requests

2 participants