On 12/16/2010 04:07 AM, Trent W. Buck wrote: > t...@cybersource.com.au (Trent W. Buck) > writes: > > >> Serge Hallyn<serge.hal...@canonical.com> >> writes: >> >> >>> You have: >>> >>> lxc.cgroup.devices.allow = c 1:3 rwm >>> lxc.cgroup.devices.allow = c 1:5 rwm >>> lxc.cgroup.devices.allow = c 1:8 rwm >>> lxc.cgroup.devices.allow = c 1:9 rwm >>> lxc.cgroup.devices.allow = c 4:* rwm >>> lxc.cgroup.devices.allow = c 5:0 rwm >>> lxc.cgroup.devices.allow = c 5:1 rwm >>> lxc.cgroup.devices.allow = c 5:2 rwm >>> lxc.cgroup.devices.allow = c 136:* rwm >>> lxc.cgroup.devices.allow = c 254:0 rm >>> >>> is your /dev/omega/squid device perhaps a blacklisted device? >>> >> Hmm, I thought lxc.cgroup.devices applied AFTER lxc.mount.entry. >>
Hmm, the lxc.cgroup is applied before the mount entry in the 0.7.2 version but that was changed and is now applied after the mount entries in the 0.7.3 version. >> I'll investigate -- if that the issue, I'll just have to stick to bind >> mounts and mount everything in the host OS in advance, because I know of >> no way to guarantee static major:minor allocation of stuff like hard >> disks and LVM LVs. >> > PS: you were right, if I add "lxc.cgroup.devices.allow = b 251:12 rwm", > the container starts up just fine, where > > r...@omega:~# ls -lids /dev/mapper/omega-squid > 4006939 0 brw-rw---- 1 root disk 251, 12 2010-12-15 19:58 > /dev/mapper/omega-squid > ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
