Bug 683582

Summary: dnsmasq service prevents libvirt's default network from starting
Product: [Fedora] Fedora Reporter: mark <markf78>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: aquini, berrange, clalance, crobinso, itamar, jforbes, laine, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-10 05:14:23 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description mark 2011-03-09 13:48:31 EST
Description of problem:

it appears impossible to run libvirt daemon and dnsmasq at the same time.


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

libvirt-0.8.3-2.fc14.x86_64
dnsmasq-2.52-1.fc13.x86_64
kernel version 2.6.35.11-83.fc14.x86_64

How reproducible:

# sudo service dnsmasq start
# sudo virsh net-start default

Steps to Reproduce:

see above
  
Actual results:

error: Failed to start network default
error: internal error '/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 69 --jump ACCEPT' exited with non-zero status 1 and signal 0: iptables: Bad rule (does a matching rule exist in that chain?).

Expected results:

both services start correctly

Additional info:

if i stop dnsmasq and then issue the command "sudo virsh net-start default" it starts correctly. 

if i start the default network usuing the "sudo virsh net-start default" command and then try to start dnsmasq service, i get this:

# sudo service dnsmasq start
Starting dnsmasq: 
dnsmasq: failed to create listening socket: Address already in use
                                                           [FAILED]
Comment 1 Daniel Berrange 2011-03-10 05:14:23 EST
This is a known issue that requires a workaround in dnsmasq.conf:

http://wiki.libvirt.org/page/Libvirtd_and_dnsmasq