On 11/04/2016 04:47 PM, Lennart Poettering wrote:
> On Fri, 04.11.16 11:12, c...@endlessnow.com (c...@endlessnow.com) wrote:
>
>>> On Thu, Nov 03, 2016 at 04:01:15PM -0700, c...@endlessnow.com wrote:
>> >> so I'm using CentOS 7, and we're mounting a disk from our
>> iSCSI
>> >> SAN and then
hi!
I am using slurm to manage GPU resources. On a host with several GPUs installed
a user gets only access to the GPUs he asks slurm for. This is implemented by
using the devices cgroup controller. For each job slurm starts, all devices
which are not allowed get denied using cgroup devices.den
On Mon, Nov 07, 2016 at 01:11:14PM +0100, Michal Privoznik wrote:
> On 07.11.2016 10:17, Daniel P. Berrange wrote:
> > On Fri, Nov 04, 2016 at 08:47:34AM +0100, Michal Privoznik wrote:
> >> Hey udev developers,
> >>
> >> I'm a libvirt developer and I've been facing an interesting issue
> >> recentl
On 07.11.2016 10:17, Daniel P. Berrange wrote:
> On Fri, Nov 04, 2016 at 08:47:34AM +0100, Michal Privoznik wrote:
>> Hey udev developers,
>>
>> I'm a libvirt developer and I've been facing an interesting issue
>> recently. Libvirt is a library for managing virtual machines and as such
>> allows ba
On Fri, Nov 04, 2016 at 08:47:34AM +0100, Michal Privoznik wrote:
> Hey udev developers,
>
> I'm a libvirt developer and I've been facing an interesting issue
> recently. Libvirt is a library for managing virtual machines and as such
> allows basically any device to be exposed to a virtual machine
On 04.11.2016 17:32, Martin Pitt wrote:
> Hello Michal,
>
> Michal Privoznik [2016-11-04 8:47 +0100]:
>> That means that whenever a VM is being started up, libvirtd (our
>> daemon we have) relabels all the necessary paths that QEMU process
>> (representing VM) can touch.
>
> Does that mean it's
