Bug#754184: systemd: poweroff shuts down systemd-nspawn-ed container

2014-07-09 Thread Łukasz Stelmach
It was 2014-07-08 wto 21:34, when Michael Biebl wrote:
 Am 08.07.2014 17:50, schrieb Łukasz Stelmach:
 It was 2014-07-08 wto 16:29, when Michael Biebl wrote:
 Am 08.07.2014 16:03, schrieb Michael Biebl:
 I can not reproduce this but I have to add that my host is running
 Debian sid with 204-14. The container was created as per your instructions.

 Have you bind-mounted /run or /dev/(shm) into the container?

 Actually, this is most likely a kernel issue.
 [...]
 Please update your kernel to the version from backports if you want to
 run systemd-nspawn and report back.
 
 Now I am running 3.12.9-1~bpo70+1 kernel and I cannot log into
 container. All I get is:
 
 login[96]: FAILED LOGIN (1) on '/dev/console' FOR 'root', System error
 
 Tomorrow I will try 3.14.

 I've setup a test-environment with 3.12 as kernel and could reproduce
 your issue. An upgrade to 3.14 did fix it for me.

Indeed, 3.14.7-1~bpo70+1 works fine. Do you think I should report
problems with 3.12?

-- 
Łukasz Stelmach
Samsung RD Institute Poland
Samsung Electronics


pgpNBGuhxDD9v.pgp
Description: PGP signature


Bug#754184: systemd: poweroff shuts down systemd-nspawn-ed container

2014-07-09 Thread Michael Biebl
Am 09.07.2014 10:20, schrieb Łukasz Stelmach:
 It was 2014-07-08 wto 21:34, when Michael Biebl wrote:
 Am 08.07.2014 17:50, schrieb Łukasz Stelmach:
 It was 2014-07-08 wto 16:29, when Michael Biebl wrote:
 Am 08.07.2014 16:03, schrieb Michael Biebl:
 I can not reproduce this but I have to add that my host is running
 Debian sid with 204-14. The container was created as per your 
 instructions.

 Have you bind-mounted /run or /dev/(shm) into the container?

 Actually, this is most likely a kernel issue.
 [...]
 Please update your kernel to the version from backports if you want to
 run systemd-nspawn and report back.

 Now I am running 3.12.9-1~bpo70+1 kernel and I cannot log into
 container. All I get is:

 login[96]: FAILED LOGIN (1) on '/dev/console' FOR 'root', System error

 Tomorrow I will try 3.14.

 I've setup a test-environment with 3.12 as kernel and could reproduce
 your issue. An upgrade to 3.14 did fix it for me.
 
 Indeed, 3.14.7-1~bpo70+1 works fine. Do you think I should report
 problems with 3.12?

I'm not sure it's worth it. After all, the kernel team already provides
a 3.14 backport so they are unlikely to spend time on the 3.12 backports
kernel.

Are you ok with closing this bug report? I don't think there is anything
to do from the systemd side here.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#754184: systemd: poweroff shuts down systemd-nspawn-ed container

2014-07-09 Thread Łukasz Stelmach
It was 2014-07-09 śro 13:24, when Michael Biebl wrote:
 Am 09.07.2014 10:20, schrieb Łukasz Stelmach:
 It was 2014-07-08 wto 21:34, when Michael Biebl wrote:
 Am 08.07.2014 17:50, schrieb Łukasz Stelmach:
 It was 2014-07-08 wto 16:29, when Michael Biebl wrote:
 Am 08.07.2014 16:03, schrieb Michael Biebl:
 I can not reproduce this but I have to add that my host is running
 Debian sid with 204-14. The container was created as per your 
 instructions.

 Have you bind-mounted /run or /dev/(shm) into the container?

 Actually, this is most likely a kernel issue.
 [...]
 Please update your kernel to the version from backports if you want to
 run systemd-nspawn and report back.

 Now I am running 3.12.9-1~bpo70+1 kernel and I cannot log into
 container. All I get is:

 login[96]: FAILED LOGIN (1) on '/dev/console' FOR 'root', System error

 Tomorrow I will try 3.14.

 I've setup a test-environment with 3.12 as kernel and could reproduce
 your issue. An upgrade to 3.14 did fix it for me.
 
 Indeed, 3.14.7-1~bpo70+1 works fine. Do you think I should report
 problems with 3.12?

 I'm not sure it's worth it. After all, the kernel team already provides
 a 3.14 backport so they are unlikely to spend time on the 3.12 backports
 kernel.

 Are you ok with closing this bug report? I don't think there is anything
 to do from the systemd side here.

