diff options
| author | Mark Asselstine <mark.asselstine@windriver.com> | 2015-09-10 13:59:12 -0400 |
|---|---|---|
| committer | Bruce Ashfield <bruce.ashfield@windriver.com> | 2015-09-10 14:42:43 -0400 |
| commit | c3c4d977cbb51363f9030c2e39d56a772b29f73b (patch) | |
| tree | 2000260bd86943fe0eb820856840f022b6b29d34 /recipes-networking/openvswitch/openvswitch-git | |
| parent | 62e49b861f211312a16367e9b032dfa097fab7d6 (diff) | |
| download | meta-virtualization-c3c4d977cbb51363f9030c2e39d56a772b29f73b.tar.gz | |
dnsmasq: allow for multiple instances (per libvirt)
We have had a persistent issue of contention with multiple instances
of dnsmasq. When libvirtd is started it will attempt and fail to
create virbr0 that includes a dnsmasq binding (dnsmasq complains that
the port is already in use). The root cause being that the base
dnsmasq configuration uses the 'default' binding, meaning it will be
greedy and bind to all available interfaces, along with any new
interfaces that appear. This prevents any new instances of dnsmasq to
fail. By changing the base dnsmasq configuration to use 'bind-dynamic'
we will be able to create new interfaces and if we want to attach a
new dnsmasq instance for the new interface we can, without contention.
Overall this change should not change the default behavior (other then
fixing the contention) as the 'bind-dynamic' mode will allow the base
config to attach to new interfaces which are not be bound to new
dnsmasq instances.
Removing dnsmasq_exclude_virbr.conf which was a previous (partial)
attempt that was made to resolve this issue.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'recipes-networking/openvswitch/openvswitch-git')
0 files changed, 0 insertions, 0 deletions