PCI gvtg funktioniert nicht mehr

loomes

Member
May 22, 2018
74
15
13
40
Seid dem heutigen Update funktioniert die gvtg Weiterleitung in eine VM (win7/8/10) nicht mehr:
Code:
cat /etc/pve/qemu-server/120.conf
agent: 1
audio0: device=ich9-intel-hda,driver=spice
bios: ovmf
boot: cdn
bootdisk: scsi0
cores: 4
cpu: host
cpulimit: 3
hostpci0: 00:02.0,mdev=i915-GVTg_V5_2,pcie=1,x-vga=1
keyboard: de
localtime: 1
machine: q35
memory: 4096
name: win10
net0: virtio=66:6E:FC:77:C9:85,bridge=vmbr0
numa: 0
ostype: win10
scsi0: local-lvm:vm-120-disk-0,cache=unsafe,discard=on,size=100G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=ddb19fd5-e307-4cc6-b378-8085bbc9428a
sockets: 1
spice_enhancements: videostreaming=all
startup: order=10
tablet: 0
usb0: spice
vga: qxl,memory=128
Code:
Use of uninitialized value $vmid in sprintf at /usr/share/perl5/PVE/SysFSTools.pm line 358.
kvm: -device vfio-pci,sysfsdev=/sys/bus/pci/devices/0000:00:02.0/00000000-0000-0000-0000-000000000000,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: vfio /sys/bus/pci/devices/0000:00:02.0/00000000-0000-0000-0000-000000000000: no such host device: No such file or directory
TASK ERROR: start failed: QEMU exited with code 1
Wenn ich die Weiterleitung der gvtg Grafikkarte entferne bootet die Maschine wieder.

Code:
pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.44-1-pve)
pve-manager: 6.2-9 (running version: 6.2-9/4d363c5b)
pve-kernel-5.4: 6.2-4
pve-kernel-helper: 6.2-4
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.44-1-pve: 5.4.44-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-5
libpve-guest-common-perl: 3.0-11
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-9
pve-cluster: 6.1-8
pve-container: 3.1-10
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-9
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-8
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1
 

loomes

Member
May 22, 2018
74
15
13
40
Sieht so aus als wenn irgendwo die mdev ID falsch an die KVM übergeben wird:
00000000-0000-0000-0000-000000000000 müsste 00000000-0000-0000-0000-000000000120 sein.
Angelegt und entfernt wird das Device einwandfrei.
Es hapert also nur an der Übergabe an die KVM CMD.

Code:
Jul 10 18:35:19 proxmox kernel: vfio_mdev 00000000-0000-0000-0000-000000000120: Adding to iommu group 8
Jul 10 18:35:19 proxmox kernel: vfio_mdev 00000000-0000-0000-0000-000000000120: MDEV: group_id = 8
Code:
Jul 10 18:35:20 proxmox kernel: vfio_mdev 00000000-0000-0000-0000-000000000120: Removing from iommu group 8
Jul 10 18:35:20 proxmox kernel: vfio_mdev 00000000-0000-0000-0000-000000000120: MDEV: detaching iommu
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!