Tomorrow i will try to backtrace.
If can help,when i try to connect via "virsh -c virtualmachinename" i have 2 errors:
"error: failed to connect to the hypervisor"
"error: no connection driver available for virtualmachinename"
But "virsh -c qemu:///system list" is working fine.
I'm on ubuntu 14.04 64bit LTS
On Mar 31, 2015 5:30 PM, Cole Robinson <crobinso@xxxxxxxxxx> wrote:
On 03/31/2015 10:04 AM, Mirko Galimberti wrote:
> Hi guys,
> I’m experiencing this issue:
>
> Traceback (most recent call last):
>
> File "/usr/share/virt-manager/virtManager/engine.py", line 296, in _tick
>
> conn.tick()
>
> File "/usr/share/virt-manager/virtManager/connection.py", line 1311, in tick
>
> self._tick(noStatsUpdate)
>
> File "/usr/share/virt-manager/virtManager/connection.py", line 1320, in _tick
>
> self.hostinfo = self.vmm.getInfo()
>
> File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3344, in getInfo
>
> if ret is None: raise libvirtError ('virNodeGetInfo() failed', conn=self)
>
> libvirtError: Cannot write data: Broken pipe
>
> 2015-03-31 15:51:46,625 (engine:310): Closing connection since libvirtd
> appears to have stopped
>
> 2015-03-31 15:51:48,542 (error:80): dialog message: Error polling connection
> 'qemu:///system': internal error: client socket is closed : Error polling
> connection 'qemu:///system': internal error: client socket is closed
>
>
That usually means libvirt has crashed. So try to catch the libvirt backtrace
and file a bug with your distribution.
>
> Traceback (most recent call last):
>
> File "/usr/share/virt-manager/virtManager/engine.py", line 296, in _tick
>
> conn.tick()
>
> File "/usr/share/virt-manager/virtManager/connection.py", line 1311, in tick
>
> self._tick(noStatsUpdate)
>
> File "/usr/share/virt-manager/virtManager/connection.py", line 1320, in _tick
>
> self.hostinfo = self.vmm.getInfo()
>
> File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3344, in getInfo
>
> if ret is None: raise libvirtError ('virNodeGetInfo() failed', conn=self)
>
> libvirtError: internal error: client socket is closed
>
>
>
> [xcb] Unknown request in queue while dequeuing
>
> [xcb] Most likely this is a multi-threaded client and XInitThreads has not
> been called
>
> [xcb] Aborting, sorry about that.
>
> python: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion
> `!xcb_xlib_unknown_req_in_deq' failed.
>
Never seen that before, could be a virt-manager threading issue or a gtk
issue, tough to say. I'd recommend filing a bug with your distro and let them
help debug it.
- Cole
> Hi guys,
> I’m experiencing this issue:
>
> Traceback (most recent call last):
>
> File "/usr/share/virt-manager/virtManager/engine.py", line 296, in _tick
>
> conn.tick()
>
> File "/usr/share/virt-manager/virtManager/connection.py", line 1311, in tick
>
> self._tick(noStatsUpdate)
>
> File "/usr/share/virt-manager/virtManager/connection.py", line 1320, in _tick
>
> self.hostinfo = self.vmm.getInfo()
>
> File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3344, in getInfo
>
> if ret is None: raise libvirtError ('virNodeGetInfo() failed', conn=self)
>
> libvirtError: Cannot write data: Broken pipe
>
> 2015-03-31 15:51:46,625 (engine:310): Closing connection since libvirtd
> appears to have stopped
>
> 2015-03-31 15:51:48,542 (error:80): dialog message: Error polling connection
> 'qemu:///system': internal error: client socket is closed : Error polling
> connection 'qemu:///system': internal error: client socket is closed
>
>
That usually means libvirt has crashed. So try to catch the libvirt backtrace
and file a bug with your distribution.
>
> Traceback (most recent call last):
>
> File "/usr/share/virt-manager/virtManager/engine.py", line 296, in _tick
>
> conn.tick()
>
> File "/usr/share/virt-manager/virtManager/connection.py", line 1311, in tick
>
> self._tick(noStatsUpdate)
>
> File "/usr/share/virt-manager/virtManager/connection.py", line 1320, in _tick
>
> self.hostinfo = self.vmm.getInfo()
>
> File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3344, in getInfo
>
> if ret is None: raise libvirtError ('virNodeGetInfo() failed', conn=self)
>
> libvirtError: internal error: client socket is closed
>
>
>
> [xcb] Unknown request in queue while dequeuing
>
> [xcb] Most likely this is a multi-threaded client and XInitThreads has not
> been called
>
> [xcb] Aborting, sorry about that.
>
> python: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion
> `!xcb_xlib_unknown_req_in_deq' failed.
>
Never seen that before, could be a virt-manager threading issue or a gtk
issue, tough to say. I'd recommend filing a bug with your distro and let them
help debug it.
- Cole
_______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
