Re: [libvirt-users] RHEL 5 libvirt client - QEMU+SSH fails with "unsupported authentication type 2" problem

After a bit more hacking through the code I think this has to do with PolicyKit authentication. The server is currently enabled to do PolicyKit based authentication. And policy kit is disabled or can't be found when building on RHEL4/5 Question: 1. Is Policy Kit available on RHEL4/5 and can the libvirt client be policy kit enabled on the client? 2. Without PolicyKit enabled on the client and server side, is it possible for a non-root user to have Read/Write "qemu:///system" remote access to the server? Sarvi From: Cisco Employee <sarvi@cisco.com<mailto:sarvi@cisco.com>> Date: Tue, 12 Mar 2013 16:17:01 -0700 To: Cisco Employee <sarvi@cisco.com<mailto:sarvi@cisco.com>>, "libvirt-users@redhat.com<mailto:libvirt-users@redhat.com>" <libvirt-users@redhat.com<mailto:libvirt-users@redhat.com>> Subject: Re: [libvirt-users] RHEL 5 libvirt client - QEMU+SSH fails with "unsupported authentication type 2" problem Subject correction From: Cisco Employee <sarvi@cisco.com<mailto:sarvi@cisco.com>> Date: Tue, 12 Mar 2013 21:12:05 +0000 To: "libvirt-users@redhat.com<mailto:libvirt-users@redhat.com>" <libvirt-users@redhat.com<mailto:libvirt-users@redhat.com>> Subject: [libvirt-users] RHEL 5 libvirt client - QEMU+SSH fails with "login authentication type 2" problem Hi, I have RHEL5 libvirt client compiled at ${BSPACE}/usrcisco This client when connecting to a libvirtd/server fails to connect as follows -bash-3.2$ ${BSPACE}/usrcisco/bin/virsh -c qemu+ssh://sarvi@cnh-nehalem-1/system?socket=/var//run/libvirt/libvirt-sock error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 I have the libvirt client compiled and installed as follows PYTHON=${BSPACE}/usrcisco/bin/python LDFLAGS="-L${BSPACE}/libnl-1.1.2/lib/ -L${BSPACE}/device-mapper.1.02.28/lib/ioctl/" CFLAGS="-I${BSPACE}/libnl-1.1.2/include -I${BSPACE}/device-mapper.1.02.28/include/" CPPFLAGS="-I${BSPACE}/device-mapper.1.02.28/include/ -I${BSPACE}/libnl-1.1.2/include" ./configure --prefix=${BSPACE}/usrcisco --enable-static --with-libvirtd=no --with-hal=no --with-python --with-PACKAGE=yes --with-packager=no --with-packager-version=no --with-gnu-ld=no --with-apparmor=no --with-apparmor-mount=no--with-attr=no --with-audit=no --with-avahi=no --with-blkid=no --with-capng=no --with-curl=no --with-dbus=no --with-fuse=no --with-hal=no --with-netcf=no --with-numactl=no --with-openwsman=no --with-pciaccess=no --with-sanlock=no --with-sasl=no --with-selinux=no --with-selinux-mount=no --with-udev=no --with-yajl=no --with-xen=no --with-xen-inotify=no --with-qemu=no --with-uml=no --with-openvz=no--with-vmware=no --with-phyp=no --with-xenapi=no --with-libxl=no --with-vbox=no --with-gnutls=no --without-ssh2 --with-rhel5-api=yes The same library sources when compiled on RHEL6 as above, without specifying the "--with-rhel5-api=yes" compiles AND connect to the same server fine I am looking for pointers as to what the problem could be OR how to trouble shoot the problem. Thanks, Sarvi _______________________________________________ libvirt-users mailing list libvirt-users@redhat.com<mailto:libvirt-users@redhat.com> https://www.redhat.com/mailman/listinfo/libvirt-users