Search results

But the baremetal Win10 benchmark that matlab is giving as an Threadripper 3970x example doesn't seems to suffer from this performance issue. Also the VM500 (the one with GPU passthrough is also fine). So what could be different from VM500? From VM config, I have set the CPU argument the same...

Thanks for the reply. No they are not running at the same time. The only other thing running is a Turnkey SAMBA server in LXC container using 1 VCPU and 512MB RAM Hardware CPU: AMD Threadripper 3970x (32C/64T) GPU: NVIDIA 2080 Ti Founders Edition Blower Style MB: MSI TRX40 Pro Wifi RAM: 256GB...

Update: I am chasing the ghost here. I have set high performance in Win10 new setting menu in VM412. But the old style power plan (now called additional power plan setting) is still on balanced. Duh. Now VM412's bench are similar to VM500. The reason why VM500 has good benchmarks at the...

Very excited. BTW, any way to make these three lines permanent at boot? Right now I need to type these three lines again after reboot.

YES!!! I solve the BAR3 error and Code43 error using a tip from UNRAID VM thread. echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind These three lines and code and original rom (not...

I did this echo "blacklist radeon" >> /etc/modprobe.d/blacklist.conf echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf echo "blacklist nvidia" >> /etc/modprobe.d/blacklist.conf unless it is not successfully blacklisting (I did update-initramfs -u -k all ) as well as echo "vfio" > \...

In the Reddit post, 2080Ti was said to be working on on the secondary slot. Use original, unpatched rom I disabled GPU in device manager in win10 and re-enable it, for a brief time, the exclamation mark disappeared and it shows device working properly. Then I restarted the VM and then still...

Thanks. The github rom patcher only works for 1xxx GPU, not RTX2xxx. I can extract rom using GPU-Z in the win10 guest system. I put extracted (original, unpatched) rom in folder /usr/share/kvm/ and put romfile=rtx2080ti.rom in 500.conf file. It still gives me code43 error. Also, same output qm...

Thanks for keeping diagnose with me. qm start works without any change now (I didn't unbind before starting vm) qm start 500 kvm: -device vfio-pci,host=0000:21:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on: Failed to mmap 0000:21:00.0 BAR 3. Performance may be slow Now I...

echo "0000:21:00.0" > /sys/bus/pci/devices/0000:21:00.0/driver/unbind echo "0000:21:00.1" > /sys/bus/pci/devices/0000:21:00.1/driver/unbind echo "0000:21:00.2" > /sys/bus/pci/devices/0000:21:00.2/driver/unbind echo "0000:21:00.3" > /sys/bus/pci/devices/0000:21:00.3/driver/unbind Still the same...

lspci -nnk full output attached 21:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti] [10de:1e04] (rev a1) Subsystem: PNY TU102 [GeForce RTX 2080 Ti] [196e:134e] Kernel driver in use: vfio-pci Kernel modules: nvidiafb, nouveau 21:00.1...

without pcie_acs_override the IOMMU grouping is the same: IOMMU Group 28: 21:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti] [10de:1e04] (rev a1) 21:00.1 Audio device [0403]: NVIDIA Corporation TU102 High Definition Audio Controller...

You are right. I can still get to web console. lsmod | grep vfio vfio_pci 49152 0 vfio_virqfd 16384 1 vfio_pci irqbypass 16384 2 vfio_pci,kvm vfio_iommu_type1 32768 0 vfio 32768 2 vfio_iommu_type1,vfio_pci modprobe vfio still...

I didn't know that I need to edit apt source. PS: I am evaluating Proxmox. Once I think Proxmox suits our need (a research lab at University), our lab will get subscription for more stable updates and support. updated to pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.55-1-pve)...

Yes. I reboot every time I made change to either /etc/modules or /etc/default/grub, or /etc/modules-load.d/vfio.conf of course after update-initramfs -u -k all or update-grub update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-5.4.34-1-pve Running hook script...

modinfo vfio modinfo: ERROR: Module vfio not found. The fact that both lsmod | grep vfio and modprobe vfio prints out nothing suggests that the vfio module is not loaded. I don't think it's related to a specific VM. So we need to figure out why vfio module is not loaded. /etc/modules has...

did apt dist-upgrade and rebooted. lsmod | grep vfio still prints out nothing. modprobe vfio prints out nothing. Still shows sh /tmp/qm.sh kvm: -device vfio-pci,host=0000:21:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on: vfio 0000:21:00.0: failed to open /dev/vfio/28...

I think the problem is still somehow vfio module is not loaded. /etc/modules has always been like this since I started following the tutorial # /etc/modules: kernel modules to load at boot time. vfio vfio_iommu_type1 vfio_pci vfio_virqfd Now I also tried this method...

My host system is booted in CSM+UEFI mode. The pure UEFI mode will give to crackling display output when I installed PVE. I put in kernel/cmdline, in one line root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet amd_iommu=on iommu=pt nofb nomodeset video=vesafb:off,efifb:off I deleted the extra stuff in...

Latest host config attached (500.txt) I turned off "pcid" option for CPU. I am attempting single-GPU passthrough. [Correction: I can still see PVE console on a monitor connected to 2080Ti] I have a very old Quadro FX580 (not installed) in case I need something. but the slot layout would made...