[SOLVED] Intel coffee lake gGVT issue.

Tahsin

Well-Known Member
Mar 24, 2018
49
5
48
36
Since the new 5.3 Kernel is release i finally can use gGVT with coffee lake, i3-8100. After adding the hostpci0: 00:02.0,mdev=i915-GVTg_V5_4. It fails to start.

The error as follows: kvm: -device vfio-pci,sysfsdev=/sys/bus/pci/devices/00:02.0/00000000-0000-0000-0000-000000000105,id=hostpci0,bus=pci.0,addr=0x10,rombar=0: vfio /sys/bus/pci/devices/00:02.0/00000000-0000-0000-0000-000000000105: no such host device: No such file or directory
Setting pci express to 1 or 0 and rombar to 1 or 0 still has the same issue.

Settings:
agent: 1
balloon: 2048
bios: ovmf
bootdisk: scsi0
cores: 2
cpu: host
efidisk0: Bay:vm-105-disk-1,size=128K
hostpci0: 00:02.0,mdev=i915-GVTg_V5_4
ide2: local:iso/virtio-win-0.1.141.iso,media=cdrom,size=309208K
machine: q35
memory: 4096
name: security
net0: virtio=02:0C:DE:57:C1:AC,bridge=vmbr1,firewall=1,queues=2
numa: 0
ostype: win10
scsi0: Bay:vm-105-disk-0,discard=on,iothread=1,size=128G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=3e1e04ca-267b-4edd-ad81-260f91b9cc87
sockets: 1
vga: qxl
vmgenid: 5a84ac84-2e69-41a9-9388-828ff47bda26
root=ZFS=rpool/ROOT/pve-1 boot=zfs i915.enable_gvt=1 kvm.ignore_msrs=1 intel_iommu=on iommu=pt drm.debug=0 pci-stub.ids=8086:3e91 console=tty0 console=ttyS1,115200n8
PCI stub is there so linux will not use intel igd as primary graphics. I have aspeed controller for BMC which I use as primary.
kvmgt
xengt
vfio-mdev

vfio
vfio-iommu-type1
vfio-pci
vfio-virqfd

Any help will be appreciated.
 
can you post your pveversion -v?
we recently changed some path building for pcie to include domains different from 0000 and maybe we forgot one place
also maybe as a workaround you could try to set the full pciid in the config
Code:
qm set ID -hostpci0 '0000:00:02.0,mdev=i915-GVTg_V5_4'
 
Same issue with 6.1-3

proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.10-1-pve: 5.3.10-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.21-4-pve: 5.0.21-9
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

Setting the full pciid in the VM config works as a workaround
 
Last edited:
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.10-1-pve: 5.3.10-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.21-4-pve: 5.0.21-9
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: not correctly installed
ifupdown2: 1.2.8-1+pve4
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

I also tired making ...00105 ID as the error message, it says the ID already exists. So it does look for existing uuid.
As noted by apkoval, putting full PCIID works fine.
 
Last edited:
I'm seeing the same issue in testing with passing through the IGP using Intel GVT-d ... It looks like this issue was also previously seen when passing through the full IGP (not as mediated device) and was fixed for that scenario but looks like the mediated device passthrough still exhibits this same issue where the hostpci ID is not automatically prefixed with 0000: in the VM.conf file ...

https://forum.proxmox.com/threads/pci-passthrough-not-working-after-update.60580/#post-279115
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!