On Thu, Sep 19, 2013 at 04:48:29PM -0300, Fernando Lozano wrote:
> I tried only digest-md5. I guess most people would use either that
> or Kerberos.
>
> Is the "authentication type 1" from the error message a libvirtd
> authentication type or a SASL one?
It's from libvirt and means SASL auth is n
Hi,
My first tests using virsh from
http://teuf.fedorapeople.org/virt-viewer-msi/ were based on the 64-bit
(x86_64) binaries. I'll try the 32-bit binaries and report on the
results.
The 32-bit binaries needed the same DLLs (of course the 32-bit ones) and
gave the same results: virsh works with
Hi Marc,
C:\Program Files\VirtViewer\bin>virsh -c qemu+tcp://kvmhost/system
error: failed to connect to the hypervisor
error: authentication failed: unsupported authentication type 1
It looks like the windows port can't do SASL auth over TCP. So I changed
libvirtd.conf to allow unauthenticated c
Hi,
My first tests using virsh from
http://teuf.fedorapeople.org/virt-viewer-msi/ were based on the 64-bit
(x86_64) binaries. I'll try the 32-bit binaries and report on the results.
After having success with a few comands using virsh, I decided to try
virt-viewer.
It reported missing libss
Hi Christophe,
If someone provides newer windows binaries -- which aren't missing
dlls, like the ones at http://teuf.fedorapeople.org/virt-viewer-msi/
-- I will test then.
I gave you links to RPMs containing the missing dlls (rpm2cpio foo.dll
| cpio -id will unpack them on linux) in
https://ww
- Original Message -
> Hi Christophe,
> >> If someone provides newer windows binaries -- which aren't missing
> >> dlls, like the ones at http://teuf.fedorapeople.org/virt-viewer-msi/
> >> -- I will test then.
> > I gave you links to RPMs containing the missing dlls (rpm2cpio foo.dll
> >
