Bug 432385
| Summary: | virConnectOpenReadOnly() failed could not use Xen hypervisor entry | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Felix Schwarz <felix.schwarz> |
| Component: | libvirt | Assignee: | Daniel Veillard <veillard> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | berrange |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-07-19 11:52:14 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
With some of the Fedora 8 updates, this started working again. |
Description of problem: As a normal user, I can't use libvirt to connect to my local Xen host (same machine). vm_applet 0.1.2 says "Failed to connect to the hypervisor". $ virsh list failed to find libvirt_proxy error: failed to connect to the hypervisor virt-manager gives this error message as soon as I try to connect to the local Xen host: Unable to open connection to hypervisor URI 'xen:///': <class 'libvirt.libvirtError'> virConnectOpenReadOnly() failed could not use Xen hypervisor entry /tmp/livirt_proxy_conn Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 310, in _open_thread self.vmm = libvirt.openReadOnly(self.uri) File "/usr/lib64/python2.5/site-packages/libvirt.py", line 144, in openReadOnly if ret is None:raise libvirtError('virConnectOpenReadOnly() failed') libvirtError: virConnectOpenReadOnly() failed could not use Xen hypervisor entry /tmp/livirt_proxy_conn Everything works as root, so there seems to be a configuration problem. Xen guests can be started and stopped (as root). This used to work on early F8 days but some weeks ago, this changed. # service libvirtd status libvirtd (PID 2272) wird ausgeführt... # service xend status xenstored (PID 2367) wird ausgeführt... blktapctrl (PID 2369) wird ausgeführt... xenconsoled (PID 2372) wird ausgeführt... xend (PID 2378) wird ausgeführt... [ OK ] (sorry, was not able to switch languages: "wird ausgeführt" means as much as "executing"