Bug 812933 - virt-manager connection to libvirtd 0.9.8 using qemu+tcp stalls after parsing storage pools
Summary: virt-manager connection to libvirtd 0.9.8 using qemu+tcp stalls after parsing...
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 17
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2012-04-16 15:35 UTC by Rouven Sacha
Modified: 2012-04-25 18:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-04-25 18:00:07 UTC
Type: Bug

Attachments (Terms of Use)
virt-manager debug output (8.66 KB, text/plain)
2012-04-16 15:35 UTC, Rouven Sacha
no flags Details

Description Rouven Sacha 2012-04-16 15:35:25 UTC
Created attachment 577744 [details]
virt-manager debug output

Description of problem:

virt-manager drops the connection to a libvirtd when using qemu+tcp. virsh console connects fine.

Version-Release number of selected component (if applicable):



Server (Debian squeeze-backports):

libvirt-bin                             0.9.8-2~bpo60+2 

How reproducible:

all the time

Steps to Reproduce:

1. Configure a new connection in virt-manager using qemu+tcp as a protocol. 
2. Connect and authenticate

Actual results:

The server connection stalls with the "Connecting" status - virt-manager switches the connection back to "disconnected" in the UI without having connected to the libvirtd after two minutes 

Expected results:

See the running VMs on the libvirtd server

Additional info:

Starting virt-manager with the --debug option one can see that vm connects correctly but the fails after trying to get the details about the storage pools (see attachment for log)

virsh itself connects fine and can list the storage pools without problems:

[rsacha@novalima ~]$ virsh -c qemu+tcp://
Please enter your authentication name: rsacha
Please enter your password: 
Willkommen bei virsh, dem interaktiven Virtualisierungsterminal.

Tippen Sie:  'help' für eine Hilfe zu den Befehlen
       'quit' zum Beenden

virsh # pool-info vg1
Name:           vg1
UUID:           33703cf0-635f-6206-0a67-7cfb5c6c865b
Status:         laufend
Persistent:     yes
Automatischer Start: yes
Kapazität:     820,20 GB
Zuordnung:      219,52 GB
Verfügbar:     600,69 GB

virsh # pool-info vg2
Name:           vg2
UUID:           25fdd5e3-3a85-5183-a42f-62e5c2ce825b
Status:         laufend
Persistent:     yes
Automatischer Start: yes
Kapazität:     2,27 TB
Zuordnung:      1,71 TB
Verfügbar:     576,66 GB

virsh # pool-info default
Name:           default
UUID:           40785e08-681e-14e2-3ab6-deadec446830
Status:         laufend
Persistent:     yes
Automatischer Start: yes
Kapazität:     984,31 GB
Zuordnung:      618,23 GB
Verfügbar:     366,08 GB

virsh # pool-list
Name                 Status     Automatischer Start
default              Aktiv      yes       
vg1                  Aktiv      yes       
vg2                  Aktiv      yes

Comment 1 Cole Robinson 2012-04-16 20:03:31 UTC
virt-manager URI is qemu+tcp:// Does adding the port there make any difference? Try virt-manager --debug --connect qemu+tcp://

And once connected with virsh, try a pool-refresh vg1, since that is the first call failing with virt-manager

Beginning of the output failures

2012-04-16 16:45:06,367 (connection:1315): Couldn't fetch active pool 'vg1'
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1312, in _poll_helper
    check_obj(name, True)
  File "/usr/share/virt-manager/virtManager/connection.py", line 1291, in check_obj
    current[key] = build_class(self, obj, key, is_active)
  File "/usr/share/virt-manager/virtManager/storagepool.py", line 38, in __init__
  File "/usr/share/virt-manager/virtManager/storagepool.py", line 115, in refresh
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2116, in refresh
    if ret == -1: raise libvirtError ('virStoragePoolRefresh() failed', pool=self)
libvirtError: End of file while reading data: Eingabe-/Ausgabefehler
2012-04-16 16:45:06,375 (connection:1287): Could not fetch pool 'vg2': End of file while reading data: Eingabe-/Ausgabefehler
2012-04-16 16:45:06,377 (connection:1287): Could not fetch pool 'default': End of file while reading data: Eingabe-/Ausgabefehler
2012-04-16 16:45:06,380 (cli:83): Uncaught exception:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/baseclass.py", line 33, in _safe_wrapper
    return func(*args)
  File "/usr/share/virt-manager/virtManager/connection.py", line 1241, in _open_notify
  File "/usr/share/virt-manager/virtManager/connection.py", line 1468, in tick
  File "/usr/share/virt-manager/virtManager/connection.py", line 1489, in _tick
    newInterfaces, self.interfaces) = self._update_interfaces()
  File "/usr/share/virt-manager/virtManager/connection.py", line 1363, in _update_interfaces
    lookup_func, build_class)
  File "/usr/share/virt-manager/virtManager/connection.py", line 1269, in _poll_helper
    if not check_support():
  File "/usr/share/virt-manager/virtManager/connection.py", line 549, in is_interface_capable
  File "/usr/lib/python2.7/site-packages/virtinst/support.py", line 577, in check_conn_support
    return _check_support(conn, feature, conn)
  File "/usr/lib/python2.7/site-packages/virtinst/support.py", line 445, in _check_support
  File "/usr/lib/python2.7/site-packages/virtinst/support.py", line 358, in _daemon_lib_ver
    return conn.getLibVersion()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3106, in getLibVersion
    if ret == -1: raise libvirtError ('virConnectGetLibVersion() failed', conn=self)
libvirtError: End of file while reading data: Eingabe-/Ausgabefehler

Comment 2 Rouven Sacha 2012-04-17 08:02:41 UTC

you're right. If i do a a "virsh# pool-refresh vg1" the virsh console just hangs for like three minutes and then prints:

virsh # pool-refresh vg1
Pool vg1 aktualisiert

virsh # 

If I issue that command a second time it takes the same amount of time.

Adding the port with virt-manager doesn't help. It disconnects after ~1 minute spewing the same errors on the console.



Comment 3 Cole Robinson 2012-04-17 15:04:12 UTC
What distro and kernel are you on? Someone reported a similar issue with alt linux 3.3 kernel and lvm pools.


Doing 'sudo LIBVIRT_DEBUG=1 libvirtd' and reproducing the virsh hang in another terminal will show lot's of output that might pinpoint the issue.

Comment 4 Rouven Sacha 2012-04-18 11:50:32 UTC
Hi - you're right again and I apologize:

I have the same issue when i execute virsh pool-refresh vg1 on the libvirtd host itself - so virsh on fedora17 is not to blame ...

The system is a Debian squeeze box with kernel, kvm-qemu and libvirt from squeeze-backports:

linux-image: 3.2.0-0.bpo.1
qemu-kvm: 1.0+dfsg-8~bpo60+1
libvirt-bin: 0.9.8-2~bpo60+2

if i find the time i am going to post some debug results here.

Thanks for helping out!


Comment 5 Cole Robinson 2012-04-25 18:00:07 UTC
Okay, closing this bug. Please follow up with debian.

Note You need to log in before you can comment on or make changes to this bug.