Assuming this is running upstart (as it looks like), try adding the
debug and verbose flags as shown in the upstart cookbook?
--
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/1551150
Finally some time to check more.
Using new /etc/init/lxc-android-config.conf from Stephane
http://paste.ubuntu.com/15264484/
When running manually $ lxc-start -n android -F -- /init
I can see init process be created, but then it exits. Also there are no logs in
syslog or /proc/kmesg
So looks
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Ondrej Kubik (w-ondra)
** Changed in: canonical-devices-system-image
Assignee: Ondrej Kubik (w-ondra) => John McAleely (john.mcaleely)
** Changed in: lxc (Ubuntu)
Importance: Undecided => Critical
--
You received this bug
** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => backlog
--
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/1551150
Title:
devel-proposed - android lxc container
Update init script is: http://paste.ubuntu.com/15264484/
--
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/1551150
Title:
devel-proposed - android lxc container fails to start
To manage
That part of the init script looks just plain wrong to me... I'm
guessing the intent was for /dev/cpuctl to be a bind-mount of
/sys/fs/cgroup but that's not at all what the code does.
I'll update my local copy here to replace that by a simple symlink from
/dev/cpuctl to /sys/fs/cgroup/cpu
--
missing android signal was caused by double mounting of cgroup cpu,
which was already mounted. Fixing that did take boot further, now
lightdm becomes alive, still boot fails, and kills adb in the process...
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I have a debdiff ready to upload for the changes so far but will wait
until we figure out the rest of this issue.
Serge Hallyn is also working on a cgroup-lite changes to get us rid of
most of that diff too.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
more debugging and android signal is still not emitted, though android init
process is running
Will keep debugging to get closer to the issue
we are progressing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
lxc-container is now running, system still does not boot, but container is no
more issue
needed changes:
install
https://launchpad.net/ubuntu/+source/cgroup-lite/1.10/+build/6001591/+files/cgroup-lite_1.10_all.deb
and modify /etc/init/lxc-android-config.conf to this:
update from running system:
$ cat /proc/cgroups
#subsys_namehierarchy num_cgroups enabled
debug 3 1 1
cpu 1 1 1
cpuacct 2 1 1
freezer 4 1 1
$ cat /proc/self/cgroup
5:name=systemd:/
4:freezer:/
3:debug:/
2:cpuacct:/
1:cpu:/
--
That is very weird, the cgroup-lite upstart job should result in your
case in 4 cgroup mounts, so I'm not sure why it's not happening here...
Could you run "bash -x /bin/cgroups-mount" as root and post its output
including a dump of /proc/self/mountinfo before and after running it?
that should
/proc/cgroups
#subsys_namehierarchy num_cgroups enabled
debug 0 1 1
cpu 0 1 1
cpuacct 0 1 1
freezer 0 1 1
/proc/self/cgroup is empty
There is no /var/log/upstart/cgroup-lite.log file and I verified that
the upstart job
And the content of fstab
/system/etc # cat fstab
# override the forced fsck from /lib/init/fstab, we use a bindmount which
confuses mountall
/dev/root / rootfs defaults0 0
# swap file
/SWAP.swap noneswapsw 0 0
--
You received
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Ondrej Kubik (w-ondra)
--
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/1551150
Title:
devel-proposed -
So far that does seem to confirm the hypothesis that since the phone has
systemd installed (but unused), this meets lxc's dependency on systemd |
cgroup-lite but as upstart is used to boot and upstart itself doesn't
mount the cgroup controllers, this results in a system without cgroups
mounted.
Some more information on cgroup-lite and where it may fail.
- cgroup lite is triggered on "mounted MOUNTPOINT=/sys/fs/cgroup" => the path
is shown as mountend above, so not it
- The job then gets skipped if /bin/cgroups-mount doesn't exist => part of the
cgroup-lite package, so not it
- The
That mountinfo shows no mounted cgroup controller, hinting that cgroup-
lite didn't start or otherwise failed to start.
Could you look for a /var/log/upstart/cgroup-lite.log file?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Hi,
sorry, mountinfo does not show the hierarchies. Can you show
/proc/cgroups and /proc/self/cgroup output?
--
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/1551150
Title:
android container log with cgroup-lite installed and content of
mountinfo from the same boot.
** Attachment added: "mountinfo.out"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584668/+files/mountinfo.out
--
You received this bug notification because
And syslog
** Attachment added: "syslog"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584669/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
The phone uses upstart. I'll try to get the content of mountinfo
--
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/1551150
Title:
devel-proposed - android lxc container fails to start
To
Do you know if the phone actually uses systemd as its init system
nowadays?
LXC requires either systemd or cgroup-lite to mount all the cgroup bits
properly, if systemd is installed but not used, that could explain what
you are seeing. Installing cgroup-lite should have fixed it though,
unless
We're gonna need a /proc/self/mountinfo output if we want to figure out
what the controller #7 is on your system...
--
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/1551150
Title:
With cgroup-lite install the error message is different:
lxc-start 20160229153538.890 ERRORlxc_cgfs - cgfs.c:cgfs_init:2300 -
cgroupfs failed to detect cgroup metadata
lxc-start 20160229153538.890 ERRORlxc_start - start.c:lxc_spawn:1026
- failed initializing cgroup support
I installed cgroup-lite 1.10 but it still doesn't boot.
--
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/1551150
Title:
devel-proposed - android lxc container fails to start
To manage
cgroup-lite is not installed:
un cgroup-lite
ii systemd:armhf 229-1ubuntu4
I cannot paste the content of /proc/mounts because I only have adb in
recovery (the devices fails before adb starts otherwise)
--
You
Can you paste the content of /proc/mounts on such a system and confirm that
either one of those is true:
- systemd is installed and used as init system
- cgroup-lite is installed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
28 matches
Mail list logo
