planetwilson

spoke too soon...got system pauses happening now with some kernel errors in the console log as well to do with ioacceleventmachine2 ? 1 step forward, 2 steps back

yes it was, no rom dumps were needed. I don't have any onboard graphics, this is the only card in the system and working on OSX and Windows perfectly. Well actually there is no HDMI sound but I don't think that is this card as my previous GTX950 started doing that recently and I've read a lot of people saying the same thing. I use some USB based external speakers so not an issue for me until it gets fixed.

So in the end I have upgraded from the GTX 950 to a Sapphire Nitro+ RX480 8GB. The whole thing is now running much better.

Well mine is working again after I tried an earlier dumped bios instead of the more recent one I had. Now wondering if the more recent one was a patched one form the website GridRunner talks about in his videos and the proper dumped one is fine.

I am getting this as well. My Windows VM which has worked for months has recently stopped working with a code 43. Tried uninstalling the drivers and reinstalling them. I noticed that my VM config now said HyperV was on (no idea what it said previously, was this changed in a recent unRAID release?) so I turned that off but still not working. I am using a bios dump that I have used previously with no issues.

I am using this card https://www.amazon.co.uk/gp/product/B01MDLG51U/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 The NVMe drive has nothing else running off it, dockers are all on the cache drive which is a normal HDD. I have also just now tried emulator pinning to first pair and assigning the last 8 pairs to the VM and it does seem to have improved things. Still not amazing though considering the resources it has. I'll do a little more digging....

I have tried with a topology and without and still find things are a bit sluggish. I wanted to pass 8 physical cores (16 HT) to the VM from a total of 14 that I have, leaving the remaining ones to unRAID. Just wondering if there is something else I can try to make things snappier? I am passing through a usb3 PCI card as well as the recommended wifi/BT card and they are all working perfectly with handoff etc. Also passing through a GTX950 which is working fine as well with nvidia drivers. The VM itself is running off a Samsung NVMe drive so I would have thought it should all run nicely. It just seems sluggish in everything takes a half second to respond to clicks or load web pages etc. <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MWiMac</name> <uuid>678ff6cb-bde5-e84b-e3ef-9ce17eb47a53</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>25165824</memory> <currentMemory unit='KiB'>25165824</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='15'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='17'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='19'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='21'/> <vcpupin vcpu='8' cpuset='9'/> <vcpupin vcpu='9' cpuset='23'/> <vcpupin vcpu='10' cpuset='11'/> <vcpupin vcpu='11' cpuset='25'/> <vcpupin vcpu='12' cpuset='12'/> <vcpupin vcpu='13' cpuset='26'/> <vcpupin vcpu='14' cpuset='13'/> <vcpupin vcpu='15' cpuset='27'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.11'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/678ff6cb-bde5-e84b-e3ef-9ce17eb47a53_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='8' cores='1' threads='2'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/VMNVM/MWiMac/vdisk2.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xf'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:64:9d:cd'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <rom file='/mnt/disks/VMNVM/gtx950.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,+invtsc,+avx,+avx2,+aes,+xsave,+xsaveopt,vmware-cpuid-freq=on,'/> </qemu:commandline> </domain>

I know that if you use the EFI mounter to have a look in the Clover folder there is a theme folder somewhere. You can just remove the xmas theme and you should be left with the default one. Pretty sure there will be a config for the other thing but not had time to check sorry.

This looks interesting, any source articles or info as to what each of those does. Any idea how much improvement it makes?

I have exactly the same card as @gridrunner as I bought it after he recommended it. Mine works fine but I only have devices plugged directly into the card, no hub used.

Is iMessage working for you? I had to follow some guide on TonyMac86 about generating a new valid serial number first. Apple does some checking in the back end for things like iMessage and maybe that also applies to the App Store? by default the serial number created by clover might not be a valid one, you have to regenerate then check with Apple to make sure it is genuine.

No it is common, I ignore it. Doesn't seem to affect anything.

If it was badly formed XML then I don't think it would save. There were a bunch of subtle differences but nothing which stood out to me. Oh well, I'll just keep this Ubuntu VM about to edit every now and again.

So in the end I created a new VM and edited it with Virt Mgr form an Ubuntu VM as suggested slightly earlier. That seemed to resolve all my issues, passthough now working again. I can't quite work out what the changes in the XML were though.

That happened to me a few months ago. I assumed I had just done something daft and not realised. To access remotely I have OpenVPN installed in a docker to get onto my local network then access unRaid as normal

Anyone know how I make use of the previous folder on the tab drive to try and boot the previous version to try that out? Update: didn’t make any difference. Something else is going on bit frustrating

Moving to another slot with a different card in the first did nothing. I honestly cannot see what has gone wrong. Just to be clear, I have had Windows and OSX VMs working fine for with GPU passthrough months on 6.3 and the 6.4 RCs. Only when I moved to official 6.4 did it all stop working.

I am getting no display out of it at all, either OSX or Windows booting. I am passing a GTX 950 in both cases. I'll check my bios (ASRock Extreme 6 X99 - I don't remember seeing anything like that in there but will check again) The card is sitting in the first slot currently but will try a little later moving it to another one.

in fact it isn't working on Windows either. I just have a general GPU passthrough issue I think ever since moving to 6.4 full version

