Enable & Using vGPU Passthrough

This gist is almost entirely not unlike Derek Seaman's awesome blog:

Proxmox VE 8: Windows 11 vGPU (VT-d) Passthrough with Intel Alder Lake

As such please refer to that for pictures, here i will capture the command lines I used as i sequence the commands a little differently so it makes more logic to me.

This gists assumes you are not running ZFS and are not passing any other PCIE devices (as both of these can require addtional steps - see Derek's blog for more info)

Note:i made no changes to the BIOS defaults on the Intel Nuc 13th Gen. This just worked as-is.

this gist is part of this series

Preparation

Install Build Requirements

apt update && apt install pve-headers-$(uname -r)
apt install git sysfsutils dkms build-* unzip -y

Install Other Drivers / Tools

This allow you to run vainfo, intel_gpu_top for testing and non-free versions of the encoding driver - without this you will not AFAIK be able to encoding with this GPU. This was missed in EVERY guide i saw for this vGPU, so not sure, but i had terrible issues until i did this.

edits the sources list with nano /etc/apt/sources.list

add the following lines:

#non-free firmwares
deb http://deb.debian.org/debian bookworm non-free-firmware

#non-free drivers and components
deb http://deb.debian.org/debian bookworm non-free

and save the file

apt update && apt install intel-media-va-driver-non-free intel-gpu-tools vainfo

This next step copies a driver missing on proxmox installs and will remove the -2 error for this file in dmesg.

wget -r -nd -e robots=no -A '*.bin' --accept-regex '/plain/' https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915/adlp_dmc.bin

cp adlp_dmc.bin /lib/firmware/i915/

Compile and Install the new driver

Clone github project

cd ~
git clone https://github.com/strongtz/i915-sriov-dkms.git

modify dkms.conf

cd i915-sriov-dkms
nano dkms.conf

change these two lines as follows:

PACKAGE_NAME="i915-sriov-dkms"
PACKAGE_VERSION="6.5"

save the file

Compile and Install the Driver

cd ~
mv i915-sriov-dkms/ /usr/src/i915-sriov-dkms-6.5
dkms install --force -m i915-sriov-dkms -v 6.5

and use dkms status to verify the module is now installed

Modify grub

edit the grub fle with nano /etc/default/grub

change this line in the file

GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt i915.enable_guc=3 i915.max_vfs=7"

note: if you have already made modifications to this line in your grub file for other purposes you should also still keep those items

finally run

update-grub
update-initramfs -u

Find PCIe Bus and update sysfs.conf

use lspci | grep VGA t find the bus number

you should see something like this:

root@pve2:~# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04)

take the number on the far left and add to the sysfs.conf as follows - note all the proceeding zeros on the bus path are needed

echo "devices/pci0000:00/0000:00:02.0/sriov_numvfs = 7" > /etc/sysfs.conf

REBOOT

Testing On Host

check devices

check devices with dmesg | grep i915

the last two lines should read as follows:

[    7.591662] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.7 on minor 7
[    7.591818] i915 0000:00:02.0: Enabled 7 VFs

if they don't then check all steps carefully

Validate with VAInfo

validate with vainfo you should see no errors (note this needs the drivers and tool i said to install at the top) and vainfo --display drm --device /dev/dri/cardN where N is a number from 0 to 7 - this will show you the acceleration endpoints for each VF

Check you can monitor the VFs - if not you have issues

monitor any VF renderer in real time with intel_gpu_top -d drm:/dev/dri/renderD128 there is one per VF - to see them all use ls -l /dev/dri

Configure vGPU Pool in Proxmox

navigate to Datacenter > Resource Mappings
click add in PCI devices
name the pool something like vGPU-Pool
map all 7 VFs for pve 1 but NOT the root device i.e 0000:00:02.x not 0000:00:02
click create
on the created pool lcikc the plus button next to vGPU-Pool
select mapping on node = pve 2, ad all devices and click create
repeat for pve3

The pool should now look like this:

Note: machines with PCI pass through devices cannot be live migrated, they must be shutdown, migrated offline to the new node and then started.

EVERYTIME THE KERNEL IS UPDATED IN PROXMOX YOU SHOULD DO THE FOLLOWING

update the kernel using proxox ui
dkms install -m i915-sriov-dkms -v 6.5 --force
reboot

How to get working in a privileged container

wow this one is hard.... you can avoid the id mapping stuff by not using a privileged container...

Assumptions:

you have a debian 12 container, you added the non-free deb and have installed the non-free drivers as per the host instructions
you have run cat /etc/groups in the container and noted down the GID for render (lets call that CTRGID) and gid for video (lets call that CTVGID).
you have run cat /etc/groups in the container and noted down the GID for render (lets call that HSTRGID) and gid for video (lets call that HSTVGID). 5 that you have va info fully working

Create Container

create container privileged, with debian 12, starts it
apt update, apt upgrade, install non free drivers, vainfo and intel_gpu_top tools
add root to user and video groups (this will mean when we get to ID mapping you don't need to tart about with user mappings - only group ones)

usermod -a -G render root
usermod -a -G video root

shutdown container

Edit container conf file

These are stored in /etc/pve/lxc and have the VMID.conf anme
nano /etc/pve/lxc/VMID.conf

Add lxc device mapping

Here you add a line for the card uyou want and the rendere. Note if you map a VF (card) to a container it means that is hard mapped, if you have that VF in a pool for VMs please remove it from the pool (this means also these containers cannot be HA)

In the example below i chose card6 - which is renderD134 These are mapped into the container as card0 and renderD128 Change your numbers as per your own VF / card mappings

lxc.cgroup2.devices.allow: c 226:6 rwm
lxc.mount.entry: /dev/dri/card6 dev/dri/card0 none bind,optional,create=file

lxc.cgroup2.devices.allow: c 226:134 rwm
lxc.mount.entry: /dev/dri/renderD134 dev/dri/renderD128 none bind,optional,create=file

Add ID mapping (only needed in unprivileged)

add the following... and here it gets complex as it will vary based on the numbers you recorded earlier - let me try... the aim is to have a continguois block of mappings but the syntax is um difficult...

lxc.idmap: u 0 100000 65536
lxc.idmap: g 0 100000 CTVGID
lxc.idmap: g CTVGID HSTVGID 1
lxc.idmap: g CTVGID+1 1000{CTVGID+1} CTRGID-CTVGID-1
lxc.idmap: g CTRGID HSTVGID 1
lxc.idmap: g CTRGID+1 100{CTRGID+1} 65536-{CTRGID+1}

so as an example, these are my values:

        host > ct
video:    44 > 44
render:  104 > 106

this is what i added to my VMID.conf file (in my case /etc/pve/lxc/107.conf

lxc.idmap: u 0 100000 65536
lxc.idmap: g 0 100000 44
lxc.idmap: g 44 44 1
lxc.idmap: g 45 100045 61
lxc.idmap: g 106 104 1
lxc.idmap: g 107 100107 65429

add your two CT values to nano /etc/subgid (only needed in unprivileged)

in my case:

root:106:1
root:44:1

after this you should be able to start up the container and run vainfo and perform transcoding.

check permissions with ls -la /dev/dri it should look like this:

root@vGPU-debian-test:~# ls -la /dev/dri
total 0
drwxr-xr-x 2 root   root         80 Oct  7 00:22 .
drwxr-xr-x 7 root   root        500 Oct  7 00:22 ..
crw-rw-rw- 1 nobody video  226,   0 Oct  4 21:42 card0
crw-rw-rw- 1 nobody render 226, 128 Oct  4 21:42 renderD128

if the group names do not say video and render then you did something wrong

**Note: YYMV **

For example plex HW transcoded just fine on my system.

Emby on the otherhand seems to interrogate the kernel driver directly and gets the wrong answers - this is IMHO an issue with their detection logic not supporting this scenario.

Another example is intel_gpu_top which doesn't seem to work in this mode either - this is because it only works with the PMUs not the VFs (so somoene said)

Or maybe i just have no clue what i am doing, lol.

---work in progress 2023.10.6---

add vGPU to a Windows 11 or Server 2022 VM

boot VM without vGPU and display set to default
install VirtIO drivers
shutdown VM and change display to VirtIO-GPU
change CPU type to 'host'
Now add the vGPU pool as a PCI device
when creating a VM add a PCI device and add the poool as follows:

now boot into VM and install latest IrisXe drivers from intel
you should now have graphics acceleration availble to apps wether you connect by webcolse VNC, SPICE or an RDP client

From @rinze24:

If you follow the guide successfully, in Device Manager you will see:

Microsoft Basic Display Adapter - If you use Display in VM Settings
Intel iGPU - passthrough

You have 2 options (or more) to use your iGPU. Because Windows 11 decide on its own which graphics to use.

Setup Remote Desktop Connection in Windows 11 and set the display to none in VM Hardware settings.

Pro: No configuration per app, Responsive Connection.
Con: No proxmox console.

Inside Windows Set which graphics preference to use per application in Display Settings -> Graphics Settings-

Pro: Have proxmox console.
Con: Need to configure per application / program.

If you hit automatic repair loop at any point shutdown the machine and edit its conf file in /etc/pve/qemu-server and add args: -cpu Cooperlake,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,+vmx

scyto,

Thank you for this. I was able to get this working in my homelab. Just a couple quick questions..

at the very bottom of your guide you make a resource mapping in datacenter.. can we assume that you have 3 identical pve nodes in a cluster and you followed your guide on all three of them and that’s why you made a resource group like this?
If someone only has one pve node or has a cluster with disparate hardware on each node, this step isn’t useful and can be skipped, right? on the VM you just choose raw device instead of resource mapping to pass through a GPU
a VM can only use a GPU of its physical host, correct? you can resource map the iGPU on 3 different nodes and expect any node to be able to make use of any other node’s iGPU, right? that seems really bandwidth intensive and not like something you could do currently. also, kinda in line with question #1.. if this is true, then why bother making the resource mapping?

Just trying to understand why you did what you did.. thanks again though!

Author

scyto

commented

Oct 1, 2023

•

edited

good questions, i will preface by saying this gist is about vGPU (aka sharing GPU between containers and VMs simultaneously - NOT passthrough - where one dedicates a whole GPU to one container (which is what a lot of the tutorials seem to be - and to be clear if you want to run a windows gaming VM then this is what is needed - but then if gaming in that important run baremetal windows IMO).

yes all 3 nodes are the same - the reason for using the pool is say we have a VM on node 1 using VF1 - when that node moves to node 2 VF1 might already be in use - you want it to pick VF2 - but yes this requires the hardware to be near-identical - you might find it works for windows ok if say you are switching between different variants of the same card (i.e. they use the same driver - windows is pretty good at handling video cards. but if your app in windows isn't it will crash.
vGPU is great IMO even on a single node - because you can share the GPU between multiple running containers and VMs simultaneously (note while their may be 7 VFs i -believe- there are only two transcode engines in total.... on 13th Gen IrisiXE not sure ... haven't tested.. but this may mean only two containers/vms can use media acceleration at the same time, i also saw somewhere somone saying a 10th gen nuc may have had only one media acceleration engine - anyhoo key is to remember a GPU is collection of engines). So if you have disprate nodes but want more than CT/VM to access the GPU at the same time on that node - make each pool node specific.
yes a vm or CT can only use the gpu on its host - i didn't make a resource mapping (you are thinking of mapping A to 1 in a fixed way)- I made a flexible pool of 7 GPUs per host that can be distributed among up to 7 running VMs or CTs requiring no intervention on my part other than to say 'use the pool' - the rest i handled automagically.

Does that help?

I did this to play, i don't yet plan to use GPU in any CT or VM (my media stuff is on a separate Synology and i never have bothered to transcode) - i just wanted to be sure the capability is there and running fine if and when i need it :-)

Absolutely, that helps.. this is all new to me. Just to give you some background.. I had to go down this path because I upgraded my proxmox host from a 7th gen hp mini to a 12th gen hp mini that’s absolutely maxed out and also has a 10g nic. I’ve had both boxes for some time, but I just recently decided to try out jellyfin and well, then I started reading and wanted to play with transcoding too, even though I don’t really need it as most of my downstream devices can playback my media library just fine. However, I got to reading and I was finally able to do split iGPU passthrough on the 7th gen, but then I figured.. may as well bite the bullet and move everything to the 12th gen since that box is maxed out on ram, storage, network, etc. Well, that’s when I hit a few walls. First, I came to find out iGPU passthrough on 12th gen is totally different than 7th gen. Using your guide and the README on the dkms SRIOV module page I was able to cobble together how to get it working for the most part. Then, I hit another brick wall. The VM I had running on the old host was using a legacy bios instead of UEFI and from what I understand you can’t really passthrough PCIe on legacy bios. Anyhow, no big deal, I guess? It took me a full day, but I was able to make a new UEFI VM on the 12th gen host and OF COURSE I used debian again, so that meant I had to completely recompile that VM’s kernel for the SRIOV module. 🤦🏻‍♂️Hours later and after getting my docker environment copied over I was able to get Intel QSV working inside my jellyfin docker container on the VM. Then I decided to rebuild the 7th gen host and make a cluster between the two and blah blah blah. Anyhow, when I got to the part about making a resource pool on the 7th gen, of course it’s not really like on 12th gen. I don’t believe you can make 7 VFs, just one available I believe. 😆

I do still have one question.. on the 12th gen VM, if I install intel-media-va-driver-non-free intel-gpu-tools intel_gpu_top doesn’t exactly work, it can’t ever detect any render engines, no matter how you try to specify them. (As I’m typing this reply I investigated a little further and I think it’s because the VF passed through to the VM doesn’t support PMU, whatever that means.. also not sure why it’s not supported). At any rate, the intel gpu tools aren’t that important.. what is.. is that things are working, both on the 7th gen and 12th gen and it was partially thanks to this gist.

Author

scyto

commented

Oct 4, 2023

•

edited

because the VF passed through to the VM doesn’t support PMU

what kernel is your guest on? IIRC the driver doesn't support 6.5 or 6.4 at the moment.
and don't forget to specify the device option for both vainfo and intel_gpu_top

AFAIK it isn't the PMU thing, because its the same message on the host....

[    8.601167] i915 0000:00:02.7: enabling device (0000 -> 0002)
[    8.601178] i915 0000:00:02.7: Running in SR-IOV VF mode
[    8.601304] i915 0000:00:02.7: [drm] GT0: GUC: interface version 0.1.0.0
[    8.601554] i915 0000:00:02.7: [drm] VT-d active for gfx access
[    8.601567] i915 0000:00:02.7: [drm] Using Transparent Hugepages
[    8.601924] i915 0000:00:02.7: [drm] GT0: GUC: interface version 0.1.0.0
[    8.602104] i915 0000:00:02.7: GuC firmware PRELOADED version 1.0 submission:SR-IOV VF
[    8.602106] i915 0000:00:02.7: HuC firmware PRELOADED
[    8.604320] i915 0000:00:02.7: [drm] Protected Xe Path (PXP) protected content support initialized
[    8.604324] i915 0000:00:02.7: [drm] PMU not supported for this GPU.
[    8.604368] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.7 on minor 7
[    8.604481] i915 0000:00:02.0: Enabled 7 VFs
[ 4577.601707] i915 0000:00:02.0: VF7 FLR
[ 4578.706506] i915 0000:00:02.0: VF7 FLR
[ 4578.871028] i915 0000:00:02.0: VF7 FLR
[ 4663.566881] i915 0000:00:02.0: VF7 FLR
[ 4663.899580] i915 0000:00:02.0: VF7 FLR
[ 4664.998613] i915 0000:00:02.0: VF7 FLR
[ 4665.168592] i915 0000:00:02.0: VF7 FLR

I have N305 with Intel UHD, i successfully pass-through the iGPU to Windows 11 VM. With

i915-sriov-dkms/6.5
Kernel Version: 6.2.16-15-pve

Note: after editing /etc/apt/sources.list you need to apt update for new package.

For Windows 11 VM

If you follow the guide successfully, in Device Manager you will see:

Microsoft Basic Display Adapter - If you use Display in VM Settings
Intel iGPU - passthrough

You have 2 option (or more) to use your iGPU. Because Windows 11 decide on its own which graphics to use.

Setup Remote Desktop Connection in Windows 11 and set the display to none in VM Hardware settings.
This will force the Windows to use the iGPU.
Pro: No configuration per app, Responsive Connection.
Con: No proxmox console.
Inside Windows Set which graphics preference to use per application in Display Settings -> Graphics Settings
Pro: Have proxmox console.
Con: Need to configure per application / program.

Author

@rinze24 thanks, added

This works great with RDP but I'm having trouble getting Parsec/Moonlight to work. My use case is remote gaming so RDP just doesn't cut it. Parsec has virtual display driver but that doesn't work either. How would I go about passing the full iGPU & HDMI port through without Error43?

Author

@oozeyyy based on my playing with parsec on real machines it always seems to need a real HDMI device plugged in.
I am not sure what that means for using parsec in a VM with no real HDMI.
The proxmox forum has upto date instructions for passing a whole card through to a single VM (this is not vGPU - it is passthrough).
I did a quick google, does this help? https://www.reddit.com/r/MoonlightStreaming/comments/rzpcpc/moonlight_streaming_without_monitor_no_dummy_plug/

@scyto I tried this earlier today and unfortunately no dice, this driver is similar to what Parsecs VDD is supposed to achieve however neither seem to work for me. I've tried hooking up a display and even using a dummy dongle however I think because I'm unable to fully passthrough the iGPU without an error43, the HDMI outputs aren't working. Sometimes I'll have the Proxmox console outputting via HDMI and other times just no signal.

I'll dig around a little bit more in the forums, thank you for your reply.

@oozeyyy what CPU type are you using inside your VM?
Make sure it is host, as the Intel GPU driver won't work with other CPU types and will produce error 43.

Maybe that doesn't help you and you already run host type, but I just thought I'd mention it as a debugging step.

@w-marco My CPU type is host, I configured the VM according to Derek Seaman's blog post linked above. I appreciate you trying, I think I'm going to have to invest in a GPU at this point.

I've been trying to get a Jellyfin lxc with hardware acceleration, using your example above, ffmpeg would never initialize. What I finally did was both to not rename Card6 to Card0, and renderD135 to renderD128, along with a different idmap and that worked!

Using python script from (https://github.com/ddimick/proxmox-lxc-idmapper), got the following idmap config, using my input of:

Container: render = 106, video = 44
Host: render=104, video = 44
then run python script ./run.py containeruid/containergid]=hostuid/hostgid (note: i used a raspi as it already had python loaded)
pi@raspberrypi:~ $ ./run.py 44=44 106=104 output below...

Add to /etc/pve/lxc/<container_id>.conf:
lxc.idmap: u 0 100000 44
lxc.idmap: g 0 100000 44
lxc.idmap: u 44 44 1
lxc.idmap: g 44 44 1
lxc.idmap: u 45 100045 61
lxc.idmap: g 45 100045 61
lxc.idmap: u 106 104 1
lxc.idmap: g 106 104 1
lxc.idmap: u 107 100107 65429
lxc.idmap: g 107 100107 65429

Add to /etc/subuid:
root:44:1
root:104:1

Add to /etc/subgid:
root:44:1
root:104:1

and finally, my lxc_id.conf file

arch: amd64
cores: 8
features: nesting=1
hostname: deb12
memory: 2048
net0: name=eth0,bridge=vmbr0,hwaddr=A6:F6:9F:60:42:1A,ip=dhcp,type=veth
ostype: debian
rootfs: local-lvm:vm-108-disk-0,size=80G
swap: 512
unprivileged: 1
lxc.cgroup2.devices.allow: c 226:7 rwm
lxc.mount.entry: /dev/dri/card7 dev/dri/card7 none bind,optional,create=file
lxc.cgroup2.devices.allow: c 226:135 rwm
lxc.mount.entry: /dev/dri/renderD135 dev/dri/renderD135 none bind,optional,create=file
lxc.idmap: u 0 100000 65536
lxc.idmap: g 0 100000 44
lxc.idmap: g 44 44 1
lxc.idmap: g 45 100045 61
lxc.idmap: g 106 104 1
lxc.idmap: g 107 100107 65429

and finally, ran the ffmpeg initialization, which worked
/usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=va:/dev/dri/renderD135 -init_hw_device opencl@va
However, intel_gpu_top does not work on container, nor on host (on host will only work on renderD128). Like you said, work in progress...

Edit: HW = Minisforum NPB5 (i5-13500H), Proxmox 8.0.4

Author

scyto

commented

Oct 25, 2023

•

edited

I've been trying to get a Jellyfin lxc with hardware acceleration, using your example above, ffmpeg would never initialize. What I finally did was both to not rename Card6 to Card0, and renderD135 to renderD128, along with a different idmap and that worked!

yeah the idmapping is different on different hardware - you should find the logic i documented is the same as the mapping tool, i didnt use the tool as i wanted to understand it from first principles

i only every got emby working so doesn't surprise me you has success with jellyfin- the detection in emby is too clever for its own good...

The last 2 proxmox kernel updates errored. I think it happens when it tries to install the kernel, so even before I do the dkms install.... to get it to work again. I didn't save the error , it happened on the last 2 kernel updates. Proxmox stays on the old kernel and doesn't offer the updates anymore until a newer kernel comes out. (yes I did reboot)

Found this tutorial while I was looking for hardware acceleration for jellyfin LXC but it´s not working right now

Proxmox 8.0.4
CPU: Intel i3 N305
Kernel Version Linux 6.2.16-19-pve #1 SMP PREEMPT_DYNAMIC PMX 6.2.16-19 (2023-10-24T12:07Z)

Followed steps up to:

root@pve:~# dkms install --force -m i915-sriov-dkms -v 6.5
Sign command: /lib/modules/6.2.16-19-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Certificate or key are missing, generating self signed certificate for MOK...
Creating symlink /var/lib/dkms/i915-sriov-dkms/6.5/source -> /usr/src/i915-sriov-dkms-6.5

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.2.16-19-pve -j8 -C /lib/modules/6.2.16-19-pve/build M=/var/lib/dkms/i915-sriov-dkms/6.5/build KVER=6.2.16-19-pve..................(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.16-19-pve (x86_64)
Consult /var/lib/dkms/i915-sriov-dkms/6.5/build/make.log for more information.

The error:

root@pve:~# cat /var/lib/dkms/i915-sriov-dkms/6.5/build/make.log
DKMS make.log for i915-sriov-dkms-6.5 for kernel 6.2.16-19-pve (x86_64)
Mon Oct 30 10:14:56 PM -03 2023
make: Entering directory '/usr/src/linux-headers-6.2.16-19-pve'
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_driver.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_drm_client.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_config.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_getparam.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_hwmon.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_ioctl.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_irq.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_mitigations.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_module.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_params.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_pci.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_scatterlist.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_suspend.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_switcheroo.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_sysfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_utils.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/intel_device_info.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/intel_memory_region.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/intel_pcode.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/intel_pm.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/intel_region_ttm.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/intel_runtime_pm.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/intel_sbi.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/intel_step.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/intel_uncore.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/intel_wakeref.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/vlv_sideband.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/vlv_suspend.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/soc/intel_dram.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/soc/intel_gmch.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/soc/intel_pch.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_memcpy.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_mm.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_sw_fence.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_sw_fence_work.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_syncmap.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_user_extensions.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_ioc32.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_debugfs_params.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_display_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_pipe_crc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_pmu.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen2_engine_cs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen6_engine_cs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen6_ppgtt.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen7_renderclear.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen8_engine_cs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen8_ppgtt.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_breadcrumbs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_context.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_context_sseu.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_engine_cs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_engine_pm.o
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen8_ppgtt.c:103:12: warning: ‘gen12_pte_encode_shim’ defined but not used [-Wunused-function]
  103 | static u64 gen12_pte_encode_shim(dma_addr_t addr,
      |            ^~~~~~~~~~~~~~~~~~~~~
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_engine_user.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_execlists_submission.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_ggtt.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_ggtt_fencing.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_buffer_pool.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_clock_utils.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_engines_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_irq.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_mcr.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_pm.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_pm_irq.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_requests.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_sysfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gtt.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_llc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_lrc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_migrate.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_mocs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_ppgtt.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_rc6.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_region_lmem.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_renderstate.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_reset.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_ring.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_ring_submission.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_rps.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_sa_media.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_sseu.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_sseu_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_timeline.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_tlb.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_wopcm.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_workarounds.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/shmem_utils.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/sysfs_engines.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_ggtt_gmch.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen6_renderstate.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen7_renderstate.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen8_renderstate.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/gen9_renderstate.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_busy.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_clflush.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_context.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_create.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_dmabuf.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_domain.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_internal.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_object.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_lmem.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_mman.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_pages.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_phys.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_pm.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_region.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_shmem.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_shrinker.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_stolen.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_throttle.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_tiling.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_ttm.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_ttm_pm.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_userptr.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gem_wait.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gem/i915_gemfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_active.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_cmd_parser.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_deps.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_gem_evict.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_gem_gtt.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_gem_ww.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_gem.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_query.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_request.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_scheduler.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_trace_points.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_ttm_buddy_manager.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_vma.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_vma_resource.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_gsc_proxy.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_gsc_uc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_gsc_uc_heci_cmd_submit.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_ads.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_capture.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_log.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_log_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_rc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_huc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_huc_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_huc_fw.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_uc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_uc_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/intel_gsc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_sriov.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/i915_sriov_sysfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/iov/intel_iov.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/iov/intel_iov_debugfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/iov/intel_iov_event.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/iov/intel_iov_memirq.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/iov/intel_iov_provisioning.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/iov/intel_iov_query.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/iov/intel_iov_relay.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/iov/intel_iov_service.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/iov/intel_iov_state.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/gt/iov/intel_iov_sysfs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/hsw_ips.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_atomic.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_atomic_plane.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_audio.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_bios.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_bw.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_cdclk.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_color.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_combo_phy.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_connector.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_crtc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_crtc_state_dump.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_cursor.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_display.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_display_power.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_display_power_map.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_display_power_well.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dmc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dpio_phy.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dpll.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dpll_mgr.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dpt.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_drrs.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dsb.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_fb.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_fb_pin.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_fbc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_fdi.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_fifo_underrun.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_frontbuffer.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_global_state.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_hdcp.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_hotplug.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_hti.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lpe_audio.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_modeset_verify.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_modeset_setup.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_overlay.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_pch_display.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_pch_refclk.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_plane_initial.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_psr.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_quirks.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_sprite.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_tc.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_vblank.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_vga.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/i9xx_plane.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/skl_scaler.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/skl_universal_plane.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/skl_watermark.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_acpi.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_opregion.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_fbdev.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/dvo_ch7017.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/dvo_ch7xxx.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/dvo_ivch.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/dvo_ns2501.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/dvo_sil164.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/dvo_tfp410.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/g4x_dp.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/g4x_hdmi.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/icl_dsi.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_backlight.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_crt.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_cx0_phy.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_ddi.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_ddi_buf_trans.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_display_trace.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dkl_phy.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp_aux.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp_hdcp.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp_link_training.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp_mst.o
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp.c: In function ‘intel_dp_mst_hpd_irq’:
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp.c:3890:9: error: implicit declaration of function ‘drm_dp_mst_hpd_irq’; did you mean ‘intel_dp_mst_hpd_irq’? [-Werror=implicit-function-declaration]
 3890 |         drm_dp_mst_hpd_irq(&intel_dp->mst_mgr, esi, &handled);
      |         ^~~~~~~~~~~~~~~~~~
      |         intel_dp_mst_hpd_irq
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp.c: In function ‘intel_dp_get_modes’:
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp.c:4847:69: warning: passing argument 2 of ‘intel_connector_update_modes’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
 4847 |                 num_modes = intel_connector_update_modes(connector, edid);
      |                                                                     ^~~~
In file included from /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp.c:55:
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_connector.h:28:47: note: expected ‘struct edid *’ but argument is of type ‘const struct edid *’
   28 |                                  struct edid *edid);
      |                                  ~~~~~~~~~~~~~^~~~
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp.c: In function ‘intel_edp_init_connector’:
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp.c:5362:51: warning: passing argument 2 of ‘drm_add_edid_modes’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
 5362 |                 if (drm_add_edid_modes(connector, edid)) {
      |                                                   ^~~~
In file included from /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp.c:44:
./include/drm/drm_edid.h:572:70: note: expected ‘struct edid *’ but argument is of type ‘const struct edid *’
  572 | int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid);
      |                                                         ~~~~~~~~~~~~~^~~~
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dsi.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dsi_vbt.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dvo.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_gmbus.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_hdmi.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lspcon.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lvds.o
  CC [M]  /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_panel.o
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:260: /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_dp.o] Error 1
make[1]: *** Waiting for unfinished jobs....
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_hdmi.c: In function ‘intel_hdmi_get_modes’:
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_hdmi.c:2558:56: warning: passing argument 2 of ‘intel_connector_update_modes’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
 2558 |         return intel_connector_update_modes(connector, edid);
      |                                                        ^~~~
In file included from /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_hdmi.c:49:
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_connector.h:28:47: note: expected ‘struct edid *’ but argument is of type ‘const struct edid *’
   28 |                                  struct edid *edid);
      |                                  ~~~~~~~~~~~~~^~~~
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lvds.c: In function ‘intel_lvds_get_modes’:
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lvds.c:485:37: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
  485 |                 struct edid *edid = drm_edid_raw(fixed_edid);
      |                                     ^~~~~~~~~~~~
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lvds.c: In function ‘intel_lvds_init’:
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lvds.c:975:58: warning: passing argument 2 of ‘drm_add_edid_modes’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
  975 |                 if (drm_add_edid_modes(&connector->base, edid)) {
      |                                                          ^~~~
In file included from /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lvds.c:39:
./include/drm/drm_edid.h:572:70: note: expected ‘struct edid *’ but argument is of type ‘const struct edid *’
  572 | int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid);
      |                                                         ~~~~~~~~~~~~~^~~~
make: *** [Makefile:2026: /var/lib/dkms/i915-sriov-dkms/6.5/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.2.16-19-pve'

EDIT: Maybe it is related to this: strongtz/i915-sriov-dkms#117 ?

Found this tutorial while I was looking for hardware acceleration for jellyfin LXC but it´s not working right now

Proxmox 8.0.4 CPU: Intel i3 N305 Kernel Version Linux 6.2.16-19-pve #1 SMP PREEMPT_DYNAMIC PMX 6.2.16-19 (2023-10-24T12:07Z)

Followed steps up to:

root@pve:~# dkms install --force -m i915-sriov-dkms -v 6.5
Sign command: /lib/modules/6.2.16-19-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Certificate or key are missing, generating self signed certificate for MOK...
Creating symlink /var/lib/dkms/i915-sriov-dkms/6.5/source -> /usr/src/i915-sriov-dkms-6.5

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.2.16-19-pve -j8 -C /lib/modules/6.2.16-19-pve/build M=/var/lib/dkms/i915-sriov-dkms/6.5/build KVER=6.2.16-19-pve..................(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.16-19-pve (x86_64)
Consult /var/lib/dkms/i915-sriov-dkms/6.5/build/make.log for more information.

  |                                     ^~~~~~~~~~~~

/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lvds.c: In function ‘intel_lvds_init’:
/var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lvds.c:975:58: warning: passing argument 2 of ‘drm_add_edid_modes’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
975 | if (drm_add_edid_modes(&connector->base, edid)) {
| ^~~~
In file included from /var/lib/dkms/i915-sriov-dkms/6.5/build/drivers/gpu/drm/i915/display/intel_lvds.c:39:
./include/drm/drm_edid.h:572:70: note: expected ‘struct edid *’ but argument is of type ‘const struct edid *’
572 | int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid);
| ~~~~~~~~~~~~~^~~~
make: *** [Makefile:2026: /var/lib/dkms/i915-sriov-dkms/6.5/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.2.16-19-pve'
EDIT: Maybe it is related to this: [strongtz/i915-sriov-dkms#117](https://github.com/strongtz/i915-sriov-dkms/issues/117) ?

I have the same issue. Might be related to that issue ?

I have the same issue. Might be related to that issue ?

Yes. I did the fix mentioned in that issue strongtz/i915-sriov-dkms#117 (comment) and it finished. Using an old kernel should work too.

Right now I'm troubleshooting a gidmap error because I want to setup a privileged container (maybe a typo in the explanation is making wrong ids). But I guess I will check with an unprivileged for testing

How did the proxmox kernels upgrade are going in general? Works always, or most of the time problems?
It is ideal to use the pass through, but if a kernel updates breaks it regularly … it is not workable.

This guide works great, thank you for this (Proxmox 8.0.2 + kernel 6.5)

Author

scyto

commented

Nov 27, 2023

•

edited

i found moving to 6.5 broke the "always do dkms install -m i915-sriov-dkms -v 6.5 --force instructions"
I used the following to clean up and remove the drivers

dkms remove i915-sriov-dkms/6.5 -k 6.2.16-15-pve

obviously change the numbers above to match whatever dkms status does

then one can repull driver from github, do clean installs, etc

If you are starting from a clean Proxmox v8.1 install with Secure Boot, you'll need to sign the DKMS drivers by running
dkms build --force -m i915-sriov-dkms -v 6.5
then
mokutil –import /var/lib/dkms/mok.pub
After reboot, you'll need to accept the keys to allow them using the password you added with the mokutil-import tool

Thanks for documenting this all out - a great reference and working great on my HP Elite Mini 800 G9 i5 and i7 with UHD770's. I've noticed a few small corrections that need to be made and detailed below in bold italic. Hope this helps:

Under 'Assumptions:'
3. you have run cat /etc/groups in the host and noted down the GID for render (lets call that HSTRGID) and gid for video (lets call that HSTVGID). 5 that you have va info fully working

Under Add ID mapping (only needed in unprivileged)
...
lxc.idmap: u 0 100000 65536
lxc.idmap: g 0 100000 CTVGID
lxc.idmap: g CTVGID HSTVGID 1
lxc.idmap: g CTVGID+1 1000{CTVGID+1} CTRGID-CTVGID-1
lxc.idmap: g CTRGID HSTRGID 1
lxc.idmap: g CTRGID+1 100{CTRGID+1} 65536-{CTRGID-1}

Have anyone actually looked into passing the video to physical output? Intel themselves mention that:

The key benefits of Intel Graphics SR-IOV are:

Support up to four independent display output and seven virtualized functions (12th generation Intel® Core™ embedded processors).

They say the same in their Github repo, however nowhere did I find any actual mentioning of how this would work in practice.

EDIT: asked them directly: intel/kubevirt-gfx-sriov#5

thanks for your tutorial，its wonderful. but i have some problem in use.
Proxmox 8.1.3 CPU: Intel N305 Kernel Version Linux 6.5.11-7-pve (2023-12-05T09:44Z)
it looks signature is missed,how can i deal it?anyone knows?

root@iAsst:~# dmesg | grep i915
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.11-7-pve root=/dev/mapper/pve-root ro intel_iommu=on i915.enable_guc=3 i915.max_vfs=7
[    0.048371] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.11-7-pve root=/dev/mapper/pve-root ro intel_iommu=on i915.enable_guc=3 i915.max_vfs=7
[    4.787774] i915: loading out-of-tree module taints kernel.
[    4.787883] i915: module verification failed: signature and/or required key missing - tainting kernel
[    5.199407] kvmgt: disagrees about version of symbol i915_gem_object_set_to_cpu_domain
[    5.199419] kvmgt: Unknown symbol i915_gem_object_set_to_cpu_domain (err -22)
[    5.199491] kvmgt: disagrees about version of symbol i915_gem_object_alloc
[    5.199494] kvmgt: Unknown symbol i915_gem_object_alloc (err -22)
[    5.199511] kvmgt: disagrees about version of symbol i915_gem_object_create_shmem
[    5.199514] kvmgt: Unknown symbol i915_gem_object_create_shmem (err -22)
[    5.199537] kvmgt: disagrees about version of symbol i915_gem_object_pin_map
[    5.199540] kvmgt: Unknown symbol i915_gem_object_pin_map (err -22)
[    5.199578] kvmgt: disagrees about version of symbol i915_gem_gtt_insert
[    5.199581] kvmgt: Unknown symbol i915_gem_gtt_insert (err -22)
[    5.199585] kvmgt: disagrees about version of symbol i915_request_add
[    5.199587] kvmgt: Unknown symbol i915_request_add (err -22)
[    5.199609] kvmgt: disagrees about version of symbol i915_gem_ww_ctx_fini
[    5.199612] kvmgt: Unknown symbol i915_gem_ww_ctx_fini (err -22)
[    5.199678] kvmgt: disagrees about version of symbol i915_gem_ww_ctx_init
[    5.199681] kvmgt: Unknown symbol i915_gem_ww_ctx_init (err -22)
[    5.199685] kvmgt: disagrees about version of symbol i915_reserve_fence
[    5.199687] kvmgt: Unknown symbol i915_reserve_fence (err -22)
[    5.199708] kvmgt: disagrees about version of symbol i915_gem_object_ggtt_pin_ww
[    5.199711] kvmgt: Unknown symbol i915_gem_object_ggtt_pin_ww (err -22)
[    5.199762] kvmgt: disagrees about version of symbol i915_gem_object_init
[    5.199765] kvmgt: Unknown symbol i915_gem_object_init (err -22)
[    5.199852] kvmgt: disagrees about version of symbol _i915_vma_move_to_active
[    5.199855] kvmgt: Unknown symbol _i915_vma_move_to_active (err -22)
[    5.199860] kvmgt: disagrees about version of symbol i915_request_create
[    5.199863] kvmgt: Unknown symbol i915_request_create (err -22)
[    5.199896] kvmgt: disagrees about version of symbol i915_ppgtt_create
[    5.199899] kvmgt: Unknown symbol i915_ppgtt_create (err -22)
[    5.199939] kvmgt: disagrees about version of symbol i915_gem_ww_ctx_backoff
[    5.199943] kvmgt: Unknown symbol i915_gem_ww_ctx_backoff (err -22)
[    5.199951] kvmgt: disagrees about version of symbol i915_unreserve_fence
[    5.199954] kvmgt: Unknown symbol i915_unreserve_fence (err -22)
[    5.199968] kvmgt: disagrees about version of symbol __i915_gem_object_set_pages
[    5.199971] kvmgt: Unknown symbol __i915_gem_object_set_pages (err -22)
[    5.200008] kvmgt: disagrees about version of symbol i915_request_wait
[    5.200010] kvmgt: Unknown symbol i915_request_wait (err -22)
[    5.200025] kvmgt: disagrees about version of symbol __i915_gem_object_flush_map
[    5.200028] kvmgt: Unknown symbol __i915_gem_object_flush_map (err -22)

Author

@nuts64

I don't know, if you did all the steps it could just be an issue with the current version of what's on GitHub for the driver
its also possible somehting changed in the driver since i last did the steps, i will try at weekend if i have time
you might want to search the issues list to see if others have this, and if not log a quality issue

thanks for your tutorial，its wonderful. but i have some problem in use. Proxmox 8.1.3 CPU: Intel N305 Kernel Version Linux 6.5.11-7-pve (2023-12-05T09:44Z) it looks signature is missed,how can i deal it?anyone knows?

root@iAsst:~# dmesg | grep i915
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.11-7-pve root=/dev/mapper/pve-root ro intel_iommu=on i915.enable_guc=3 i915.max_vfs=7
[    0.048371] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.11-7-pve root=/dev/mapper/pve-root ro intel_iommu=on i915.enable_guc=3 i915.max_vfs=7
[    4.787774] i915: loading out-of-tree module taints kernel.
[    4.787883] i915: module verification failed: signature and/or required key missing - tainting kernel
[    5.199407] kvmgt: disagrees about version of symbol i915_gem_object_set_to_cpu_domain
[    5.199419] kvmgt: Unknown symbol i915_gem_object_set_to_cpu_domain (err -22)
[    5.199491] kvmgt: disagrees about version of symbol i915_gem_object_alloc
[    5.199494] kvmgt: Unknown symbol i915_gem_object_alloc (err -22)
[    5.199511] kvmgt: disagrees about version of symbol i915_gem_object_create_shmem
[    5.199514] kvmgt: Unknown symbol i915_gem_object_create_shmem (err -22)
[    5.199537] kvmgt: disagrees about version of symbol i915_gem_object_pin_map
[    5.199540] kvmgt: Unknown symbol i915_gem_object_pin_map (err -22)
[    5.199578] kvmgt: disagrees about version of symbol i915_gem_gtt_insert
[    5.199581] kvmgt: Unknown symbol i915_gem_gtt_insert (err -22)
[    5.199585] kvmgt: disagrees about version of symbol i915_request_add
[    5.199587] kvmgt: Unknown symbol i915_request_add (err -22)
[    5.199609] kvmgt: disagrees about version of symbol i915_gem_ww_ctx_fini
[    5.199612] kvmgt: Unknown symbol i915_gem_ww_ctx_fini (err -22)
[    5.199678] kvmgt: disagrees about version of symbol i915_gem_ww_ctx_init
[    5.199681] kvmgt: Unknown symbol i915_gem_ww_ctx_init (err -22)
[    5.199685] kvmgt: disagrees about version of symbol i915_reserve_fence
[    5.199687] kvmgt: Unknown symbol i915_reserve_fence (err -22)
[    5.199708] kvmgt: disagrees about version of symbol i915_gem_object_ggtt_pin_ww
[    5.199711] kvmgt: Unknown symbol i915_gem_object_ggtt_pin_ww (err -22)
[    5.199762] kvmgt: disagrees about version of symbol i915_gem_object_init
[    5.199765] kvmgt: Unknown symbol i915_gem_object_init (err -22)
[    5.199852] kvmgt: disagrees about version of symbol _i915_vma_move_to_active
[    5.199855] kvmgt: Unknown symbol _i915_vma_move_to_active (err -22)
[    5.199860] kvmgt: disagrees about version of symbol i915_request_create
[    5.199863] kvmgt: Unknown symbol i915_request_create (err -22)
[    5.199896] kvmgt: disagrees about version of symbol i915_ppgtt_create
[    5.199899] kvmgt: Unknown symbol i915_ppgtt_create (err -22)
[    5.199939] kvmgt: disagrees about version of symbol i915_gem_ww_ctx_backoff
[    5.199943] kvmgt: Unknown symbol i915_gem_ww_ctx_backoff (err -22)
[    5.199951] kvmgt: disagrees about version of symbol i915_unreserve_fence
[    5.199954] kvmgt: Unknown symbol i915_unreserve_fence (err -22)
[    5.199968] kvmgt: disagrees about version of symbol __i915_gem_object_set_pages
[    5.199971] kvmgt: Unknown symbol __i915_gem_object_set_pages (err -22)
[    5.200008] kvmgt: disagrees about version of symbol i915_request_wait
[    5.200010] kvmgt: Unknown symbol i915_request_wait (err -22)
[    5.200025] kvmgt: disagrees about version of symbol __i915_gem_object_flush_map
[    5.200028] kvmgt: Unknown symbol __i915_gem_object_flush_map (err -22)

Try running a mokutil –import /var/lib/dkms/mok.pub
If mokutil not installed, install with apt install mokutil and rerun the above
then...
build with dkms build -m i915-sriov-dkms -v 6.5 -k 6.5.11-7-pve --force
install with dkms install -m i915-sriov-dkms -v 6.5 -k 6.5.11-7-pve --force

thanks for your tutorial，its wonderful. but i have some problem in use. Proxmox 8.1.3 CPU: Intel N305 Kernel Version Linux 6.5.11-7-pve (2023-12-05T09:44Z) it looks signature is missed,how can i deal it?anyone knows?

root@iAsst:~# dmesg | grep i915
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.11-7-pve root=/dev/mapper/pve-root ro intel_iommu=on i915.enable_guc=3 i915.max_vfs=7
[    0.048371] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.11-7-pve root=/dev/mapper/pve-root ro intel_iommu=on i915.enable_guc=3 i915.max_vfs=7
[    4.787774] i915: loading out-of-tree module taints kernel.
[    4.787883] i915: module verification failed: signature and/or required key missing - tainting kernel
[    5.199407] kvmgt: disagrees about version of symbol i915_gem_object_set_to_cpu_domain
[    5.199419] kvmgt: Unknown symbol i915_gem_object_set_to_cpu_domain (err -22)
[    5.199491] kvmgt: disagrees about version of symbol i915_gem_object_alloc
[    5.199494] kvmgt: Unknown symbol i915_gem_object_alloc (err -22)
[    5.199511] kvmgt: disagrees about version of symbol i915_gem_object_create_shmem
[    5.199514] kvmgt: Unknown symbol i915_gem_object_create_shmem (err -22)
[    5.199537] kvmgt: disagrees about version of symbol i915_gem_object_pin_map
[    5.199540] kvmgt: Unknown symbol i915_gem_object_pin_map (err -22)
[    5.199578] kvmgt: disagrees about version of symbol i915_gem_gtt_insert
[    5.199581] kvmgt: Unknown symbol i915_gem_gtt_insert (err -22)
[    5.199585] kvmgt: disagrees about version of symbol i915_request_add
[    5.199587] kvmgt: Unknown symbol i915_request_add (err -22)
[    5.199609] kvmgt: disagrees about version of symbol i915_gem_ww_ctx_fini
[    5.199612] kvmgt: Unknown symbol i915_gem_ww_ctx_fini (err -22)
[    5.199678] kvmgt: disagrees about version of symbol i915_gem_ww_ctx_init
[    5.199681] kvmgt: Unknown symbol i915_gem_ww_ctx_init (err -22)
[    5.199685] kvmgt: disagrees about version of symbol i915_reserve_fence
[    5.199687] kvmgt: Unknown symbol i915_reserve_fence (err -22)
[    5.199708] kvmgt: disagrees about version of symbol i915_gem_object_ggtt_pin_ww
[    5.199711] kvmgt: Unknown symbol i915_gem_object_ggtt_pin_ww (err -22)
[    5.199762] kvmgt: disagrees about version of symbol i915_gem_object_init
[    5.199765] kvmgt: Unknown symbol i915_gem_object_init (err -22)
[    5.199852] kvmgt: disagrees about version of symbol _i915_vma_move_to_active
[    5.199855] kvmgt: Unknown symbol _i915_vma_move_to_active (err -22)
[    5.199860] kvmgt: disagrees about version of symbol i915_request_create
[    5.199863] kvmgt: Unknown symbol i915_request_create (err -22)
[    5.199896] kvmgt: disagrees about version of symbol i915_ppgtt_create
[    5.199899] kvmgt: Unknown symbol i915_ppgtt_create (err -22)
[    5.199939] kvmgt: disagrees about version of symbol i915_gem_ww_ctx_backoff
[    5.199943] kvmgt: Unknown symbol i915_gem_ww_ctx_backoff (err -22)
[    5.199951] kvmgt: disagrees about version of symbol i915_unreserve_fence
[    5.199954] kvmgt: Unknown symbol i915_unreserve_fence (err -22)
[    5.199968] kvmgt: disagrees about version of symbol __i915_gem_object_set_pages
[    5.199971] kvmgt: Unknown symbol __i915_gem_object_set_pages (err -22)
[    5.200008] kvmgt: disagrees about version of symbol i915_request_wait
[    5.200010] kvmgt: Unknown symbol i915_request_wait (err -22)
[    5.200025] kvmgt: disagrees about version of symbol __i915_gem_object_flush_map
[    5.200028] kvmgt: Unknown symbol __i915_gem_object_flush_map (err -22)

Try running a mokutil –import /var/lib/dkms/mok.pub If mokutil not installed, install with apt install mokutil and rerun the above then... build with dkms build -m i915-sriov-dkms -v 6.5 -k 6.5.11-7-pve --force install with dkms install -m i915-sriov-dkms -v 6.5 -k 6.5.11-7-pve --force

thanks for your help! I try to do this ,but it looks dosen't work, get same result. I will try the tutorial again.

mokutil –import /var/lib/dkms/mok.pub have a incorrect OPTION，i fix it，mokutil --import /var/lib/dkms/mok.pub

when i in install step,it looks another errors happen.i try find a way to deal it now. am a rookie,haha

dkms install -m i915-sriov-dkms -v 6.5 -k 6.5.11-7-pve --force

Module i915-sriov-dkms-6.5 for kernel 6.5.11-7-pve (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

i915.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.5.11-7-pve/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.
depmod...

i915.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/6.5.11-7-pve/updates/dkms/
depmod...

@nuts64

I don't know, if you did all the steps it could just be an issue with the current version of what's on GitHub for the driver its also possible somehting changed in the driver since i last did the steps, i will try at weekend if i have time you might want to search the issues list to see if others have this, and if not log a quality issue

thanks a lot，i will try it again one step by one,perhaps the version is new. I find a lot about kernel 5.1 or 5.2.i follow this tutoral (change version to 5.5)

(https://github.com/strongtz/i915-sriov-dkms)

before,but failed. i dont make sure it cause conflict

After following the guide, I had Error 43 in Intel UHD graphics adapter. The fix for me was to reinstall Windows 11. I did not create a new VM or change any settings, simple reinstall made the error 43 go away. I can see GPU in Task Manager and it's being used when watching YouTube in Chrome or Edge.
My miniPC is Beelink S12 Pro, N100.
I also tried to blacklist i915 driver and get HDMI to work, but no luck. However, I do see the display go blank once I start the VM. Before starting the VM, the display is showing Proxmox Login page, so something is happening there. There is gazillion of options in BIOS, many related to graphics and I have changed some, but so far nothing made HDMI work.
BME DMA Mitigation when Enabled, I think it broke 7 VFs, dmesg would show "Enabled 7 VFs" and later on "VFs Disabled" or something similar. Disabling the setting made VFs work again.

proxmox-vGPU.md

Enable & Using vGPU Passthrough

Preparation

Install Build Requirements

Install Other Drivers / Tools

Compile and Install the new driver

Clone github project

modify dkms.conf

Compile and Install the Driver

Modify grub

Find PCIe Bus and update sysfs.conf

Testing On Host

check devices

Validate with VAInfo

Check you can monitor the VFs - if not you have issues

Configure vGPU Pool in Proxmox

EVERYTIME THE KERNEL IS UPDATED IN PROXMOX YOU SHOULD DO THE FOLLOWING

How to get working in a privileged container

Assumptions:

Create Container

Edit container conf file

Add lxc device mapping

Add ID mapping (only needed in unprivileged)

add vGPU to a Windows 11 or Server 2022 VM

From @rinze24:

Recommend

攻克私有云通杀神器proxmox-sery

Proxmox 使用nfs备份及存储iso-sery

proxmox超融合集群用户授权-sery

乾坤大挪移，巧迁数据到proxmox平台-sery

proxmox超融合集群挂接nfs出错删除挂接点操作备忘-sery

用备份玩死proxmox超融合私有云集群-sery

可照搬实施的商超高可用方案：proxmox + haproxy 等-sery

速来围观老司机快速排错--解决论坛迁移到proxmox超融合私有云平台后后部分功能不能使...

Github GitHub - DualCoder/vgpu_unlock: Unlock vGPU functionality for consumer gr...

MIG or vGPU Mode for NVIDIA Ampere GPU: Which One Should I Use? (Part 1 of 3)

About Joyk