ich777

But you don,t have to switch it, or why do you want to switch it? You can also buy a HDMI Dummy plug for the iGPU. The VM will start fine if you‘ve assigned the dGPU wirhout switching the HDMI cable.

I‘ve gone through the build log and everything seema fine. I‘ve now read through your first post, please enable the iGPU and set it to the primary graphics device so that Unraid can use it for the console output.

From what I see in your log from your VM RMRR isn't the issue here, please try to create a post in the VM support subforums, I'm not really the expert when it comes to passing through things to VMs...

Please use the support thread for the plugin: Also include your Diagnostics!

Was? Werd ich mir gleich ansehen. Das hängt aber höchstwahrscheinlich nicht mit Unraid RC3 zusammen sondern eher mit CoreFreq. EDIT: Bei mir funktioniert das schon: (wie du unten sehen kannst wird mir auch der Kernel 5.15.27 angezeigt, das ist der von Unraid 6.10.0-rc3) Ist auch deprecated, zumindest meines wissens und wird nicht mehr weiterentwickelt.

Can you post your Diagnostics again, but I don't think that this is a issue with RMRR anymore.

This is really weird because nothing else changed under the hood from what I know. I will take a look at the build logs from the plugin but from what I know it should work just fine, keep in mind this patch is only a workaround and not a real solution to the issue...

Looks like I forgot about this for a long time... I actually stopped creating containers for games that I personally don't own because giving support for such containers is a real nightmare for me.

Of course not. Tick the boxes at System Devices and at the bottom click „Bind on Reboot to VFIO“ and reboot afterwards. This question would be better suired in the VM sub forums how to bind cards, RMRR is working from what I see.

The main issue is that GVT-g isn‘t officially supported on OSX. I know that there are a few modifications and tutorials out there that maybe can get it to work but the last time that I‘ve tried it I couldn’t get it to work but I also have to point out that I‘m not really a OSX guy.

I think because 11 is used for Unraid… Is this a quad gigabit card? I would recommend that you bind all NICs that you want to use to VFIO and then try to pass them through.

Because I've quoted the part from the RC3 Changelog where it says that it's now part of Unraid itself, anyways here is the link: Click Those two posts are now also deprecated because it's part of Unraid itself. Go to the Unraid "Main" tab -> click on your USB Boot device (blue text "flash") -> at the green Syslinux configuration add this (just add it if you have any other things there): Click on the bottom on "Apply" and reboot your server.

Blacklist the driver like @SimonF mentioned and Intel-GPU-TOP will take care of the probe. Don't forget to reboot after you've blacklisted the driver and maybe post the Diagnostics afterwards. To blacklist the driver run this from an Unraid terminal: mkdir -p /boot/config/modprobe.d echo "blacklist i915" > /boot/config/modprobe.d/i915.conf

Have you yet tried to reboot the server? You can also try to upgrade to RC3 and see if it starts working there. I have now tried the exact same driver on my test machine on Unraid 6.10.0-rc2 and it works flawlessly (with a Nvidia T400).

I think you didn‘t read the changelog: The RMRR patch is integrated directly into Unraid since RC2 and you only have to add this: intel_iommu=relax_rmrr to your syslinux.conf and it will work right OOB since RC2.

Bekanntes Problem unter 6.9.2 wird mit 6.10.0 behoben. Für was brauchst du den GUI modus? konfiguration über das Webinterface nicht möglich?

If it's a Alder Lake chip I don't think that it will work properly...

From what I see this won't change anything, but at least you can try it. In your case (or I think for all Alder Lake chips) the iGPU doesn't reset properly with the current Kernel. On what Unraid version are you? Can you share your Diagnostics?

As @SimonF pointed out, what CPU are you using, can you upload your Diagnostics please? If you are talking about Alder Lake I would really appreciate if you are upload your Diagnostics.

Exactly, this is why I don't switch over to 2.0-latest, it sometimes crashes even the host. If you really want to use 2.0-latest then please edit it so that it works for you.

Try to run fix permissions from the GUI for your isos path.

Have you restarted the Docker service or your server? Please post your Diagnostics.

Just to let you guys know, a update for ZFS is available ZFS v2.1.3 (Changelog) The new ZFS packages where built yesterday for Unraid versions: 6.9.2 6.10.0-rc2 6.10.0-rc3 To pull the update please restart your server or upgrade to Unraid 6.10.0-RC3 if you want to try the Unraid RC series (if you restart your server make sure that your Server has a active internet connection on boot and is actually able to connect to the internet). Thank you @steini84 for the plugin.

Are you sure that your "Default ISO storage path" is valid? No issue over her: (except for the slow download speed)

Can you try to add: i915.enable_guc=0 to your syslinux.conf and test if it crashes again, if yes please edit this entry and try: i915.enable_guc=2 and report back if it's the same. Have you guys connected a Monitor or a HDMI Dummy plug to your iGPU? It is much recommended to at least attach a HDMI Dummy plug to avoid Kernel Panics with newer Kernels. Please don't do this, Intel-GPU-TOP will handle the force probe, just blacklist the i915 module, you even don't need to do a chmod -R 777 /dev/dri because Unraid does this itself if the path is found.