Comment 9 for bug 1999445

Yesterday I compared both a CentOS and a Debian platform regarding libvirt packages installed into the host.

<TL;DR> Conclusion: There is no need to add any extra libvirt package to a Debian platform.

The confusion came from the fact the on CentOS, a meta package "libvirt" was installed and would install all the other libvirt related packages.
Differently, on Debian all packages were separated so we can install only what is really required for it to work as peer our requirements.
Checking on CentOS, we do not have any ENABLED systemd service related to libvirt.
The daemons are started from within the libvirt container (in chroot) that has privileged mode enabled

On CentOS, even after the application is applied, libvirt container started and running, there is nos systemd service required on the host. Again, it runs inside the container on privileged mode. So the only change now is that there is a libvirtd.pid, created when the container started the daemon.
The conclusion then is that on Debian there is no need to add any further libvirt packages to the host, since all the required packages are already running inside the container.
Sanity tests showed that, on Debian, libivirt container started successfully and VMs were launched and pingable.

Also, with the already merged change to the application, the device /dev/kvm was checked with the correct user/group and access.

The second code change will be abandoned and this Launchpad can be closed now.