On Thu, Aug 21, 2014 at 11:48:15AM +0200, Michal Privoznik wrote: > On 21.08.2014 11:40, David kiarie wrote: > >Ooh forgot to say that this happens on a Xen system > > > >On Thu, Aug 21, 2014 at 12:36 PM, David Kiarie <davidkiarie4@xxxxxxxxx> wrote: > >> > >>For some I cannot be able able to use virsh after 65b7d553. > >> > >>Libvirtd initializes without errors but I guess something is going > >>unreported > >> > >>$libvirtd -d > >> 2014-08-21 09:29:22.748+0000: 468: info : libvirt version: 1.2.8 > >> 2014-08-21 09:29:22.748+0000: 468: warning : virGetHostname:665 : > >> getaddrinfo failed for 'linux-xzc4': Name or service not known > >> > >>$ps aux | grep libvirtd > >> root 471 0.0 0.1 375692 10268 ? SLl 12:29 0:00 > >> libvirtd -d > >> root 570 0.0 0.0 10520 928 pts/0 S+ 12:30 0:00 grep > >> --color=auto libvirtd > >> > >>$virsh nodeinfo > >> error: failed to connect to the hypervisor > >> error: no valid connection > >> error: An error occurred, but the cause is unknown > > Since vbox registers first, you may be connecting to different URI than you > think. Hmm, that change isn't good. We shouldn't change the priority ordering of the hypervisor drivers - when I suggested reordering vbox driver, I only meant that the storage & network driver parts of vbox be placed first - not that the hypervisor part should be raised in priority. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list