it is a bug introduced in 2.1.0 - i've just copied you on a patch that should fix it. If possible, it'd be good if you can build with that patch and report whether it works for you
After patch, container pass mount phase. But crash somewhere later: ---------------------------------------------------------------------------- 2016-08-11 14:54:03.728+0000: 1: debug : lxcContainerMountAllFS:1625 : Mounting '(null)' -> '/dev/shm' 2016-08-11 14:54:03.904+0000: 6713: debug : lxcContainerWaitForContinue:418 : Got continue on fd 11 0 2016-08-11 14:54:03.904+0000: 6713: error : virLXCControllerRun:2439 : error receiving signal from container: Input/output error 2016-08-11 14:54:03.904+0000: 6713: debug : virFileClose:102 : Closed fd 9 2016-08-11 14:54:03.904+0000: 6713: debug : virFileClose:102 : Closed fd 11 2016-08-11 14:54:03.904+0000: 6713: debug : virProcessAbort:167 : aborting child process 6714 2016-08-11 14:54:03.904+0000: 6713: debug : virProcessAbort:172 : process has ended: fatal signal 11 Failure in libvirt_lxc startup: error receiving signal from container: Input/output error ---------------------------------------------------------------------------- After remove from config section <filesystem type='ram', container started, but /dev/shm use all memory from hardware node: [root@tst2 ~]# df | grep shm tmpfs 32849396 0 32849396 0% /dev/shm I found another way to limit /dev/shm, inside container change /etc/fstab next way: -none /dev/shm tmpfs nosuid,nodev 0 0 +none /dev/shm tmpfs nosuid,nodev,size=512M 0 0 b.r. Maxim Kozin