[libvirt] Libvirtd not initializing after 65b7d553
Michal Privoznik
mprivozn at redhat.com
Thu Aug 21 09:48:15 UTC 2014
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 at gmail.com> 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. What does 'virsh uri' print out? How about:
virsh -c xen:/// nodeinfo
does it work? Unfortunately I don't run xen myself, but if the problem
persist I can try to install it and see where the problem is.
>>
>> $libvirtd -vvv
>> 2014-08-21 09:31:12.549+0000: 584: info : libvirt version: 1.2.8
>> 2014-08-21 09:31:12.549+0000: 584: warning : virGetHostname:665 :
>> getaddrinfo failed for 'linux-xzc4': Name or service not known
>> 2014-08-21 09:31:12.919+0000: 596: info : libvirt version: 1.2.8
>> 2014-08-21 09:31:12.919+0000: 596: warning : virQEMUCapsInit:976 :
>> Failed to query host NUMA topology, disabling NUMA capabilities
>> 2014-08-21 09:31:12.920+0000: 596: warning : virQEMUCapsInit:980 :
>> Failed to get host CPU
>> 2014-08-21 09:31:12.978+0000: 596: warning : virLXCDriverCapsInit:82 :
>> Failed to query host NUMA topology, disabling NUMA capabilities
>> 2014-08-21 09:31:12.979+0000: 596: warning : umlCapsInit:70 : Failed to
>> query host NUMA topology, disabling NUMA capabilities
>>
>> I have no idea whether this is related to my system or the commit but
>> libvirt master before that commit work perfectly with me.
Michal
More information about the libvir-list
mailing list