[Ovirt-devel] issues creating a vm on stand-alone ovirt node remotely via virt-manager
David Huff
dhuff at redhat.com
Tue Feb 3 20:20:38 UTC 2009
Running: ovirt-node-image-0.97-rc3.el5ovirt.x86_64
I will try to reproduce on upstream fedora node next...
I am able to conect to node via virt manager with
"qemu+tcp://hostname/system"
I run thought the install remotely via virt-manager every thing seems
fine, ie Im connected to the node and can create new networks and stuff,
however when hit finish "ready to begin installation" I get an error....
"
Unable to complete install '<class 'libvirt.libvirtError'> Failed to
start SASL negotiation: -4 (SASL(-4): no mechanism available: No worthy
mechs found)
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 719, in
do_install
guest.conn = libvirt.open(self.connection.get_uri())
File "/usr/lib64/python2.5/site-packages/libvirt.py", line 160, in open
if ret is None:raise libvirtError('virConnectOpen() failed')
libvirtError: Failed to start SASL negotiation: -4 (SASL(-4): no
mechanism available: No worthy mechs found)
"
every thing looks good on the node:
[root at NODE ~]# cat /etc/sasl2/libvirt.conf | grep -v ^#
sasldb_path: /etc/libvirt/passwd.db
mech_list: digest-md5
[root at NODE ~]# cat /etc/libvirt/libvirtd.conf | grep -v ^# | grep -v ^$
listen_tls = 0
listen_tcp = 1
Virt-install with LIBVIRT_DEBUG=1:
[david at sunset src]$ sudo LIBVIRT_DEBUG=1 virt-install
--connect=qemu+tcp://dhcp231-77.rdu.redhat.com/system --hvm --name test
--ram 512 --network bridge:breth1 -f /var/lib/libvirt/images/test.img
-s 10 --cdrom /dev/cdrom
DEBUG: libvirt.c: virInitialize (register drivers)
DEBUG: libvirt.c: virRegisterDriver (registering Test as driver 0)
DEBUG: libvirt.c: virRegisterNetworkDriver (registering Test as network
driver 0)
DEBUG: libvirt.c: virRegisterStorageDriver (registering Test as storage
driver 0)
DEBUG: libvirt.c: virRegisterDriver (registering Xen as driver 1)
DEBUG: libvirt.c: virRegisterDriver (registering OPENVZ as driver 2)
DEBUG: libvirt.c: virRegisterDriver (registering remote as driver 3)
DEBUG: libvirt.c: virRegisterNetworkDriver (registering remote as
network driver 1)
DEBUG: libvirt.c: virRegisterStorageDriver (registering remote as
storage driver 1)
DEBUG: libvirt.c: virRegisterDeviceMonitor (registering remote as device
driver 0)
DEBUG: libvirt.c: virConnectOpen
(name=qemu+tcp://dhcp231-77.rdu.redhat.com/system)
DEBUG: libvirt.c: do_open (name
"qemu+tcp://dhcp231-77.rdu.redhat.com/system" to URI components:
scheme qemu+tcp
opaque (null)
authority (null)
server dhcp231-77.rdu.redhat.com
user (null)
port 0
path /system
)
DEBUG: libvirt.c: do_open (trying driver 0 (Test) ...)
DEBUG: libvirt.c: do_open (driver 0 Test returned DECLINED)
DEBUG: libvirt.c: do_open (trying driver 1 (Xen) ...)
DEBUG: libvirt.c: do_open (driver 1 Xen returned DECLINED)
DEBUG: libvirt.c: do_open (trying driver 2 (OPENVZ) ...)
DEBUG: libvirt.c: do_open (driver 2 OPENVZ returned DECLINED)
DEBUG: libvirt.c: do_open (trying driver 3 (remote) ...)
DEBUG: remote_internal.c: doRemoteOpen (proceeding with name =
qemu:///system)
DEBUG: remote_internal.c: remoteAuthSASL (Client initialize SASL
authentication)
DEBUG: remote_internal.c: remoteAuthSASL (Client start negotiation
mechlist 'DIGEST-MD5')
DEBUG: libvirt.c: do_open (driver 3 remote returned ERROR)
DEBUG: datatypes.c: virUnrefConnect (unref connection 0x22b9e70 1)
DEBUG: datatypes.c: virReleaseConnect (release connection 0x22b9e70)
ERROR Failed to start SASL negotiation: -4 (SASL(-4): no mechanism
available: No worthy mechs found)
Traceback (most recent call last):
File "/usr/sbin/virt-install", line 692, in <module>
main()
File "/usr/sbin/virt-install", line 507, in main
conn = cli.getConnection(options.connect)
File "/usr/lib/python2.5/site-packages/virtinst/cli.py", line 127, in
getConnection
return libvirt.open(connect)
File "/usr/lib64/python2.5/site-packages/libvirt.py", line 160, in open
if ret is None:raise libvirtError('virConnectOpen() failed')
libvirtError: Failed to start SASL negotiation: -4 (SASL(-4): no
mechanism available: No worthy mechs found)
Any suggestions.....
-D
More information about the ovirt-devel
mailing list