I use to have virt-manager connecting fine to xen Dom'0/U. Now it seems like virt-manager/libvirt can not connect to xen hypervisor. Although xen USE flag is displayed for information always as ( -xen) (not sure about the meaning of these parenthesis), I can not have it taken into account at build time. Reproducible: Always
For the moement virtmanager return an error message such as: authentication failed Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 1055, in _try_open None], flags) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 102, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: authentication failed
that's not libvirt. That is the security selection for xend. To use virt-manager you need have the xen use flag enables in the libvirt build. The selections for security are dummy, flask and acm. acm is broken. Disable it if enabled. The selction of security must be set correctly in /etc/xen/xend-config.sxp
Sorry for a rather mixed-up initial report. Indeed I'm not blaming virt-manager but libvirt. I started my conf a long time ago with libvirt-0.8.5-r2 for which I had to raise xen flag to have virt-manager connecting to xen. Since I don't use virt-manager very often, I did let portage upgrading it at each stable release. I've recently noticed virt-manager didn't connect to xen anymore, and have found out that the xen USE flag for libvirt which appears as ( -xen) when I do eix -I libvirt can never be actived at build time what ever flags I set in portage.use in this regard. Unfortunately it seems I can not recover to some former stable and 'xen able' version of libvirt. For the record I am running on dummy security module in xend-config.sxp Maybe I've missed up things elsewhere, but at least I hope this little explanation make my issue more understandable. Regards
*** This bug has been marked as a duplicate of bug 379815 ***