Well that didn't work tried dumping the ROM again as well. 2018-01-19 10:50:53.254+0000: Domain id=1 is tainted: high-privileges 2018-01-19 10:50:53.254+0000: Domain id=1 is tainted: custom-argv 2018-01-19 10:50:53.254+0000: Domain id=1 is tainted: host-cpu 2018-01-19T10:50:53.306628Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/1 (label charserial0) 2018-01-19T10:50:55.302315Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,id=hostdev0,bus=pci.3,addr=0x0,romfile=/mnt/cache/downloads/gtx950mw.dump: Failed to mmap 0000:03:00.0 BAR 3. Performance may be slow

yes I am coming to the same conclusion. I have ordered a super cheapo passive card to stick in so hopefully unRAID will use that and I can safely assign the main card to the VM. Does anyone know how unRAID decides? does it matter as it will switch to the other if I try to assign one to a VM?

2018-01-17T08:25:01.051885Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.4,addr=0x0,romfile=/mnt/disks/VMNVM/highsierra/gtx950.rom: Failed to mmap 0000:02:00.0 BAR 3. Performance may be slow usb_desc_get_descriptor: 2 unknown type 33 (len 10) usb_desc_get_descriptor: 1 unknown type 33 (len 10) usb_desc_get_descriptor: 1 unknown type 33 (len 10) 2018-01-17T08:26:15.112664Z qemu-system-x86_64: vfio_region_write(0000:02:00.0:region3+0x1088, 0x7ffe11,8) failed: Device or resource busy 2018-01-17T08:26:15.128268Z qemu-system-x86_64: vfio_err_notifier_handler(0000:02:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest 2018-01-17T08:26:15.221718Z qemu-system-x86_64: vfio_err_notifier_handler(0000:02:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest 2018-01-17T08:26:15.221765Z qemu-system-x86_64: vfio_err_notifier_handler(0000:02:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest yeah it is just an SSD unassigned device that I run VMs from. The High Sierra VM is running off another unassigned NVMe drive. I copied the ROM file to the same location as the disk images on the NVMe just to check and still get the same issue. I am thinking this might be to do with whether it is the only graphics card. I will need to test when I get back home by throwing in another old card I have.

Do you have any other graphics in your system like built in Intel or another card?

Has anyone got PCI graphics passthrough working on OSX with an NVidia card and did you have to do a BIOS dump for the card and include in the XML? I can see on @gridrunner's latest video for Windows he hasn't dumped a bios to get the card working in Windows...but it still doesn't work for me when I try that (no onboard graphics in my setup) UPDATE: followed GridRunner's video on NVidia as primary card and edited a ROM from techpowerup but still same result with that or my original dumped one. This was working at the weekend when I was on the RC21 release.

I spoke too soon, mine was working fine but now when I start my VM I get an issue in mapping the NVidia rom file (I have a GTX 950) 2018-01-15 09:11:09.940+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.2, hostname: pwnas LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=High Sierra Gfx,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-High Sierra Gfx/master-key.aes' -machine pc-q35-2.10,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -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/a2f6f8c2-8b33-11d9-6a41-87fa8f45543f_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 16384 -realtime mlock=off -smp 8,sockets=1,cores=4,threads=2 -uuid 920636ba-12a2-ee7c-eff6-a6575d058a7c -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-High Sierra Gfx/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on 000-82545em,netdev=hostnet0,id=net0,mac=52:54:00:8b:8f:ec,bus=pci.2,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev 'socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-2-High Sierra Gfx/org.qemu.guest_agent.0,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=02:00.0,id=hostdev0,bus=pci.4,addr=0x0,romfile=/mnt/disks/VMSSD/vbiosbound.rom -device vfio-pci,host=02:00.1,id=hostdev1,bus=pci.5,addr=0x0 -device vfio-pci,host=07:00.0,id=hostdev2,bus=pci.6,addr=0x0 -device virtio-balloon-pci,id=balloon0,bus=pci.3,addr=0x0 -usb -device usb-mouse,bus=usb-bus.0 -device usb-kbd,bus=usb-bus.0 -smbios type=2 -cpu Penryn,vendor=GenuineIntel,kvm=on,+invtsc,vmware-cpuid-freq=on, -msg timestamp=on 2018-01-15 09:11:09.941+0000: Domain id=2 is tainted: high-privileges 2018-01-15 09:11:09.941+0000: Domain id=2 is tainted: custom-argv 2018-01-15 09:11:09.941+0000: Domain id=2 is tainted: host-cpu 2018-01-15T09:11:09.987833Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2018-01-15T09:11:11.798850Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.4,addr=0x0,romfile=/mnt/disks/VMSSD/vbiosbound.rom: Failed to mmap 0000:02:00.0 BAR 3. Performance may be slow 2018-01-15T09:12:33.812985Z qemu-system-x86_64: vfio_region_write(0000:02:00.0:region3+0x1088, 0x7ffe11,8) failed: Device or resource busy 2018-01-15T09:12:33.830419Z qemu-system-x86_64: vfio_err_notifier_handler(0000:02:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest I used to always get the red line about tainted domains, the yellow part about the ROM is new and stopping VM from booting. part where I passthrough (video and sound PCI devices from the graphics card) :- <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <rom file='/mnt/disks/VMSSD/vbiosbound.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev>