Quoting Daniel Lezcano (daniel.lezc...@free.fr): > fedora 15 has a patched kernel with utrace.
By patched, you mean utrace is not upstream? > Are we sure, utrace is pid namespace aware ? I've not looked at it, no. > My natty container booted on fedora 15 but is stuck at: > > \_ lxc-start -n natty -l DEBUG -o /dev/pts/0 > \_ /sbin/init > \_ /sbin/plymouthd --mode=boot --attach-to-session > \_ /sbin/plymouthd --mode=boot --attach-to-session Does this only happen with my patches? > pidof /sbin/plymouthd > 6224 6222 > > cat /proc/6224/stack > [<ffffffff81098ad9>] utrace_stop+0x128/0x181 > [<ffffffff81098b9c>] finish_resume_report+0x6a/0xb2 > [<ffffffff810999ea>] utrace_get_signal+0x460/0x5a6 > [<ffffffff81064d0a>] get_signal_to_deliver+0x102/0x3a9 > [<ffffffff81008f43>] do_signal+0x69/0x67f > [<ffffffff8100959a>] do_notify_resume+0x28/0x83 > [<ffffffff81009e90>] int_signal+0x12/0x17 > [<ffffffffffffffff>] 0xffffffffffffffff > > cat /proc/6222/stack > [<ffffffff8112882d>] pipe_wait+0x61/0x7c > [<ffffffff81128fe6>] pipe_read+0x344/0x3c1 > [<ffffffff811212b2>] do_sync_read+0xbf/0xff > [<ffffffff81121919>] vfs_read+0xa9/0xf0 > [<ffffffff811219aa>] sys_read+0x4a/0x6e > [<ffffffff81009bc2>] system_call_fastpath+0x16/0x1b > [<ffffffffffffffff>] 0xffffffffffffffff > > > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
