Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-11 Thread Dariusz Michaluk
On 10.03.2014 22:50, Lennart Poettering wrote: Which version of systemd is this? any chance you can reproduce this with systemctl compiled fresh from current git? Or could you run gdbus introspect --system --dest org.freedesktop.systemd1 --object-path /org/freedesktop/systemd1 and see if any of

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-10 Thread Lennart Poettering
On Thu, 06.03.14 10:51, Dariusz Michaluk (d.micha...@samsung.com) wrote: Program received signal SIGSEGV, Segmentation fault. sd_bus_message_unref (m=0x8000) at ../src/libsystemd/sd-bus/bus-message.c:800 800 m-n_ref--; (gdb) bt #0 sd_bus_message_unref (m=0x8000) at

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-07 Thread Daniel P. Berrange
On Thu, Mar 06, 2014 at 07:54:05PM +0100, Lennart Poettering wrote: On Thu, 06.03.14 16:55, Dariusz Michaluk (d.micha...@samsung.com) wrote: On 05.03.2014 19:16, Lennart Poettering wrote: nspawn and libvirt-lxc mostly follow the same code paths and register via machined... So it's

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-07 Thread Dariusz Michaluk
On 07.03.2014 10:39, Daniel P. Berrange wrote: Can someone file a bug against libvirt for this and we'll look at not doing this. https://bugzilla.redhat.com/show_bug.cgi?id=1073891 -- Dariusz Michaluk Samsung RD Institute Poland Samsung Electronics d.micha...@samsung.com

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-06 Thread Dariusz Michaluk
On 05.03.2014 19:16, Lennart Poettering wrote: Oh, yuck! THis is weird. Can you get a gdb backtrac and/or valgrind run for this? Can't reproduce this here... (gdb) run show Starting program: /usr/bin/systemctl show [Thread debugging using libthread_db enabled] Using host libthread_db library

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-06 Thread Jacek Pielaszkiewicz
, 2014 9:11 PM To: Jacek Pielaszkiewicz Cc: systemd-devel@lists.freedesktop.org Subject: Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container On Tue, 04.03.14 16:23, Jacek Pielaszkiewicz (j.pielasz...@samsung.com) wrote: +-machine.slice │ L-machine

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-06 Thread Jacek Pielaszkiewicz
- From: Jacek Pielaszkiewicz [mailto:j.pielasz...@samsung.com] Sent: Thursday, March 06, 2014 12:55 PM To: 'Lennart Poettering' Cc: 'systemd-devel@lists.freedesktop.org' Subject: RE: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container Hi

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-06 Thread Jacek Pielaszkiewicz
-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container Hi In previous mail I putted case for libvirt. In case of nspawn everything works fine (see details below): +++ Guest Jacek Pielaszkiewicz Samsung RD Institute

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-06 Thread Dariusz Michaluk
On 05.03.2014 19:16, Lennart Poettering wrote: nspawn and libvirt-lxc mostly follow the same code paths and register via machined... So it's weird that different things happen. Somehow the systemd instance inside the container must be confused about the cgroup it is running in... Next few

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-06 Thread Lennart Poettering
On Thu, 06.03.14 16:55, Dariusz Michaluk (d.micha...@samsung.com) wrote: On 05.03.2014 19:16, Lennart Poettering wrote: nspawn and libvirt-lxc mostly follow the same code paths and register via machined... So it's weird that different things happen. Somehow the systemd instance inside the

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-05 Thread Dariusz Michaluk
On 04.03.2014 21:10, Lennart Poettering wrote: OK, this looks wrong, the machine slice appears to have been used twice in the cgroup path. Can you try this with 210 in the container, and then run systemctl show and report the value of the ControlGroup property, please? If you boot this up

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-05 Thread Lennart Poettering
On Wed, 05.03.14 11:38, Dariusz Michaluk (d.micha...@samsung.com) wrote: I can't report the value of the ControlGroup property, I get this: # systemctl show Segmentation fault Oh, yuck! THis is weird. Can you get a gdb backtrac and/or valgrind run for this? Can't reproduce this here...

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-05 Thread arnaud gaboury
I can reproduce similar behaviour on Fedora 21. I used Linux 3.14.0-0.rc5, systemd 210 on host and guest machine, libvirtd 1.2.2. See this yesterday thread Network unreachable in container and Lennart comment : What is Host ? What is guest ?? ___

[systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-04 Thread Jacek Pielaszkiewicz
Hi, It seems that systemd builds incorrectly cgroup hierarchy when is running in the container. Systemd duplicates part of the hierarchy below machine.slice/machine...scope/. It causes finally that non root user session cannot be created due to lack of permissions. In nspawn

Re: [systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

2014-03-04 Thread Lennart Poettering
On Tue, 04.03.14 16:23, Jacek Pielaszkiewicz (j.pielasz...@samsung.com) wrote: +-machine.slice │ L-machine-lxc\x2dtizen\x2dbash\x2d2.scope │ +-2672 /usr/libexec/libvirt_lxc --name tizen-bash-2 --console 20 -- security= │ L-machine.slice │ L-machine-lxc\x2dtizen\x2dbash\x2d2.scope │