SimpleDino

@ghost82 The issue has been solved, again thanks for the help. The changes I made and steps taken: 1. Changed the GPU to the 2nd slot and re-dumped the vbios. 2. Input the edit text from you and changed of course from 0e to 0f accordingly to correct slot. 3. Removed the USB mouse also and replaced it with a USB Logitec unifier with mouse and keyboard. (maybe this also eliminated some errors?) 4. RUN AMD reset bug Script so no reboot needed. 4.Always made sure to RUN the macos vm_helper script after changes. 5. Succes! display output works perfectly! 6. For remote access (outside of home network), I've setup teamviewer which works flawlessly. Better than NoMachine, no port forwarding needed. Issues left, how to make the vm autoboot without me needing to press enter in bootloader. Best regards,

@nug, did you ever get this question answered? Br,

On the contrary, you've been of great help! I will try the slot change when I have the time. Thanks!

@vxch Did you ever solve this for MacOS VM? Or did you just change to the secondary GPU slot? Br,

No, the system has two video cards. 1st primary slot - AMD RX 480 Connected to display with HDMI cable (works perfectly when win11 vm is running) 2nd secondary slot - Nvidia P2000 with DP Dummy Plug (used for plex transcoding only) I absolutely have no idea if unraid switches between these, all I can mention when no vm is running the display shows no signal detected and as mentioned above same message is diplayed if macos is running or not. Please see attached diag. tower-diagnostics-20210722-1350.zip

Do you think maybe multifunction=on should be applied on the sound also in the xml?

Hi, I tried it now after the changes and a amd gpu bug reset but no display output , one thing to mention is that the gpu is in the primary gpu slot. Does that affect anything? Here is the new log: -device e1000-82545em,netdev=hostnet0,id=net0,mac=52:54:00:e4:da:ce,bus=pci.1,addr=0x0 \ -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:0e:00.0,id=hostdev0,bus=pci.3,multifunction=on,addr=0x0,romfile=/mnt/user/isos/vbios/rx 480v2.rom' \ -device vfio-pci,host=0000:0e:00.1,id=hostdev1,bus=pci.3,addr=0x0.0x1 \ -device usb-host,hostbus=5,hostaddr=6,id=hostdev2,bus=usb.0,port=2 \ -usb \ -device usb-kbd,bus=usb-bus.0 \ -device '************************' \ -smbios type=2 \ -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2021-07-22 11:37:52.547+0000: Domain id=13 is tainted: high-privileges 2021-07-22 11:37:52.547+0000: Domain id=13 is tainted: custom-argv 2021-07-22 11:37:52.547+0000: Domain id=13 is tainted: host-cpu char device redirected to /dev/pts/2 (label charserial0) 2021-07-22T11:37:52.614986Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.616758Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.618153Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.619304Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.620615Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.621913Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.622898Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.623867Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.624902Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.625784Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.626708Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.627566Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.628506Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.629434Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.630358Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:52.631286Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-22T11:37:58.257929Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0e:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest 2021-07-22T11:37:58.258039Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0e:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest 2021-07-22T11:38:44.521096Z qemu-system-x86_64: terminating on signal 15 from pid 28679 (/usr/sbin/libvirtd) 2021-07-22 11:38:46.723+0000: shutting down, reason=destroyed

Hi thanks for finding the error, I will try the change now. Regarding vbios and amd bug, I have delt with those issues, the vbios is being dumped with the Spaceinvader method and amd gpu reset bug also. Is there any extra change needed for the vbios? I thought not when dumping your own? Br,

