Ubuntu
libvirt package

libvirt conflicts with existing dnsmasq installation

Bug #500484 reported by Alexey Kotlyarov on 2009-12-26

This bug report is a duplicate of: Bug #231060: packages dnsmasq and libvirt-bin conflict with each other. Edit Remove

4

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	libvirt (Ubuntu)	Invalid	Low	Unassigned

Bug Description

Binary package hint: virt-manager

I have dnsmasq installed and running.

When creating (or starting) a virtual network with virt-manager, I get:

Error starting network: internal error 'dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default_network.pid --conf-file= --listen-address 192.168.100.1 --except-interface lo --dhcp-range 192.168.100.128,192.168.100.254' exited with non-zero status 2 and signal 0:
dnsmasq: failed to bind listening socket for 192.168.100.1: Address already in use

The _virtual_ network, which NATs to physical interfaces, should not open any _listening_ ports on them.

ProblemType: Bug
Architecture: amd64
Date: Sat Dec 26 10:37:00 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: virt-manager 0.7.0-3ubuntu1
ProcEnviron:
PATH=(custom, user)
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: virt-manager
Uname: Linux 2.6.31-17-generic x86_64

Tags:

Revision history for this message

Alexey Kotlyarov (koterpillar) wrote on 2009-12-26:

#1

Dependencies.txt Edit (5.7 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (29.0 KiB, text/plain; charset="utf-8")

Marc Deslauriers (mdeslaur) on 2010-02-08

affects:	virt-manager (Ubuntu) → libvirt (Ubuntu)
summary:	- virt-manager conflicts with existing dnsmasq installation + libvirt conflicts with existing dnsmasq installation

Revision history for this message

Chuck Short (zulcss) wrote on 2010-02-09:

#2

Looks like something is already binding to port 53. Can you attach the output of netstat -ap?

Thanks
chuck

Changed in libvirt (Ubuntu):
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

Alexey Kotlyarov (koterpillar) wrote on 2010-02-09:

#3

$ sudo netstat -apn | grep dnsmasq
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 6890/dnsmasq
tcp6 0 0 :::53 :::* LISTEN 6890/dnsmasq
udp 0 0 0.0.0.0:53 0.0.0.0:* 6890/dnsmasq
udp6 0 0 :::53 :::* 6890/dnsmasq
unix 2 [ ] DGRAM 19903 6890/dnsmasq

But that is the point: I need that port. Libvirt should not.

Revision history for this message

Soren Hansen (soren) wrote on 2010-02-09:

#4

I don't fully understand this bug report.

libvirt uses dnsmasq to provide dhcp services to virtual networks. It will not listen on 0.0.0.0. If you have a dnsmasq listening on 0.0.0.0, it's because you've installed the dnsmasq package yourself (libvirt pulls in dnsmasq-base, not dnsmasq) and let it be configured to listen to 0.0.0.0. If it does that, libvirt will not be able to bind to a port 53 on a specific interface.

Revision history for this message

Alexey Kotlyarov (koterpillar) wrote on 2010-02-10:

#5

Thank you for the explanation, I have indeed configured dnsmasq incorrectly. My apologies.

Changed in libvirt (Ubuntu):
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #231060 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.