Frédéric Grelot | 21 Jul 12:01 2012
Picon

[fedora-virt] qemu updated to 1.1 and libvirt to 0.9.13 : nothing works!

Hi all, 

I updated my vm server yesterday with the latest packages from virt-preview : qemu 1.1, libvirt 0.9.13, and
virt-manager 0.9.3
Unfortunately, I couldn't connect using virsh anymore (nor using virt-manager). I had the same problem a
few days earlier when I forced installation of those packages from rawhide for testing purposes, but I
hadn't time to report.
yesterday, I increased the log verbosity, so here it is :
#virsh -d 4 list
erreur :Failed to reconnect to the hypervisor
erreur :pas de connexion valide
erreur :no connection driver available for No connection for URI qemu:///system
erreur :Failed to reconnect to the hypervisor

in /var/log/messages :
with loglevel = 2 :
(libvirtd startup, nothing especially wrong)
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: info : libvirt version:
0.9.13, package: 2.fc17 (Fedora Project, 2012-07-20-10:09:35, x86-01.phx2.fedoraproject.org)
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning :
virDriverLoadModule:72 : Module
/usr/lib64/libvirt/connection-driver/libvirt_driver_network.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning :
virDriverLoadModule:72 : Module
/usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning :
virDriverLoadModule:72 : Module
/usr/lib64/libvirt/connection-driver/libvirt_driver_nodedev.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning :
virDriverLoadModule:72 : Module
/usr/lib64/libvirt/connection-driver/libvirt_driver_secret.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning :
virDriverLoadModule:72 : Module
/usr/lib64/libvirt/connection-driver/libvirt_driver_nwfilter.so not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning :
virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so
not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning :
virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so
not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning :
virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_uml.so
not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning :
virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_xen.so
not accessible
Jul 20 21:12:14 vmserver libvirtd[3387]: 2012-07-20 19:12:14.583+0000: 3387: warning :
virDriverLoadModule:72 : Module /usr/lib64/libvirt/connection-driver/libvirt_driver_libxl.so
not accessible
Jul 20 21:12:14 vmserver libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: Aucun fichier ou
dossier de ce type
(when I try virsh list)
Jul 20 21:12:21 vmserver libvirtd[3387]: 2012-07-20 19:12:21.662+0000: 3395: error : do_open:1174 : no
connection driver available for No connection for URI (null)
Jul 20 21:12:21 vmserver libvirtd[3387]: 2012-07-20 19:12:21.663+0000: 3387: error :
virNetSocketReadWire:1003 : End of file while reading data: Erreur d'entrée/sortie
Jul 20 21:12:21 vmserver libvirtd[3387]: 2012-07-20 19:12:21.666+0000: 3393: error : do_open:1174 : no
connection driver available for No connection for URI (null)
Jul 20 21:12:21 vmserver libvirtd[3387]: 2012-07-20 19:12:21.667+0000: 3387: error :
virNetSocketReadWire:1003 : End of file while reading data: Erreur d'entrée/sortie

I also have a log with loglevel=1, but it is far longer... However, the section corresponding to the virsh
list is short :
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.546+0000: 3140: info :
remoteDispatchAuthList:2193 : Bypass polkit auth for privileged client pid:3153,uid:0
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.550+0000: 3137: error : do_open:1174 : no
connection driver available for No connection for URI qemu:///system
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.551+0000: 3133: error :
virNetSocketReadWire:1003 : End of file while reading data: Erreur d'entrée/sortie
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.553+0000: 3143: info :
remoteDispatchAuthList:2193 : Bypass polkit auth for privileged client pid:3153,uid:0
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.556+0000: 3140: error : do_open:1174 : no
connection driver available for No connection for URI qemu:///system
Jul 20 21:03:05 vmserver libvirtd[3133]: 2012-07-20 19:03:05.557+0000: 3133: error :
virNetSocketReadWire:1003 : End of file while reading data: Erreur d'entrée/sortie

I'm not sure why in this latest log, the URI is qemu:///system while it seems to be "null" in the first one...
However, none of them worked.

Precision : virsh list was entered in root. By the way, virt-manager (not working either, but I haven't kept
the logs) was run by a non-privileged user which is asked a password when connecting.

Currently, I managed to go back to a working state by yum removing qemu*, libvirt* and then "yum install
--disablerepo=fedora-virt-preview qemu* libvirt* virt-*" (or similar : I did not really installed all
subpackages of libvirt* and virt-*). But if you were to push those packages to the main repos, that'll
become problematic...

If necessary, it is quite easy to go back to the non-working state (yum update actually...), so tell me if
it's needed for tests.

Frederic.

_______________________________________________
virt mailing list
virt <at> lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/virt

Gmane