Understandable; thanks for your assistance in this. I don’t have any 12th-gen Intel hardware to test with myself.
I’m kinda struggling to see the broader use case here. I thought this was about running TrueNAS as the hypervisor with SR-IOV, but you seem to want to keep your hypervisor?
Hypervisor → TrueNAS VM → Container that uses iGPU is possible without SR-IOV if you passthrough your entire iGPU to the TrueNAS VM
But I’m assuming you can’t do that because you also have a different VM that also needs the iGPU, so you installed the experimental DKMS on both the hypervisor and this VM.
Wouldn’t it be wiser to just spin up yet another VM with the DKMS to run your container instead of doing it in TrueNAS? Is this all just to bypass the virtual network and have raw access to the data in TrueNAS from the container? I think you’ll find that NFS, SMB and iSCSI are plenty fast for any such need.
It’d be safer to wait for/contribute for the support to be provided by the mainline xe driver, in my opinion.
By the same logic, truenas scale is not needed. After all, truenas core exists. Anything you want that can’t be achieved by truenas core, can be achieved by spinning up a Linux VM.
I believe the intention has been clearly communicated, and I don’t intend to start an argument about all the details.