Bug 692214 - libvirt has low possibilities to manage dnsmasq
Summary: libvirt has low possibilities to manage dnsmasq
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-30 17:41 UTC by Jiri Kastner
Modified: 2011-06-02 13:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-02 13:41:15 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jiri Kastner 2011-03-30 17:41:50 UTC
Description of problem:
libvirtd starts dnsmasq with "... --conf-file= --listen..." which doesn't allow customization of dnsmasq behavior. --conf-file should lead to some file. e.g. to /etc/libvirt/dnsmasq/default.conf for 'default' network

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. service libvirtd restart
2. ps ewww -p `pgrep dnsmasq`
3. check --conf-file parametr
  
Actual results:
/usr/sbin/dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file=  --listen-address 192.168.122.1 --except-interface lo --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-lease-max=253

Expected results:
/usr/sbin/dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file=/etc/libvirt/dnsmasq/default.conf  --listen-address 192.168.122.1 --except-interface lo --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-lease-max=253

Additional info:

Comment 2 Jiri Denemark 2011-06-02 13:41:15 UTC
It's a design decision that libvirt (upstream, not just RHEL) doesn't allow for any kind of configuration of dnsmasq except for what can be done through network XML. However, if you want specific features that dnsmasq provides, we can consider modeling them in network XML so that users may use them through libvirt.


Note You need to log in before you can comment on or make changes to this bug.