binaryhamster

You are a bloddy genius... I installed Teamviewer because thats the only one I knew for windows. Then I just installed the nvidia drivers and boom...It appeared. Ive been obsessed about this issue for 3 days now. I bought the 2000$ setup just for this purpose and the thought of not being able because of bad choise of hardware would have been devastating. Thanx again man... Your awsome... Next step...passthrough keyboard and mouse.

Nice...Good thinking... I will try

I can connect to the vm while its in passthrough? How? The choise dissapears when I put it in passthrough

maincore-diagnostics-20220121-1341.zip

Same result. Do I need to wait for the VM to fully boot before I try and take HDMI out and in?

Same result... Its trying...But finding no signal. maincore-diagnostics-20220121-1307.zip

I am new to unraid. I will do that now. Anyway, 08:00.4 is in a iommu group together with other devices, that are not attached to vfio, so 08:00.4 can't be resetted. Thank you. How to resolve it? maincore-diagnostics-20220121-1206.zip

I am on legacy... changed it....I just unmark the "Force UEFI"... Thats enough right? Or I need to reinstall flash with legacy?

Linux 5.10.28-Unraid x86_64 I try and set it using spaceinvaderones guide and the monitor is trying to connect but ends up without signal ErrorWarningSystemArrayLogin -nodefaults \ -chardev socket,id=charmonitor,fd=31,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Windows 10/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Windows.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device ide-cd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0,bootindex=2 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.190-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \ -netdev tap,fd=33,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:a2:91:b5,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=34,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -device vfio-pci,host=0000:06:00.0,id=hostdev0,bus=pci.0,multifunction=on,addr=0x5,romfile=/mnt/disk3/VM-shared/System/nvidia.rom \ -device vfio-pci,host=0000:06:00.1,id=hostdev1,bus=pci.0,addr=0x5.0x1 \ -device vfio-pci,host=0000:08:00.4,id=hostdev2,bus=pci.0,addr=0x8 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2022-01-21 07:17:55.342+0000: Domain id=3 is tainted: high-privileges 2022-01-21 07:17:55.342+0000: Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2022-01-21T07:17:57.472389Z qemu-system-x86_64: vfio: Cannot reset device 0000:08:00.4, depends on group 17 which is not owned. 2022-01-21T07:17:58.518687Z qemu-system-x86_64: vfio: Cannot reset device 0000:08:00.4, depends on group 17 which is not owned. 2022-01-21T07:18:06.894483Z qemu-system-x86_64: vfio: Cannot reset device 0000:08:00.4, depends on group 17 which is not owned. 2022-01-21T07:18:07.927438Z qemu-system-x86_64: vfio: Cannot reset device 0000:08:00.4, depends on group 17 which is not owned. in the log I only see this line that might be revelant Jan 20 22:33:59 Maincore kernel: vfio-pci 0000:06:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem