Re: [lxc-users] LXC not starting with already mounted LV as read-only mount

2014-11-26 Thread Claudio Kuenzler
I applied the patch but it does not work for the read only mount. lxc-start 1416993491.172 INFO lxc_conf - conf.c:check_autodev:3821 - Autodev not required. lxc-start 1416993491.172 ERRORlxc_conf - conf.c:mount_entry:1916 - Device or resource busy - failed to mount '/dev/vglxc/

Re: [lxc-users] LXC not starting with already mounted LV as read-only mount

2014-11-26 Thread Claudio Kuenzler
I made a couple of mistakes in my modified patch - so please ignore that.But the basic idea of it was to handle special mount flags (in this case RDONLY) before it hits if (mount(fsname, target, fstype, mountflags & ~MS_REMOUNT, data)) Will be glad to test additional patches for you. On Wed, Nov

Re: [lxc-users] iptables-persistent not loading rules

2014-11-26 Thread Serge Hallyn
Quoting Sergey (serg...@gmail.com): > Hi, > > Is your container unprivileged? > I'm experiencing the same issue with unprivileged container on ubuntu > trusty. > > I've tried to investigate it with strace. There is the log: > > # strace iptables-save 2>&1 |tail > > mprotect(0x7fdd75e12000, 4096,

Re: [lxc-users] iptables-persistent not loading rules

2014-11-26 Thread Eric W. Biederman
Serge Hallyn writes: > Quoting Sergey (serg...@gmail.com): >> Hi, >> >> Is your container unprivileged? >> I'm experiencing the same issue with unprivileged container on ubuntu >> trusty. >> >> I've tried to investigate it with strace. There is the log: >> >> # strace iptables-save 2>&1 |tail

[lxc-users] blkio.wieght not working

2014-11-26 Thread Nishant Agrawal
Hi Guys, I am trying to assign weighted limit to multiple containers on blkio but I don't see the effect after applying. Throttling seems to be working but weighted share does not, any help is appreciated. I have checked that host kernel is using CFQ scheduling. I am using 3.13.0.32 kernel (

Re: [lxc-users] LXC not starting with already mounted LV as read-only mount

2014-11-26 Thread Fajar A. Nugraha
I'm pretty sure it's NOT lxc's fault. For starters, have you tried testing the same (i.e. mount rw, and then mount again ro) in normal, non-lxc setup? That does not work, and does indeed fail with a message like this mount: /dev/zd208 already mounted or /mnt/tmp2 busy mount: according to mtab, /d