mojotaker

I just wanted to say thank you for your time and effort, and really appreciate you sharing. Thanks alot.

Thanks

Hello, please did you find a solution ?

Bump. Im having this exact same problem. Any Help please !!!

PLEASSEEEEEEE How did you fix it. I have this problem with fresh installs also

WOOOOOOOOOOOW!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Thank you, thank you, thank you, thank you. You were correct. I redit the vbios modifications, and its working now. Thank you again. 4hrs wasted on that.

Hmm very weird, I responded to you, but i guess the post didnt got through. Thank you all for your time. Yes i did edit the bios with a hex editor. Lol thats the video i followed. Im going to redo it again, and will post back. Thanks again.

With the latest bios for my board: Asus strix x470-F Bios: 5406 : Update AM4 combo PI 1.0.0.4 patch B Gpu: Asus strix gpu gtx 1070 Processor: Ryzen 2700x Unraid: 6.80 Gpu passthrough not working, No error message. just blank screen. Log: -cpu host,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vendor-id=none \ -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on \ -drive file=/etc/libvirt/qemu/nvram/fc0e2c3c-8ea7-754a-298e-9c6867155fc6_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 \ -m 4096 \ -overcommit mem-lock=off \ -smp 4,sockets=1,cores=4,threads=1 \ -uuid fc0e2c3c-8ea7-754a-298e-9c6867155fc6 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=33,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 \ -drive 'file=/mnt/user/domains/Windows 10 Graphics Design/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive file=/mnt/user/isos/Windows.iso,format=raw,if=none,id=drive-ide0-0-0,readonly=on \ -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 \ -drive file=/mnt/user/isos/virtio-win-0.1.160-1.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ -netdev tap,fd=36,id=hostnet0,vhost=on,vhostfd=37 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:35:ba:5b,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=38,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device vfio-pci,host=0000:0a:00.0,id=hostdev0,bus=pci.0,multifunction=on,addr=0x5,romfile=/mnt/user/domains/vbios/Asus.GTX1070.8192.160531.rom \ -device vfio-pci,host=0000:0a:00.1,id=hostdev1,bus=pci.0,addr=0x5.0x1 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-01-03 17:19:04.721+0000: Domain id=5 is tainted: high-privileges 2020-01-03 17:19:04.721+0000: Domain id=5 is tainted: host-cpu New windows 10 vm. Other info: Never downgraded the bios, cause i didn't need gpu pasthrough at the time. Thank you.

Hello Unraid Engineers, What I like most about unraid, is its ease of install, What I would like to see in 2020 is Either a mobile app, Or a PWA version of the control panel. Thank you.

Thank you.

Fellow Friends, I ran into this problem when I upgraded to 6.8 and had to downgrade back to 6.7.2. Advice, please what is the consensus here should i upgrade to rc 6.8.7 or stay on 6.7.2 ? or at least what did you settle with for now ? Thank you.

Please could you take a screenshot of your pfsense vm settings like the one attached And just so you know, I think the latest pfsense requires you use "OVMF" bios. And if you followed space invader 1's video, you would see thats the bios, that was used. Lastly make sure that your motherboard bios supports hardware passthrough.

+1

This is no longer working in 6.6 RC2 I Checked the Repo, and it no longer exists. I have gone back to using this command modprobe it87 force_id=0x8620 Please fix.