After following https://gitlab.com/polloloco/vgpu-proxmox along with https://wvthoog.nl/proxmox-7-vgpu-v2/ and https://www.youtube.com/watch?v=cPrOoeMxzu0&ab_channel=CraftComputing
I've got to cloned VMs with the same settings.
and
After proxmox reboot I type in CLI
Then I'm able to start any of two VM's and GPU works fine there. If I try to start second vm I get:
and the weird thing is that if I stop the first vm and try to get it running again I revieve the same error but with a different group.
So that I have to
I've got to cloned VMs with the same settings.
args: -device 'vfio-pci,sysfsdev=/sys/bus/mdev/devices/5be2a059-3ad4-45b9-8515-92c6d7081b8b,display=off,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,x-pci-vendor-id=0x10de,x-pci-device-id=0x0x1b81,x-pci-sub-vendor-id=0x10de,x-pci-sub-device-id=0x11A0' -uuid 5be2a059-3ad4-45b9-8515-92c6d7081b8band
args: -device 'vfio-pci,sysfsdev=/sys/bus/mdev/devices/4550976a-6ab8-48c5-9825-4cc578fb91fa,display=off,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,x-pci-vendor-id=0x10de,x-pci-device-id=0x0x1b81,x-pci-sub-vendor-id=0x10de,x-pci-sub-device-id=0x11A0' -uuid 4550976a-6ab8-48c5-9825-4cc578fb91faAfter proxmox reboot I type in CLI
mdevctl start -u 5be2a059-3ad4-45b9-8515-92c6d7081b8b -p 0000:08:00.0 --type nvidia-50mdevctl start -u 4550976a-6ab8-48c5-9825-4cc578fb91fa -p 0000:08:00.0 --type nvidia-50Then I'm able to start any of two VM's and GPU works fine there. If I try to start second vm I get:
kvm: -device vfio-pci,sysfsdev=/sys/bus/mdev/devices/5be2a059-3ad4-45b9-8515-92c6d7081b8b,display=off,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,x-pci-vendor-id=0x10de,x-pci-device-id=0x1c31: vfio 5be2a059-3ad4-45b9-8515-92c6d7081b8b: error getting device from group 26: Connection timed outVerify all devices in group 26 are bound to vfio-<bus> or pci-stub and not already in usestopping swtpm instance (pid 3445) due to QEMU startup errorTASK ERROR: start failed: QEMU exited with code 1and the weird thing is that if I stop the first vm and try to get it running again I revieve the same error but with a different group.
So that I have to
reboot and start over