Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Nvidia passthrough not working on Linux guests with 6.4.0?

Featured Replies

After upgrading to 6.4.0, none of my Linux VMs seem to work properly when I pass through my GTX 960 to those VMs. I currently have 7 VMs -- one Windows VM and 6 Linux VMs.

Four of them are Gentoo with different configurations within Gentoo. The other two are Arch and Fedora. All of these should be using roughly similar XMLs as I've not made any changes to them outside of the webUI.

 

When I boot any of the gentoo or Arch VMs, they immediately hang. I see the message that the kernel and initial ramdisk are loading, and then it gets no further than that. If I boot back to the 6.3.5 image (ie; hit tab to change the command line and add previous/ to the bz* references), all my gentoo and Arch VMs boot fine without making any other changes.

 

Fedora is the exception that can fully boot up in 6.4.0. I presume the difference between Arch, gentoo and Fedora is that neither Arch nor gentoo have nouveau support enabled, while Fedora has it enabled by default. However, one of the first things I did after installing Fedora was enable the rpmfusion repo and install the proprietary drivers. I can get to the desktop and nouveau is loaded according to both lsmod and glxinfo. Yet, I look at the commandline and nouveau is blacklisted and it says to load nVidia DRM. I don't see any reference to failing to load the proprietary nvidia drivers in the dmesg.

 

The gentoo and Arch VMs also seem to boot up fine if I disable my passthrough and change the Video to VNC.

 

I don't even know if it's a problem with passhthrough generally. I'm typing this from my Windows VM and at the very least, Windows is reporting that it's using the 960. Stuff seems to be getting passed through to Linux, as evidenced by the behavior in Fedora. I'm passing through some USB controllers and a sound card which is how I get mouse, keyboard and sound to my VMs.

 

I've also attached some info in case it helps -- including diagnostics from my server and some example libvirt XMLs in case that might help. The Windows one is the working one with GPU passthrough, while the Linux one is not. The qemu logs in the diagnostic zip are also from me attempting to run Arch, Gentoo and Fedora in 6.4.0 with passhthrough -- nothing particularly relevant as far as I can tell though.

Windows 10 - haibane.xml

Gentoo - kagura (unstable).xml

mayuko-diagnostics-20180115-0940.zip

I tried out the UEFI 6.4 pre release images back before I bought and went stable. I could not get nvidia passthrough to work at all on anything except one of the linux distros (I think ubuntu) I switched to 6.3.5 and everything was fine. I upgraded yesterday to 6.4 but left UEFI off, and windows at least is still fine, but I'm holding back switching to UEFI because of earlier problems. Will check my linux vm's tonight, but it might be worth disabling UEFI if you enabled that when you switched.

  • Author

When you're talking about UEFI, are you talking about booting unRAID with UEFI or the VMs? If unRAID, I haven't made any changes relating to that. I have always created my VMs to boot via UEFI..

 

Small update.

 

I was talking with someone on reddit about this earlier today, and it occurred to me that I hadn't tried defining any new VMs in 6.4.0 yet. There does seem to be some incompatibility between 6.3.5 and 6.4.0 (or maybe the way I created the XMLs), since when I edit XMLs in 6.4.0, they are no longer visible in 6.3.5.

 

I've tried two things so far:

  • Defining a new XML for Arch and referencing the existing install vdisk
  • Doing a clean install of.. something.

Creating a "new" VM for Arch and then referencing the vdisk image in that new VM didn't work. I booted to the Arch install ISO, did an arch-chroot and then did a grub-install to re-install the bootloader on the "new" VM. I rebooted and faced the same behavior as previously -- it boots, says loading kernel/initial ramdisk and then immediately hanged.

 

I ended up doing a new install of Fedora. I had some issues with RPM Fusion being down, but I am now typing this post from Fedora with nvidia drivers.Still not exactly clear what the actual problem is, but it seems to be working so far. I'm hoping I don't need to reinstall gentoo. ;) I'll do some more experiments with that.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.