Hi, I've hit following traceback:
Traceback (most recent call last):
File "/usr/bin/lnst-ctl", line 24, in <module>
from lnst.Controller.NetTestController import NetTestController, NetTestError
File "/usr/lib/python2.7/site-packages/lnst/Controller/NetTestController.py",
line 24, in <module>
from lnst.Common.VirtUtils import VirtNetCtl, VirtDomainCtl
File "/usr/lib/python2.7/site-packages/lnst/Common/VirtUtils.py", line 23, in
<module>
_libvirt_conn = libvirt.open(None)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 236, in open
if ret is None:raise libvirtError('virConnectOpen() failed')
libvirt.libvirtError: Failed to connect socket to
'/var/run/libvirt/libvirt-sock': No such file or directory
This leads me to the question whether we should implement this
differently in on-demand way, e.g. set _libvirt_conn to None and have a
function that initiates this connection once we know that the guests
will be used. Currently we're relying on virtualization software
installed. In case the pool consists only from bare metal machines this
is not guaranteed.
Any opinion on this?
-Jan