On 02/05/2014 09:27 AM, Sven Kieske wrote:
Well, I just tested this. and I can't connect to virsh with this information. I guess the mentioned user vdsm@rhevh might not be the actual one used in 3.3.2 anymore? (mail is from 2012 and mentions rhev, so..)
well, that's a question for vdsm-devel
or can't libvirt manage multiple authenticated users? Because I registered my own using:
saslpasswd2 -a libvirt USERNAME
which still works.
Am 05.02.2014 09:15, schrieb Sven Kieske:
It's actually step 5 :)
Am 05.02.2014 07:50, schrieb Itamar Heim:
(step 6 explains where the user/password for libvirt/virsh are.
On Wed, Feb 05, 2014 at 02:25:08PM +0100, Itamar Heim wrote:
On 02/05/2014 09:27 AM, Sven Kieske wrote:
Well, I just tested this. and I can't connect to virsh with this information. I guess the mentioned user vdsm@rhevh might not be the actual one used in 3.3.2 anymore? (mail is from 2012 and mentions rhev, so..)
well, that's a question for vdsm-devel
Yes, vdsm@rhevh is a remnant of the past (that can still be seen on the RHEV product). I believe that it can be very easily dropped from there, too. (And `/usr/sbin/saslpasswd2 -p -a libvirt -d vdsm@ovirt` moved to vdsm-tool, for symetry)
vdsm-devel@lists.fedorahosted.org