Hi, I've got issue with MacOS Big Sur VM, I've followed SpaceInvader's One guide to the letter but no succes when passing through GPU. The VM starts successfully with GPU and sound passthrough but (hdmi) display does NOT detect any signal at all from the VM. And for example on windows 11 VM everything works just fine with passthrough etc. but not MacOS. How can I fix the issue? or rather what is the problem that prevents display output? Here is a log from the VM, there is a few errors: -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:0e:00.0,id=hostdev0,bus=pci.3,addr=0x0,romfile=/mnt/user/isos/vbios/rx 480v2.rom' \ -device vfio-pci,host=0000:0e:00.1,id=hostdev1,bus=pci.4,addr=0x0 \ -device usb-host,hostbus=5,hostaddr=5,id=hostdev2,bus=usb.0,port=2 \ -usb \ -device usb-kbd,bus=usb-bus.0 \ -device '************************' \ -smbios type=2 \ -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2021-07-21 14:48:35.448+0000: Domain id=12 is tainted: high-privileges 2021-07-21 14:48:35.448+0000: Domain id=12 is tainted: custom-argv 2021-07-21 14:48:35.448+0000: Domain id=12 is tainted: host-cpu char device redirected to /dev/pts/3 (label charserial0) 2021-07-21T14:48:35.516052Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.517561Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.518593Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.519424Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.520368Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.521435Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.522396Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.523457Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.524552Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.525444Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.526346Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.527252Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.528167Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.529115Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.530040Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:35.530979Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2021-07-21T14:48:39.912666Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0e:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest 2021-07-21T14:48:39.912778Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0e:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest 2021-07-21T14:53:42.531522Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] 2021-07-21T14:53:42.531630Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0e:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest 2021-07-21T14:53:42.532672Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0e:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest

@Subtletree Was this ever solved? Having the same issue unfortunately Br,

Hi, Did you ever solve this issue? I'm curious because am in the same boat with this. NoMachine doesnt start when VM is started gpu passth.. Br,

Hi, Do you use a HDMI/DP Dummy plug for headless access with GPU passthrough? If yes, then how do you get access with nomachine from client? does nomachine start automatically after reboot and so on..? Thanks in advance! BR,

Thanks for the quick response, changed the port and now it works perfectly!

Hi, I recently changed motherboard and cpu from Intel to Ryzen 3900x and something weird has happened. All new docker that I try to install (1) failes though visible in dockers but of course won't (2) start and says Execution Error, see pictures and diagnostics file. My already installed Dockers work just fine. Have something changed in shares or alike? Thanks in advance! Br, tower-diagnostics-20210708-1151.zip

The power state has is solved. I applied this solution with some help from the Unraid Reddit forum: This solution changes the power state from P0 to P8 and 20W --> 8W. The P-state will change if the GPU is being passed through for transcoding or VMs. But the solution is temporary, it will reset and not persist after a reboot. Type in console/Terminal: This solution changes the power state from P0 to P8 and 20W --> 8W. The P-state will change if the GPU is being passed through for transcoding or VMs. But the solution is temporary, it will reset and not persist after a reboot. Type in console/Terminal: nvidia-smi --persistence-mode=1 Solution #2. To make it permanent. Download the "User Scripts" plugin. make a new script to run at: "First Array Start Only" and put this into it: #!/bin/bash #nvidia-smi --persistence-mode=1 nvidia-persistenced fuser -v /dev/nvidia*

The UNRAID OS and community is amazing, anything is possible and it's really easy "sometimes" to figure some stuff out but not this time. I have a Nvidia Quadro P2000 GPU and it has a max TDP of 70W and in UNRAID OS it idles at 20W (load = 1 - 2%) with Power State P0 all the time. So in conclusion with Spaceinvader One's video on improving power usage the only solutions for low power usage at idle are: GUI Mode with no VM's activated, only use for transcoding. Headless Mode when being passed through to a VM that is idle. I read somewhere that could force the power state from P0 to P8 for idle to lower the usage but how will that react when for example Plex Transcoding is activated? Will the Power state change so that the GPU actually transcodes? Or will it remain in P8 state because it has been forced and no transcodes? The reason for this post is obvious, I want to lower the idle power usage from 20W to 6-10W Best regards,

Thanks for the help, I need to polish my googling skills even more!

Hi, So I have an issue with the Unraid - USB Flash Creator. When trying to write to usb the process gets stuck at "syncing file system...". How long does it take really to sync and finish writing? been waiting for 30mins now and still stuck. please see picture. Best regards, A total newbie in the Unraids vast world!