Yes. Thak you for your attention and assistance.

-- 
Łukasz Stelmach
Samsung RD Institute Poland
Samsung Electronics


pgp0Aw56JbpvR.pgp
Description: PGP signature


Bug#754184: systemd: poweroff shuts down systemd-nspawn-ed container

2014-07-08 Thread Michael Biebl
Am 08.07.2014 15:01, schrieb Łukasz Stelmach:
 Package: systemd
 Version: 204-14~bpo70+1
 Severity: normal
 
 Dear Maintainer,
 
 I want to run systemd in a container on my desktop. I installed a
 minimal debian system in a directory (debootstrap) and started a
 container in it. Much to my surprise when I wanted to shutdown the
 container with the poweroff command my host went down.
 
 This might a problem with systemd, however, I dare to start reporting it
 here.
 
 I use 204-14 in the container (testing) and 204-14~bpo70+1 on my host.
 
 Steps to reproduce
 
 1. debootstrap testing --exclude=sysvinit --include=systemd-sysv,systemd 
 ./debian
 2. cd debian
 3. systemd-nspawn -b
 4. [log in as root]
 5. poweroff (or systemctl poweroff)

I can not reproduce this but I have to add that my host is running
Debian sid with 204-14. The container was created as per your instructions.

Have you bind-mounted /run or /dev/(shm) into the container?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#754184: systemd: poweroff shuts down systemd-nspawn-ed container

2014-07-08 Thread Michael Biebl
Am 08.07.2014 16:03, schrieb Michael Biebl:
 I can not reproduce this but I have to add that my host is running
 Debian sid with 204-14. The container was created as per your instructions.
 
 Have you bind-mounted /run or /dev/(shm) into the container?

Actually, this is most likely a kernel issue.
The kernel in wheezy (3.2.0) is too old to properly handle a reboot
request when using namespaces.

Upstream (kay) pointed to [1] and [2].


Please update your kernel to the version from backports if you want to
run systemd-nspawn and report back.



Michael

[1]
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/kernel/pid_namespace.c#n287
[2]
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cf3f8921
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#754184: systemd: poweroff shuts down systemd-nspawn-ed container

2014-07-08 Thread Łukasz Stelmach
It was 2014-07-08 wto 16:29, when Michael Biebl wrote:
 Am 08.07.2014 16:03, schrieb Michael Biebl:
 I can not reproduce this but I have to add that my host is running
 Debian sid with 204-14. The container was created as per your instructions.
 
 Have you bind-mounted /run or /dev/(shm) into the container?

 Actually, this is most likely a kernel issue.
[...]
 Please update your kernel to the version from backports if you want to
 run systemd-nspawn and report back.

Now I am running 3.12.9-1~bpo70+1 kernel and I cannot log into
container. All I get is:

login[96]: FAILED LOGIN (1) on '/dev/console' FOR 'root', System error

Tomorrow I will try 3.14.
-- 
Łukasz Stelmach
Samsung RD Institute Poland
Samsung Electronics


pgpF6uZbotDRy.pgp
Description: PGP signature


Bug#754184: systemd: poweroff shuts down systemd-nspawn-ed container

2014-07-08 Thread Michael Biebl
Am 08.07.2014 17:50, schrieb Łukasz Stelmach:
 It was 2014-07-08 wto 16:29, when Michael Biebl wrote:
 Am 08.07.2014 16:03, schrieb Michael Biebl:
 I can not reproduce this but I have to add that my host is running
 Debian sid with 204-14. The container was created as per your instructions.

 Have you bind-mounted /run or /dev/(shm) into the container?

 Actually, this is most likely a kernel issue.
 [...]
 Please update your kernel to the version from backports if you want to
 run systemd-nspawn and report back.
 
 Now I am running 3.12.9-1~bpo70+1 kernel and I cannot log into
 container. All I get is:
 
 login[96]: FAILED LOGIN (1) on '/dev/console' FOR 'root', System error
 
 Tomorrow I will try 3.14.

I've setup a test-environment with 3.12 as kernel and could reproduce
your issue. An upgrade to 3.14 did fix it for me.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature