libvirt users - May 2016 - Re: dhcpd (via systemd) @boottime which does not wait for the interface..

hi users

I have my dhcpd to serve nothing but virbr0 (libvirt), OS is Centos 7.2
Dhcpd would not start, complaining like this:

No subnet declaration for virbr0 (no IPv4 addresses).
** Ignoring requests on virbr0.  If this is not what
   you want, please write a subnet declaration
   in your dhcpd.conf file for the network segment
   to which interface virbr0 is attached. **
##SELECTION_END##
and systemctl -l shows:
...
systemd[1]: start request repeated too quickly for dhcpd.service
...

but suffice to restart dhcpd and all works!
I'v customized systemd's service conf, I've put:

After=libvirtd.service
Requisite=libvirtd.service

but this did not help.
Would you share your thoughts? Systemd list say it's libvirt
(wrong)doing.
many thanks.
L.

On Fri, 2016-05-06 at 07:41 -0400, Laine Stump wrote:
> On 05/04/2016 08:40 AM, lejeczek wrote:
> 
> > hi users
> > 
> > 
> > I have my dhcpd to serve nothing but virbr0 (libvirt), OS is Centos
> > 7.2
> > Dhcpd would not start, complaining like this:
> > 
>  
> Is virbr0 created by libvirt as part of one of its "virtual
> networks"? If so, why are you using dhcpd rather than the dnsmasq
> that libvirt already runs for it (and how are you managing to
> terminate the dnsmasq process run by libvirt so its listening socket
> doesn't conflict with the listener setup by dhcpd?)
yes, set up like this: 
 <forward mode='route'/>
  <bridge name='virbr0' stp='on' delay='0'/>
It really is simple plain vanilla setup, maybe not common but simple,
should be easy to reproduce: libvirtd's only one virbr0 and dhcpd to
listen only on this iface.
> 
>     
> 
>     > > 
> >       > > 
> >         
> > 
> >         
> > 
> >         > > No subnet declaration for virbr0 (no IPv4
addresses).
> > 
> >         > > ** Ignoring requests on virbr0.  If this is not what
> > 
> >         > >    you want, please write a subnet declaration
> > 
> >         > >    in your dhcpd.conf file for the network segment
> > 
> >         > >    to which interface virbr0 is attached. **
> > 
> >         
> > 
> >         
> > 
> >         > > and systemctl -l shows:
> > 
> >         > > ...
> > 
> >         > > systemd[1]: start request repeated too quickly for
> >           dhcpd.service
> > 
> >         > > ...
> > 
> >         
> > 
> >         
> > 
> >         > > but suffice to restart dhcpd and all works!
> > 
> >         > > I'v customized systemd's service conf,
I've put:
> > 
> >         
> > 
> >         
> > 
> >         > > After=libvirtd.service
> > 
> >         > > Requisite=libvirtd.service
> > 
> >       
> > 
> >     
> 
>     
> 
>     If virbr0 is created by libvirt, it's already starting a dnsmasq
>     process to handle dhcp requests, so you don't need (and
shouldn't be
>     able to start) dhcpd listening on it. If virbr0 *isn't* created by
>     libvirt, then the change to systemd's configuration won't have
any
>     effect.
> 
>     
> 
>     > > 
> >       > > 
> >         
> > 
> >         
> > 
> >         > > but this did not help.
> > 
> >         > > Would you share your thoughts? Systemd list say
it's
> >           libvirt (wrong)doing.
> > 
> >         > > many thanks.
> > 
> >       
> > 
> >     
> 
>     > > 
> >       > > 
> >         > > L.
> > 
> >       
> > 
> >       
> > 
> >       > > 
> >       
> > 
> >       > > _______________________________________________
> > libvirt-users mailing list
> > 
libvirt-users@redhat.com> > 
https://www.redhat.com/mailman/listinfo/libvirt-users
> > 
> >     
> 
>     
> 
>     
> 
>   
> 
>