Support libvirt per-driver daemons

[qiankehan]

Since libvirt 5.6, several split daemons are created to replace the functions of libvirtd:
Primary virt drivers:

  virtlibxld
  virtlxcd
  virtqemud
  virtvboxd
  virtvzd

Secondary drivers:

  virtinterfaced
  virtnetworkd
  virtnodedevd
  virtnwfilterd
  virtsecretd
  virtstoraged

Finally to support IP connectivity, and also the legacy lbivirtd UNIX domain socket (for the old libvirt remote driver SSH tunnelling):

  virtproxyd

BTW, the configuration files and daemons sockets are changed accordingly. Reference: Libvirt patches: https://www.redhat.com/archives/libvir-list/2019-July/msg01311.html

[chunfuwen]

@balamuruhans @sathnaga @kylazhang @dzhengfy

[chunfuwen]

files,which may touch the changes under avocado-vt repository: (base) [root@localhost avocado-vt]# find . -name '*.py' -exec grep 'libvirtd' {} \; -print|grep -i '.py' ./avocado_vt/test.py ./virttest/libvirt_installer.py ./virttest/libvirt_remote.py ./virttest/utils_disk.py ./virttest/utils_libvirtd.py ./virttest/utils_sasl.py ./virttest/utils_test/init.py ./virttest/utils_test/libvirt.py ./virttest/virt_admin.py ./virttest/env_process.py ./virttest/libvirt_vm.py ./virttest/test_setup.py ./virttest/utils_config.py ./virttest/utils_conn.py ./virttest/virsh.py

[chunfuwen]

Here there are two kinds of things addressed here: 1)Start different daemons separately, currently existed libvirtd is one good example,which is defined as class in utils_libvirtd.py 2)Create Config file matched with separate daemon,currently existed LibvirtdConfig is one good example ,which is defined as class in utils_config.py Therefore, the path to address those two issues could be create separate daemon and config class by simulating currently existed good examples.

[sathnaga]

Therefore, the path to address those two issues could be create separate daemon and config class by simulating currently existed good examples.

@chunfuwen yep, good approach, have any one started coding it?

[sathnaga]

this will be a bottle neck for future test executions, and one more thing to consider is to retain the backward compatibility... for older distributions...

[sathnaga]

If no one started implementing or planning to implement yet, I can contribute...

[sathnaga]

@qiankehan @chunfuwen ping