This bug was fixed in the package libvirt - 7.4.0-0ubuntu3
---
libvirt (7.4.0-0ubuntu3) impish; urgency=medium
* d/t/smoke-lxc: skip if cgroup v1 are present (systemd 248
was not enough)
libvirt (7.4.0-0ubuntu2) impish; urgency=medium
* d/t/smoke-lxc: skip before systemd
Em quinta-feira, 17 de junho de 2021, às 10:07:39 -03, Christian Ehrhardt
escreveu:
> The dependencies already are (and would stay)
> iptables (>= 1.8.1-1) | firewalld
> from Package: libvirt-daemon-system.
> This is very much the same in Debian where we have kept it enabled.
> Therefore I
The dependencies already are (and would stay)
iptables (>= 1.8.1-1) | firewalld
from Package: libvirt-daemon-system.
This is very much the same in Debian where we have kept it enabled.
Therefore I can enable the support in libvirt without pushing anything into
main that isn't supposed to be
Hello Christian,
Thank you for your quick and thorough response!
Em quarta-feira, 12 de maio de 2021 08:12:17 -03 você escreveu:
> Hi Thiago,
> the problem is that firewalld isn't in main and thereby not fully
> supported which means that libvirt (that is in main) can not depend on
> it - see
Hi Thiago,
the problem is that firewalld isn't in main and thereby not fully supported
which means that libvirt (that is in main) can not depend on it - see [1] for
some details.
Ubuntu's choice for this usually us UFW, but there is no UFW backend for
libvirt.
Being on iptables wasn't so much
More information I should have mentioned earlier:
The impact of this bug is that libvirt can't start the default network:
bauermann@popigai:~$ virsh -c qemu:///system net-start default
error: Failed to start network default
error: internal error: firewalld is set to use the nftables backend, but
