Re: [Devel] https://bugs.openvz.org/browse/OVZ-6834 CUDA in container

2016-12-14 Thread Thomas Hoberg
Just one correction: Please forget about /proc/driver appearing as a file, a mistake a keep repeating, sorry! Am 14.12.2016 um 19:15 schrieb Thomas Hoberg: Hi Andrey, thanks a lot for your feedback! Ok, now I'm beginning to understand what's going on here... OpenVZ is "hijacking" the sticky

Re: [Devel] https://bugs.openvz.org/browse/OVZ-6834 CUDA in container

2016-12-14 Thread Thomas Hoberg
Hi Andrey, thanks a lot for your feedback! Ok, now I'm beginning to understand what's going on here... OpenVZ is "hijacking" the sticky bits on /proc dir entries to decide if it should be replicated into containers... ...while CGROUP, Docker, LXC etc. just plain copy everything (except the

Re: [Devel] https://bugs.openvz.org/browse/OVZ-6834 CUDA in container

2016-12-13 Thread Andrey Ryabinin
On 12/13/2016 05:57 PM, Andrey Ryabinin wrote: > Access to proc directories is slightly different. We show directory in > container iff it sticky bit is set. > You can set sticky bit via chmod (it's forbidden for proc entries in OpenVZ > kernel, I dunno why), > but you can change the source li

Re: [Devel] https://bugs.openvz.org/browse/OVZ-6834 CUDA in container

2016-12-13 Thread Andrey Ryabinin
On 12/12/2016 03:58 PM, Thomas Hoberg wrote: > Hi Andrey, > > I'm very sorry to contact you directly, but I've run out of options to help > myself. > > I am trying to get CUDA programs to run inside OpenVZ containers (they > already run on Docker containers on the host) and my problem is that t