This post suggests that it could be a packaging problem: https://nocthoughts.com/2023/04/26/arch-linux-virt-manager-and-firewalld.html
In any case, the libvirt-daemon-driver-network package contains
template firewalld zone files in /usr/lib/firewalld/zones/ - it
suffices to copy them to /etc/firewalld/zones/ and restart
firewalld.
I've found the root of the problem: I was connecting to libvirt via ssh
using an unprivileged user part of the libvirt group. That works for
most of the tasks but not for creating the firewalld libvirt zone. Using root, while being less than ideal, works fine.
I think what might be happening is that we don't have any code in the
libvirt package that matches the following snippet from the upstream
spec file:
%post daemon-driver-network
%if %{with_firewalld_zone}
%firewalld_reload
%endif
It would probably make sense to at least attempt to reload firewalld
when the network driver is installed, the way upstream and Fedora
already do.
--
Andrea Bolognani <eof@kiyuko.org>
Resistance is futile, you will be garbage collected.
_______________________________________________
Pkg-libvirt-maintainers mailing list Pkg-libvirt-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers
On Sun, Apr 13, 2025 at 01:15:28AM +0200, Andrea Bolognani wrote:
I think what might be happening is that we don't have any code in the libvirt package that matches the following snippet from the upstream
spec file:
%post daemon-driver-network
%if %{with_firewalld_zone}
%firewalld_reload
%endif
Nice find!
It would probably make sense to at least attempt to reload firewalld
when the network driver is installed, the way upstream and Fedora
already do.
Instead of all packages shipping zones doing this firewalld should
likely better register a trigger, like e.g. glib does for new schemas:
/usr/share/glib-2.0/schemas libglib2.0-0t64:amd64
in /var/lib/dpkg/triggers/File
so probably best to move the issue there?
Control: reassing -1 firewalld
Control: retitle -1 firewalld: Please introduce a trigger for zones installed by other packages
Control: affects -1 libvirt
On Sun, Apr 13, 2025 at 09:28:58AM +0200, Guido Günther wrote:
On Sun, Apr 13, 2025 at 01:15:28AM +0200, Andrea Bolognani wrote:
I think what might be happening is that we don't have any code in the libvirt package that matches the following snippet from the upstream
spec file:
%post daemon-driver-network
%if %{with_firewalld_zone}
%firewalld_reload
%endif
Nice find!
It would probably make sense to at least attempt to reload firewalld
when the network driver is installed, the way upstream and Fedora
already do.
Instead of all packages shipping zones doing this firewalld should
likely better register a trigger, like e.g. glib does for new schemas:
/usr/share/glib-2.0/schemas libglib2.0-0t64:amd64
in /var/lib/dpkg/triggers/File
so probably best to move the issue there?
Agreed, that would probably be the best way to handle things.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 482 |
Nodes: | 16 (2 / 14) |
Uptime: | 53:49:50 |
Calls: | 9,566 |
Files: | 13,660 |
Messages: | 6,142,642 |