raw device showing only 02.0

[clemone210]

Hi,
I followed your guide and want to enable the vGPU. However it shows only the 02.0 raw device.
Do you have some tips how to troubleshoot?

[SyntaxError1871]

Having the same issue here. Followed all the steps and the Intel Xe PCI device shows up as the 02.0 raw device.

[chilltrout]

Also can report the same issue on 6.8.12-1 its weird because in the docs for https://github.com/strongtz/i915-sriov-dkms it says it works on 6.8.12-1.
I wonder I already have the entire device passed through to my HAOS VM as in 02.0 not 02.1 for example because when I initially set it up the host couldn't see the sub devices.
I'm remote and cant mess with stuff because I will probably kill my access but I'm wondering if you both have passed the entire device already to a VM to?

[chilltrout]

Can confirm this is because you have passed the whole device to your VM. Remove it from the VM reboot the host and you should see everything on lscpi | grep vga, then pass one of the sub devices

[mioiox]

Guys, take a look at my comment in the automated script issue here - Upinel/PVE-Intel-vGPU-Lazy#2 (comment)
I think you will be able to resolve it (if you haven't done so already)

[Bastilms]

If you are using ZFS, the path for the kernel parameters is wrong in this guide. You have to add them to /etc/kernel/cmdline and then run pve-efiboot-tool refresh.
The cmdline file should look like this:

root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet intel_iommu=on iommu=pt i915.enable_guc=3 i915.max_vfs=7

[YehezkielLegowo]

I got myself work, look for thousand of pages but i have Engineering Sample 0000 which cause headache driver for Windows (i have no driver for them) so anyway feel free to checkout "strongtz/i915-sriov-dkms#339"

[GloriaOS]

Thanks for reporting. I've added a comprehensive Troubleshooting section to the guide covering this exact scenario. Common causes: kernel cmdline missing IOMMU flags, sysfs.conf not applied, DKMS module not loaded, or SR-IOV not fully enabled in BIOS. The new section has step-by-step diagnostics with exact commands. Check it out and let me know if it resolves your issue!