[Pkg-libvirt-maintainers] Bug#714372: Bug#714372: libvirt: Please enable firewalld support

[Guido Günther]

On Sun, Jun 30, 2013 at 10:42:08PM +0200, Laurent Bigonville wrote:
> Le Fri, 28 Jun 2013 22:05:34 +0200,
> Guido Günther <agx at sigxcpu.org> a écrit :
> 
> > On Fri, Jun 28, 2013 at 04:44:01PM +0200, Laurent Bigonville wrote:
> > > Le Fri, 28 Jun 2013 16:36:13 +0200,
> > > Guido Günther <agx at sigxcpu.org> a écrit :
> > > 
> > > > Hi,
> > > > On Fri, Jun 28, 2013 at 04:22:26PM +0200, Laurent Bigonville
> > > > wrote:
> > > > > Source: libvirt
> > > > > Version: 1.0.6-1
> > > > > Severity: wishlist
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > Could you please enabled firewalld support.
> > > > > 
> > > > > The code should provide a fallback to the regular calls to
> > > > > iptables if the daemon is not running (I didn't test this
> > > > > myself)
> > > > > 
> > > > > The firewalld package is itself depending against the iptables
> > > > > package, so I guess it's not really usefull to enable this
> > > > > on !linux.
> > > > 
> > > > Could you check if the fallback works? We had firewalld disabled
> > > > and it caused trouble without firewalld installed.
> > > 
> > > 
> > > Any reference on what was broken?
> > 
> > It was a long time ago but IIRC the build relied on firewalld being
> > available if support was compiled in. So libvirtd wouldn't start and
> > when working around that it failed to do proper nating etc.
> 
> OK, I've just tested and libvirt seems to work as expected if firewalld
> is not running.
> 
> However I've experienced a bug with firewalld itself (the bug has been
> reported upstream).
> 
> I guess we should wait until this is fixed before enabling the support
> in libvirt.
Thanks for testing. Could you add a reference to the upstream bugreport
that blocks enabling firewalld to this bug?
 -- Guido