Search results

this happens for any VM i attempt passthrough with for both GPU and Audio (same ID.x) latest VE 6.2 fully updated qm start simply states the device was allready assigned/associated, which is how i found out about this happening in the first place

While struggeling with PCI passthrouhg (it does work, eventually) i found something peculiar. Sometimes the VM would not boot because the PCI.id for a device was alread in use. This was because the pci-id for the vga and the audio were written as the same. So instead of 0000:17:0.0 and...

It is demanding to get it working but i can say nothing is broken, at least not for my system. This machine is running on Proxmox VE 6.2 since about one month. GPU passthrough is quite demanding in my experience but if it works, it works very close to native speed. Staring a VM from the shell...

Which is in-line with vfio 0000:65:00.0: failed getting region info for VGA region index 8: Invalid argument device does not support requested feature x-vga

this post https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/trouble-with-gpu-passthrough-on-slackware-14-2-failed-getting-region-info-for-vga-region-index-8-a-4175601587/ suggests to remove x-vga=1

Ah! I completely missed that error message. cat /etc/pve/qemu-server/107.conf agent: 1 bootdisk: sata0 cores: 10 cpu: host,hidden=1,flags=+pcid args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off' hostpci0: 65:00,pcie=1,x-vga=1 ide2: none,media=cdrom machine: q35 memory...

the proxmox system completely froze, zero logs happening, no network, not even a bad write to disk. the first log entry i see after me trying to figure out what happened to the server are logs for the host booting up. * only recent changes to the system was the introduction of huge pages...

eh, just read what i wrote, all is there. iommu: Default domain type: Translated must read ommu: Default domain type: passthrough for it to work, at least imho and something like options vfio-pci ids=10de:1f82,10de:10fa

Dear, Syslog is afluent with pvx vio4wd_core_scheduler[<PID>]: No response from stats server. Reconnecting... These are linked to /usr/sbin/watchdoc-mux I found /etc/default/virtioforwarder but have no memory of having it enabled or configured. I have learned this requires hugepages to be...

Just checked, on this machine the webUI reports all correctly as on the commandline. I must add i experienced the same issue as you observerd. With me memory usage was wildly overreported, close to 25GB while just 5GB was in use. I assume this to have been because of hugepage configuration. I...

https://www.kernel.org/doc/html/v5.4/x86/intel-iommu.html#graphics-problems If you encounter issues with graphics devices, you can try adding option intel_iommu=igfx_off to turn off the integrated graphics engine. If this fixes anything, please ensure you file a bug reporting the problem.

it is a classic in the world of computing :D

Thanks, interesting. A few assumptions and observations. Based on the output i'd suggest you look for a BIOS upgrade and install it, here referring to BUG notifications on TSC, TAA, MDS and others. Because of [ 0.476774] iommu: Default domain type: Translated present i assume your system is...

With Ryzen 1700, make sure you update the BIOS to the most recent version. When using GPU passthrough, you may require to use a reset script. #!/bin/bash # #replace xx\:NN.x with the number of your gpu and sound counterpart # # echo "disconnecting amd graphics" echo "1" | tee -a...

what does the output say for dmesg | grep -e BAR -e iommu -e IOMMU -e vfio -e "[b|B]"u -e DMAR

Notice how available is 3583 (3.59 rounded) wich matches the 3.59 out of 4.00 GB, an unusual way of representing memory usage by Proxmox.

No worries, memory requirements can often be configured and are highly dependent on the load on the web server. I run a few vm <= 1GB of RAM running multiple services. No problems, even without swap.

Fully up to date Proxmox VE 6.2

What i meant to say is. Typically it does not make sense to do PCI passthrough since KVM is really fast, if you need it. Setting CPU to host make run QEMU on bare metal which is fastest. Most other peripherals are available to the VM. Passthrough of the Intel HD 5500 will not work unless you...

Describing here a problem encountered. noteworthy is previously there were hugepages configured with the VM running and these were subsequently removed. Proxmox did not catch this imho. Booting a VM where the CPU configuration had pdpe1gb flag enabled this appeared to have resulted in initially...