[ovirt-users] Virsh

[Koen Vanoppen]

That works...

[root at mercury1 ~]# virsh -r list
 Id    Name                           State
----------------------------------------------------
 3     elear01prod                running
...

[root at mercury1 ~]# ps aux | grep libvirt
root      6137  1.6  0.0 1283180 23636 ?       Ssl  Feb16 325:14
/usr/sbin/libvirtd --listen
root     48600  0.0  0.0 112652  1008 pts/7    S+   11:37   0:00 grep
--color=auto libvirt


On 2 March 2017 at 10:00, Arman Khalatyan <arm2arm at gmail.com> wrote:

> what about:
> virsh -r list
> ps aux | grep libvirt
>
>
> On Thu, Mar 2, 2017 at 7:38 AM, Koen Vanoppen <vanoppen.koen at gmail.com>
> wrote:
>
>> I wasn't finished... :-)
>> Dear all,
>>
>> I know I did it before.... But for the moment I can't connect to virsh...
>> [root at mercury1 ~]# saslpasswd2 -a libvirt koen
>> Password:
>> Again (for verification):
>> [root at mercury1 ~]# virsh
>> Welcome to virsh, the virtualization interactive terminal.
>>
>> Type:  'help' for help with commands
>>        'quit' to quit
>>
>> virsh # pool-list
>> Please enter your authentication name: koen
>> Please enter your password:
>> error: failed to connect to the hypervisor
>> error: no valid connection
>> error: authentication failed: authentication failed
>>
>> So, i created a new username (I had the same error when I tried to set a
>> password for "admin" user), gave the user a password, but still, I can't
>> connect... What am I missing?
>> We are running on ovirt 4. Hypervisors are running.
>> These are the version of qem:
>> [root at mercury1 ~]# rpm -qa | grep -i qemu
>> qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64
>> qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64
>> qemu-img-ev-2.3.0-31.el7.16.1.x86_64
>> qemu-kvm-tools-ev-2.3.0-31.el7.16.1.x86_64
>> ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch
>> libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64
>> [root at mercury1 ~]# rpm -qa | grep -i libvirt
>> libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.5.x86_64
>> libvirt-daemon-driver-storage-1.2.17-13.el7_2.5.x86_64
>> libvirt-client-1.2.17-13.el7_2.5.x86_64
>> libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.5.x86_64
>> libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.5.x86_64
>> libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64
>> libvirt-daemon-1.2.17-13.el7_2.5.x86_64
>> libvirt-python-1.2.17-2.el7.x86_64
>> libvirt-lock-sanlock-1.2.17-13.el7_2.5.x86_64
>> libvirt-daemon-driver-interface-1.2.17-13.el7_2.5.x86_64
>> libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64
>> libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64
>> libvirt-daemon-driver-secret-1.2.17-13.el7_2.5.x86_64
>>
>> Anybody any idea?
>>
>> Thanks in advance.
>>
>> Kind regards,
>>
>> Koen
>>
>>
>> On 2 March 2017 at 07:37, Koen Vanoppen <vanoppen.koen at gmail.com> wrote:
>>
>>> Dear all,
>>>
>>> I know I did it before.... But for the moment I can't connect to virsh...
>>> [root at mercury1 ~]# saslpasswd2 -a libvirt koen
>>> Password:
>>> Again (for verification):
>>> [root at mercury1 ~]# virsh
>>> Welcome to virsh, the virtualization interactive terminal.
>>>
>>> Type:  'help' for help with commands
>>>        'quit' to quit
>>>
>>> virsh # pool-list
>>> Please enter your authentication name: koen
>>> Please enter your password:
>>> error: failed to connect to the hypervisor
>>> error: no valid connection
>>> error: authentication failed: authentication failed
>>>
>>> So, i created a new username (I had the same error when I tried to set a
>>> password for "admin" user), gave the user a password, but still, I can't
>>> connect... What am I missing?
>>> We are running on ovirt 4. Hypervisors are running.
>>> These are the version of qemu
>>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170302/24714b0b/attachment.html>