Hide Forgot
Description of problem: I try install Kaspersky Security for Virtualization 3.0 Light Agent to ovirt node. Some scripts need authentification example ./get_capabilities.sh #!/bin/sh virsh -c qemu:///system capabilities ./get_virsh_version.sh #!/bin/sh virsh -c qemu:///system version ./get_vm_names.sh #!/bin/sh virsh -c qemu:///system list --all --persistent --name Version-Release number of selected component (if applicable): Kaspersky Security for Virtualization 3.0 Light Agent Version: 3.4.44.7177 Can exclude authentification for virsh ?
I have an additional comment. If we do not use oVirt (just KVM only), Kaspersky for VE installs ok. If we have oVirt installed, installation is hanging and we see that Kaspersky script is endlessly trying to authenticate running virsh. We tried root user first, next we tried oVirt authenticated user. The last went further, but still stacked trying to get list of VMs.
I don't think this is an oVirt bug, nevertheless, keeping it open to allow vdsm people to review and maybe help configuring the system for allowing kaspersky to run on the host without breaking vdsm.
If you can configure the product to work with the authentication set up by oVirt it would not cause any harm then (supposing that the product doesn't really break the functionality of VMs). That's the best option. We configure by default a SASL-based authentication with oVirt user over the unix socket interface. You can either use the same user or add yours with your password or enable additional different authentication schemes and transports Refer to https://libvirt.org/auth.html for further details