Tuomas Katila

I followed instructions from the audit entry: ``` sudo ausearch -c 'intel_gpu_devic' --raw | audit2allow -M intelgpudevice sudo semodule -X 300 -i intelgpudevice.pp ``` That seems to allow device plugin...

@mregmi do you happen to know the container-selinux version?

Well, there are also items like "Intel FPGA test tool" in the extensions. So GPU fakedev would be fine in that sense. We're also missing the xpumanager-sidecar from the list.

> > Well, there are also items like "Intel FPGA test tool" in the extensions. So GPU fakedev would be fine in that sense. > > Maybe there should be...

Hi @brgavino The GPU plugin is supposed to be run on homogeneous nodes (only one type of GPU). As both cards appear as same resource (`gpu.intel.com/i915`), you wouldn't be able...

If you are referring to GPU Aware Scheduling with GAS, it states in its README that it expects cluster to be homogeneous. I'm sorry, but I don't think there are...

> One way that we have considered this is to present a stand-in, such as requesting `memory.max` that will be larger than one card/tile type. For the case of `sharedDevNum=1`,...

> Correct me if I got this wrong - The problem seems a limitation of the naming of Flex GPU in the NFD. It cannot tell two types (or more...

> It does look like the DRA driver would be a better fit in the long term. Based on the discussion here, it seems that DRA is the preferred path...

> Regarding your solution -- a "pci device id" to "resource name" mapping, do you mean something like pci_device_id to "gpu_type" mapping? Yes. Plugin would read device's PCI ID and...