This bug was fixed in the package libvirt - 0.9.8-2ubuntu17.2
---
libvirt (0.9.8-2ubuntu17.2) precise-proposed; urgency=low
* debian/libvirt-bin.install, debian/rules: name the apport file
source_libvirt.py, not source_libvirt-bin.py. (LP: #1007405)
* install /etc/dnsmasq.d/l
Marking verification-done based on previous comment.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title
Verified on precise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
packages dnsmasq and libvirt-bin conflict with each other
To manage notifications about this bug g
** Branch linked: lp:ubuntu/precise-proposed/libvirt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
packages dnsmasq and libvirt-bin conflict with each other
To manag
Hello Louis-Dominique, or anyone else affected,
Accepted libvirt into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/libvirt/0.9.8-2ubuntu17.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. S
** Changed in: dnsmasq (Ubuntu Precise)
Status: New => Invalid
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bug
> Is there anything more to do in dnsmasq for this bug report?
I don't believe so. While it'll definately be great to have dnsmasq
in bind-interfaces mode detect new interfaces, that doesn't need to
be tracked here.
Thanks.
--
You received this bug notification because you are a member of Ubun
Is there anything more to do in dnsmasq for this bug report?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
packages dnsmasq and libvirt-bin conflict with each other
(Cont'd.) Simon Kelley on enhancing dnsmasq and subsequent discussion in
bug #959037 comment #89 (e.g.).
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/959037/comments/89
In the same bug report we discuss various ways of getting
NetworkManager-controlled dnsmasq ("nm-dnsmasq") and standal
>From the IRC discussion:
23:01 < RAOF> stgraber: I don't suppose there's a way to get the best of both
worlds? Have dnsmasq ignore the interfaces you need, *and* pick up new
interfaces?
23:01 < RAOF> For example: how disruptive is restarting dnsmasq?
Please note that Simon Kelley is working on
As per discussion on irc, I've kept the removal of
/etc/dnsmasq.d/libvirt (because otherwise dnsmasq could be kept in bind-
interfaces mode even though it didn't need to be), but added a warning
comment at the top of the file that any changes will be lost when
libvirt-bin is removed.
Package re-dp
http://paste.ubuntu.com/1062735/ is an irc discussion where RAOF and
stgraber appear to come to an agreement about the dnsmasq bit. So I
will fix the postrm, and resubmit.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubu
On 19/06/12 10:10, Chris Halse Rogers wrote:
> Additionally, I'd like to know what the likely impact of adding bind-
> interfaces to dnsmasq is on users. What (if anything) will break on
> users' systems?
>
Three things change.
1) Dnsmasq loses the ability to provide service on dynamically crea
The proposed package (specifically the postrm) breaks Policy - you're
unconditionally removing a conffile on upgrade/removal/etc which will
destroy any user changes.
Additionally, I'd like to know what the likely impact of adding bind-
interfaces to dnsmasq is on users. What (if anything) will bre
** Also affects: dnsmasq (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubun
s/lxc/libvirt-bin/ (copy/pasted the reply from an identical comment in
bug 928524)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
packages dnsmasq and libvirt-bin conf
That's correct, though currently when installing dnsmasq with lxc, it
has a 50% chance of not starting at all (the other 50% being lxc not
starting at all).
My initial idea was to set bind-interfaces by default in dnsmasq and SRU
that as it's default behaviour is breaking many setups and is extrem
>From the SRU justification:
> Regression potential: There should be none, since we are
> simply telling the system-wide dnsmasq (if any) not to bind
> to the virbr0 which our own dnsmasq instance will bind to.
There is more risk of trouble than that. With this change to libvirt-
bin, after libvi
Launchpad did NOT like that :) So I added an SRU justification here.
thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
packages dnsmasq and libvirt-bin conflict
Hi Brian,
until recently I wasn't quite sure if there might be a difference
between this bug and bug 928524. There is not, so I will mark this bug
a duplicate of bug 928524, which has an SRU justification.
Thanks.
** Description changed:
+ SRU justification ===
+ Impact: l
Great, thanks Thomas!
In that case, the SRU fixes are pending acceptance in the archive for
lucid, oneiric and precise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
@Serge: I was just going by what I read in comment #1 where vnet0 was
named.
You are right. Adding --bind-interfaces and --exclude-interface=virbr0
allows both the general dnsmasq and the libvirt-bin dnsmasq to start.
Without --bind-interfaces and --exclude-interface=virbr0:
dnsmasq[5279]:
@Thomas,
I'm probably wrong, but are you sure that vnet0 needs to be listed?
vnet0 is usually a nic bridged to either br0 or virbr0. i would think
that dnsmasq would ignore bridged interfaces.
In fact, using just 'except-interface=virbr0' I brought up a kvm guest
(which had vnet0 as its nic on t
** Changed in: dnsmasq (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
packages dnsmasq and libvirt-bin conflict with
Oops, I changed the status to "fix released" but then realized that
#231060 wasn't addressed by 0.9.12-0ubuntu3. The latter included
bind-interfaces
except-interface=virbr0
whereas to fix #231060 the following would be needed.
bind-interfaces
except-interface=vnet0
I don't have
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
packages dnsmasq and libvirt-bin conflict with
** Branch linked: lp:ubuntu/libvirt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
packages dnsmasq and libvirt-bin conflict with each other
To manage notifications a
This bug was fixed in the package libvirt - 0.9.12-0ubuntu3
---
libvirt (0.9.12-0ubuntu3) quantal; urgency=low
* install apport hook as right name - libvirt-bin is the binary package,
the source package name is libvirt. (LP: #1007405)
* install /etc/dnsmasq.d/libvirt to confi
@Thomas,
I was planning on doing a fix like the one Stéphane pushed for
lxc+dnsmasq in 928524. Would that address the concerns in this bug? (I
believe it would, but maybe there is more to this particular bug that I
am missing).
--
You received this bug notification because you are a member of
** Changed in: dnsmasq (Ubuntu)
Status: In Progress => Confirmed
** Changed in: libvirt (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.n
@Thomas,
959037 means that this issue potentially exists for everyone, rather than
just those few folk with specialised needs (mine having been running both a
virtualisation host and a tftp server on the same machine).
The main issue being the racy nature of running multiple greedy
dnsma
** Changed in: dnsmasq (Ubuntu)
Assignee: Emmet Hikory (persia) => (unassigned)
** Changed in: libvirt (Ubuntu)
Assignee: Emmet Hikory (persia) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu
Emmet in #14> So, my plan is as follows:
Should #959037 be taken into consideration here?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
packages dnsmasq and libvirt-
On 10.04
Netstat give me no listen on port 53 for dnsmasq after the reboot.
Installing with apt-get libvirt-bin dnsmasq dnsmasq-base give me no
error's. But no virbr0!
So setting up virbr0 with the command virsh net-define default.xml en
virsh net-autostart default is ok. But net-start default i
Natty 11.04
does the same as 10.04!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in ubuntu.
https://bugs.launchpad.net/bugs/231060
Title:
packages dnsmasq and libvirt-bin conflict with each other
--
Ubuntu-server-bugs m
Lucid 10.04
With no bind9 installed and apt-get purge libvirt-bin, dnsmasq, dnsmasq-
base:
netstat -nap | grep dnsmasq say it still listen on port 53.
sudo apt-get install dnsmasq give me now the error dnsmasq: failed to
create listening socket: Address already in use
Why is port 53 not cleaned
@Simon, Thanks for the guidance. Of the options:
1) This seems least invasive in the short-term
2) There's a few potential issues here.
a) Install order, because defaults need to be adjusted, and services may
need to restart. Some of this can be handled by triggers, but it
requires cooperation
Thierry Carrez wrote:
> @Simon: what are the options from a dnsmasq perspective ?
>
Some background: dnsmasq can run in two modes.
Default mode: dnsmasq binds the wildcard address and does network magic
to determine which interface request packets actually come from, so that
the results can be
@Simon: what are the options from a dnsmasq perspective ?
--
packages dnsmasq and libvirt-bin conflict with each other
https://bugs.launchpad.net/bugs/231060
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in ubuntu.
--
Ubuntu-se
Implementation of this in libvirt is blocked by a race condition that
prevents the use of the --interface argument in libvirt. There is a
race condition when using --listen-address that dnsmasq will immediately
exit if the interface is not yet visible to userspace, which can often
happen with how
Yes, this is still a problem with libvirt (dnsmasq doesn't start in its
default config when you install it after libvirt-bin)
I actually checked that except-interface= is additive, so it's fine to
ship a snippet listing it.
--
packages dnsmasq and libvirt-bin conflict with each other
https://bug
Is this still a problem with libvirt?
Regards
chuck
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Low
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
--
packages dnsmasq and libvirt-bin conflict with each other
https://bugs.launchpad.net/bugs/231060
You received thi
Support for dnsmasq.d is now in Jaunty's dnsmasq.
Ready to work with whatever libvirt would drop there.
** Changed in: dnsmasq (Ubuntu)
Status: New => Fix Released
--
packages dnsmasq and libvirt-bin conflict with each other
https://bugs.launchpad.net/bugs/231060
You received this bug not
dnsmasq 2.46-1 (soon in an archive near you) implements a /etc/dnsmasq.d
directory that allows to drop configuration snippets from other
packages. This opens ways for more collaboration between the two
packages.
Following advice in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505522
We could f
The problem is not really in libvirt, which calls dnsmasq with the
appropriate settings to limit itself to the right interface. It's in
dnsmasq, which by default binds to all interfaces, thus preventing the
dnsmasq-from-libvirt from serving its addresses.
I tend to agree with Soren and Neal : yes,
libvirt now depends on dnsmasq-base, which does not install any config files.
After doing a default install
dnsmasq starts with:
dnsmasq --keep-in-foreground --strict-order --bind-interfaces --pid-file
--conf-file --listen-address 192.168.122.1 --except-interface lo
--dhcp-leasefile=/var/lib
How about a more helpful error message? Perhaps libvirtd could notice
that dnsmasq is already running and say "please disable dnsmasq on
interface xyz". Or maybe dnsmasq itself could be noticing that?
--
packages dnsmasq and libvirt-bin conflict with each other
https://bugs.launchpad.net/bugs/
dnsmasq is a general purpose dns (and DHCP, but let's ignore this for the
purpose of this conversation) server.
The dnsmasq package installs itself and starts listening on all interfaces.
That seems like a reasonable default behaviour for a general purpose caching
dns server to me.
libvirt uses
The above workarounds only work if you also set "bind-interfaces" in
/etc/dnsmasq.conf, otherwise dnsmasq binds to the wildcard address.
--
packages dnsmasq and libvirt-bin conflict with each other
https://bugs.launchpad.net/bugs/231060
You received this bug notification because you are a member
49 matches
Mail list logo