Red Hat Bugzilla – Bug 636115
RFE: dnsmasq: rewrite dnsmasq integration to work with a single system instance
Last modified: 2016-05-02 10:18:08 EDT
Description of problem:
Upstream dnsmasq offered to extend its functionality to allow libvirt to drop in configuration for a single system instance. This will avoid the problem of clashing dnsmsaq processes on a single host.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
changed behavior to always start dnsmasq if ip addresses are defined. There is no keyword (that I can find) to tell libvirt "don't start a dnsmasq for this bridge, I want to run one myself". Is adding such a keyword ok, or is it nacked on principle?
(In reply to serge from comment #1)
> changed behavior to always start dnsmasq if ip addresses are defined. There
> is no keyword (that I can find) to tell libvirt "don't start a dnsmasq for
> this bridge, I want to run one myself". Is adding such a keyword ok, or is
> it nacked on principle?
serge if your issue was never resolved I suggest starting a thread on libvir-list instead, it will probably get a better response
I know we've reworked dnsmasq code quite a bit over the years, but we still haven't gotten around to using a single system dnsmasq instance and I don't really hear people clamoring for it... is this even still relevant?
Just re-iterating that I don't really see us reworking the network driver to work like this. Maybe we could make it an optional config to use a single system daemon, but since it doesn't sound like there's many requests for this feature and the work isn't exactly forthcoming I don't see the benefit in tracking it here