Description of problem: It appears that systemd-nspawn doesn't work on s390/s390x. The clone() fails because the signature of the raw system call is slightly different on 390/s390x. Since the order of the first and second arguments is reversed it gets invoked with a bogus value of the child_stack pointer and segfaults. The corresponding patch has been accepted upstream: http://cgit.freedesktop.org/systemd/systemd/commit/?id=60e1651a31c9c0ed1caef1a63f5e3a87156b0b1e Version-Release number of selected component (if applicable): systemd-216-12.fc21.s390x How reproducible: always Steps to Reproduce: systemd-nspawn -D mycontainer Actual results: strace: clone(Process 1552 attached child_stack=0x2c020011, flags=) = 1552 [pid 1552] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_errno=1224498, si_addr=0x2c020000} --- Expected results: Spawning container mycontainer on /path/to/mycontainer. Additional info: I think every s390x/s390 Fedora version that has systemd is affected. Fortunately it's easy to fix.
After rebuilding the systemd-216-12 package with the patch applied on s390x I'm able to successfully spawn a namespace container.
systemd-216-13.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/systemd-216-13.fc21
Package systemd-216-13.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-216-13.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-17330/systemd-216-13.fc21 then log in and leave karma (feedback).
Yep, systemd-nspawn of systemd-216-13.fc21 works for me on s390x. Thanks! Are there any plans on adding the patch to the systemd provided for Fedora 20 as well?
Yes, I plan to do a big update with backported fixes, including this one. It may take a while, though.
systemd-216-13.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
F20 fix: http://pkgs.fedoraproject.org/cgit/systemd.git/commit/?h=f20&id=e0c0dfb92028b2139f8bbf9da048e0e05089ea64
systemd-208-29.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-29.fc20
Package systemd-208-29.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-208-29.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-0254/systemd-208-29.fc20 then log in and leave karma (feedback).
systemd-208-29.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.