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
Fix verified on precise.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928524
Title:
lxcbr0 fails to come up when dnsmasq is in
Thomas, Stéphane;
Yes, let's track the change for network-manager in bug #959037 -- marking the
task for n-m here as Invalid.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
** Changed in: network-manager (Ubuntu Precise)
Status: New => Invalid
--
You received this
** Branch linked: lp:ubuntu/precise-proposed/libvirt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928524
Title:
lxcbr0 fails to come up when dnsmasq is installed
To manage notifications about this
Hello Serge, 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. See
https:/
@Stéphane: network-manager should also include a file in dnsmasq.d/ with
"bind-interfaces". Can we track that need in bug #959037 and close this
report (#928524) as affects network-manager?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
That's right.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928524
Title:
lxcbr0 fails to come up when dnsmasq is installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/
That's not completely correct actually (haven't looked at the bug
though).
dnsmasq by default binds on 0.0.0.0 which will include (127.0.0.2), so
even if Network Manager moves to using 127.0.0.2, which I believe is a
good idea, it should still ship a dnsmasq.d config file containing
"bind-interfac
Ah, I understand.
In #959037 various ways of resolving (no pun intended) the conflict
between standalone dnsmasq and nm-dnsmasq have been discussed and in
recent comments we were working on the idea of moving nm-dnsmasq to
another loopback address, say 127.0.0.2, which allows standalone dnsmasq
to
Exactly the same as lxc and libvirt.
That's to have any package using dnsmasq-base also ship /etc/dnsmasq.d/ that contains:
bind-interfaces
except-interface=
For libvirt, that's for virbr0, for lxc that's for lxcbr0 and for
network-manager that'd be the loopback.
This simply prevents dnsmasq fro
My apologies. I thought it was fixed in lxc and nothing needed to be
done for n-m. What further changes do you plan for n-m?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928524
Title:
lxcbr0 fail
Reverting Thomas' change as he didn't give a rational for these and
isn't the network-manager maintainer.
** Changed in: network-manager (Ubuntu)
Status: Invalid => New
** Changed in: network-manager (Ubuntu Precise)
Status: Invalid => New
--
You received this bug notification bec
** Changed in: network-manager (Ubuntu Precise)
Status: New => Invalid
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928524
This bug was fixed in the package lxc - 0.7.5-3ubuntu59
---
lxc (0.7.5-3ubuntu59) precise-proposed; urgency=low
[ Serge Hallyn ]
* 0085-pivot-dir: use a directory other than /mnt to put the pivot_root
old dir into (LP: #986385)
* 0086-lxc-unshare-zero-args: fix lxc-unshare s
Adding a task for network-manager. I believe a similar fix would help
quite a few desktop users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928524
Title:
lxcbr0 fails to come up when dnsmasq is i
Confirmed to work fine here.
** Tags removed: verification-needed
** Tags added: verification-done
** Changed in: dnsmasq (Ubuntu Precise)
Status: New => Invalid
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification b
On 18/06/12 18:11, Thomas Hood wrote:
> Hi Stéphane,
>
> Changing the default of dnsmasq to bind-interfaces wouldn't have been a
> very good solution because some people run dnsmasq without installing
> those other packages and rely upon the "unbound" mode. The implemented
> solution is better be
Indeed, that's the only scenario that'd be a problem, but to workaround
that issue, I added a mention of /etc/dnsmasq.d/ in /etc/default/lxc
which is where you'd disable lxc's own dnsmasq.
So in theory anyone disabling LXC's own dnsmasq daemon will see the note
that they should also update dnsmasq
Hi Stéphane,
Changing the default of dnsmasq to bind-interfaces wouldn't have been a
very good solution because some people run dnsmasq without installing
those other packages and rely upon the "unbound" mode. The implemented
solution is better because the cases of dnsmasq being forced into bind
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 lxcbr0 which our own dnsmasq instance
> will bind to.
There is more risk of trouble than that. With this change, after lxc is
installed, d
** Description changed:
SRU justification ===
Impact: lxc (by way of lxc-net) fails to start when dnsmasq is installed
Development fix: install a dnsmasq.d file to prevent the system-wide dnsmasq
from binding to lxcbr0
Stable fix: same as Development fix
Test case:
** Branch linked: lp:ubuntu/precise-proposed/lxc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928524
Title:
lxcbr0 fails to come up when dnsmasq is installed
To manage notifications about this bug
Hello Serge, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback will
** Description changed:
+ SRU justification ===
+ Impact: lxc (by way of lxc-net) fails to start when dnsmasq is installed
+ Development fix: install a dnsmasq.d file to prevent the system-wide dnsmasq
+ from binding to lxcbr0
+ Stable fix: same as Development fix
+ Test case:
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
** Branch linked: lp:ubuntu/lxc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928524
Title:
lxcbr0 fails to come up when dnsmasq is installed
To manage notifications about this bug go to:
https://b
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu10
---
lxc (0.8.0~rc1-4ubuntu10) quantal; urgency=low
[ Serge Hallyn ]
* 0084-lxc-ubuntu-drop-duplicate-code.patch: drop some duplicate code from
the ubuntu template. (LP: #1004118)
* 0085-pivot-dir: use a directory ot
** Changed in: lxc (Ubuntu)
Importance: Low => High
** Changed in: libvirt (Ubuntu)
Importance: Low => High
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Here is the entry in the libvirt wiki describing this problem and the
solution:
http://wiki.libvirt.org/page/Virtual_network_%27default%27_has_not_been_started
In short, the systemwide dnsmasq instance should have "bind-interfaces"
added to its configuration, and the particular interfaces you wan
Now that we rely on dnsmasq by default for name resolution, the
importance is higher because the bridge comes up before dnsmasq, dnsmasq
fails to start and the system can't do name resolution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928524
Title:
lxc
A recommendation in comments 7 and 8 of bug 925511 seems like the best
way to solve this for both lxc and libvirt. However, I don't think
we'll have time to do this in time for precise. The libvirt patch will
have to be sent and vetted upstream, both lxc and libvirt will need to
switch from depen
33 matches
Mail list logo
