Hi,
I suspect you're suffering from the veth offloading feature in saucy
kernel. If possible please flush the lxc cache (sudo rm -rf
/var/cache/lxc/*) and re-create the containers, or else chroot into the
containers to update them. Newer userspace will work around the
"feature".
If that doesn't
Is it possible that this bug returned?
I updated the host to ubuntu saucy and lxc was working fine with the
virtual machine "jenkins". Once I updated the guest system to saucy as
well, it seemed not to boot, but I was wrong. It never reached the
runlevel (5), which it did before.
Here is the outp
This bug was fixed in the package lxc - 0.7.4-0ubuntu7.3
---
lxc (0.7.4-0ubuntu7.3) natty-proposed; urgency=low
* lxcguest.lxcguest.upstart: emit the net-device-up IFACE=lo event, so
that any upstart jobs waiting on it (esp rc-sysinit before oneiric) will
proceed. (LP: #924
Based on comment above, marking verification-done
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc
Just confirmed; this did fix a newly created Natty container for me.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid contai
Salgado, would you be able to do this verification? If not, let me
know, and I'll do it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with
** Branch linked: lp:ubuntu/natty-proposed/lxc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid containers (container does
not rea
Hello Gary, or anyone else affected,
Accepted lxc into natty-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Cha
Confirmed - in fact /etc/init/lxcguest.conf is missing altogether,
causing other problems as well.
I'll push a fix to natty-proposed. Thanks for pointing this out.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https:/
This happens to me on a Natty container:
salgado@delgadito:~$ cat /var/lib/lxc/patchmetrics/rootfs/etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=11.04
DISTRIB_CODENAME=natty
DISTRIB_DESCRIPTION="Ubuntu 11.04"
salgado@delgadito:~$ sudo lxc-start -n patchmetrics
init: procps main process (26) t
This bug was fixed in the package lxc - 0.7.5-0ubuntu8.5
---
lxc (0.7.5-0ubuntu8.5) oneiric-proposed; urgency=low
* lxcguest.lxcguest.upstart: emit the net-device-up IFACE=lo event, so
that any upstart jobs waiting on it (esp rc-sysinit before oneiric) will
proceed. (LP: #9
Confirmed, lxcguest from oneiric-proposed fixes this in an oneiric
guest.
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/b
** Branch linked: lp:ubuntu/oneiric-proposed/lxc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid containers (container does
not r
Hello Gary, or anyone else affected,
Accepted lxc into oneiric-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** C
** Description changed:
+
+ SRU Justification
+ 1. Impact: any upstart jobs which start on lo being raised will not start
+ 2. Development fix: lxcguest emits the signal pretending that lo was created
+ 3. Stable fix: same as development fix
+ 4. Test c
** Changed in: lxc (Ubuntu Natty)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid containers (contain
** Branch linked: lp:ubuntu/lxc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid containers (container does
not reach runlevel 2)
This bug was fixed in the package lxc - 0.7.5-3ubuntu18
---
lxc (0.7.5-3ubuntu18) precise; urgency=low
* lxcguest.lxcguest.upstart: emit the net-device-up IFACE=lo event, so
that any upstart jobs waiting on it (esp rc-sysinit before oneiric) will
proceed. (LP: #924337)
*
** Changed in: lxc (Ubuntu)
Status: Fix Released => Confirmed
** Also affects: lxc (Ubuntu Oneiric)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpa
** Changed in: lxc (Ubuntu)
Assignee: Stéphane Graber (stgraber) => Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: lxc (Ubuntu Natty)
Importance: Undecided
Status: New
--
You received this bug notification because
Right, so we need for anything before Oneiric to have that emit in
lxcguest, since Oneiric it should be properly handled by networking.conf
bringing up lo and by the static-network-up event.
Starting with Precise where we won't have lxcguest, the same trick as
Oneiric will work so we won't need to
It turns out the original problem never went away. The container never
gets a net-device-up event for lo, even in precise. You can verify this
trivially with two upstart jobs, /etc/init/lxc{lo,eth}.conf:
lxclo.conf
description "detect net-device-up IFACE=lo"
start on net-device-up IFAC
When I first created lxcguest, one of the main things it did was emit
that event. Then we stopped having to, but the reasons were always a
bit too mysterious for me.
Assigning to stgraber as I *believe* he will know offhand what's going
on. If not, please feel free to reassign to me.
** Changed
rc-sysinit.conf never starts because it doesn't see net-device-up for
lo. When I do:
sudo initctl emit --no-wait net-device-up IFACE=lo
then the container transitions to runlevel 'N 2'.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Summary changed:
- lxc on precise is not working with lucid containers
+ lxc on precise is not working with lucid containers (container does not reach
runlevel 2)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https
Serge, cool. The workaround is fine. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid containers
To manage notifications
It seems to be a bug in lxcguest. runlevel shows 'unknown', whereas on
a real host or precise container it shows 'N 2'
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Reproduced. Note that during this time I can ssh in just fine. The
container does have an ip address! (you can find it with tail
/var/log/daemon.log on the host)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https:/
@Gary
terribly sorry, 'mounted=/run' won't work in your containers as you are
using lxcguest.
You should be safe to just make it 'start on started lxcguest' (really
even 'start on startup', which I just tried and worked fine)
--
You received this bug notification because you are a member of Ubu
** Changed in: lxc (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid containers
To manage
I tried the fix and I got the same symptom.
For clarity:
- I wiped out /var/lxc/cache before I started because lxc-create wasn't
working. That got lxc-create working. I used the same commands I
listed in the bug description.
- I changed the container's console.conf as described:
$ cat /var/li
Thanks, Gary.
Note that the upstart 'fix' will basically be the same as the suggested
workaround.
I think the stp on for virbr0 is actually a red herring here, for two
reasons. First, you show in the Description that you are using lxcbr0,
which should have stp off. Second, in my own experiments
I reported on IRC to Serge that virbr0 did indeed have STP enabled, but
that I did not see any obvious dnsmasq errors. He already had diagnosed
the problem & said as a workaround I could just change the 'start on' in
/etc/init/console.conf in my container to 'start on mounted
MOUNTPOINT=/run'. st
Hi Gary,
when we've seen this before it has been because the container was
waiting for a dhcp response. It has generally been on virbr0, and when
virbr0 had stp on.
Can you show what 'brctl show' on the host gives? Do your host logs
show any problems with dnsmasq on lxcbr0?
** Changed in: lxc
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid containers
To manage
35 matches
Mail list logo
