[systemd-devel] systemd-nspawn 208 fails to mount special filesystems

[Leho Kraav]

Hi all


I've been trying to solve this for several hours over multiple days now 
and am at the end of my wits, so asking for help.

One machine, my laptop, boots "systemd-nspawn -D /srv/canister -b" 
perfectly fine. All services load OK in a blink of an eye, login prompt 
appears, all is good. Everything works both for 3.10 and 3.14 kernel 
I've booted. Config http://bpaste.net/show/290940/

My real target, the server, gets stuck mounting special file systems 
like "POSIX Message Queue" etc. With special filesystem mounts taking 
enormous amounts of time to finally display "failed", getting to login 
prompt can take hours, so I just have to pkill -HUP the nspawn process. 
Server runs 3.14-pf, config visible http://bpaste.net/show/290933/
As far as I can tell I have the same kernel configuration for things 
that look relevant.

Everything is booted audit=0.

/srv/canister filesystem is identical for the testing purposes, so that 
to my mind mostly leaves the difference to possibly some magic kernel 
configuration item that I don't know to select on the server side.

Or what else should I look at? What could be another reason for the 
special filesystems not to properly mount?

Gentoo stable is currently 208, so I have an option to try 212 unstable, 
but I'd rather not for now, while I can see everything is capable of 
working perfectly fine on the laptop with 208.

Thanks for any tips.