4:36 a.m.
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
$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.
4:40 a.m.
Ooh forgot to say that this happens on a Xen system
On Thu, Aug 21, 2014 at 12:36 PM, David Kiarie <davidkiarie4(a)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
$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.
4:48 a.m.
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(a)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
4:53 a.m.
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(a)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.
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 :|
4:57 a.m.
$virsh -c xen:/// nodeinfo
CPU model: x86_64
CPU(s): 8
CPU frequency: 3392 MHz
CPU socket(s): 1
Core(s) per socket: 4
Thread(s) per core: 2
NUMA cell(s): 1
Memory size: 8275524 KiB
Works
On Thu, Aug 21, 2014 at 12:53 PM, Daniel P. Berrange
<berrange(a)redhat.com> wrote:
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(a)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.
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 :|
3747
days inactive
3747
days old
4 comments
4 participants
participants (4)
-
Daniel P. Berrange -
David Kiarie -
David kiarie
-
Michal Privoznik