Evedoescomputerstuff

First. Do VMs work with no GPU and VNC selected? If they do, PCI ACS Override + Multifunction. ACS override is a GUI setting, multifunction can only be enabled for the VM by editing the XML. You may have to play with which ACS override setting to use and the multifunction setting in the XML.

I'd love an explanation, this has been plaguing me for like a week out of the blue and since it's not *actually* broken I haven't waded through all the forum posts to find out why this happens but I am curious! Mainly since I get errors in the log before I even launch the VNC viewer in my browser, yet everything works.... It's just interesting.

At this point since it's fixed, surely you don't want to mess around. However, i'm very curious about the processor now. Since unRAID was unable to boot did you ever try another OS during this process? Mainly just wondering if the processor somehow went bad or theres actually an incompatibility with unRAID? Been planning on trying unRAID with some Ryzen builds (you know the drill, old desktop becomes another server) now that the prices keep falling.

Can we try to see if this is some weird hardware problem unrelated to unraid? Have you ever been able to boot another OS or live image on this machine?

This is probably not the right answer but can you try re-creating your VMs (not their vdisks ) from scratch?

Rad. It's not *exactly* a bug but definitely not intuitive as it could be. The addition of 'optional' devices is sweet.

Yeah, you need to pass through the NVMe PCI-E device directly, not just map the vdisk location to it. In other words, you don't want to be using a vdisk.

That's strange. Can you try CRU to force the resolution / refresh? Display Port? If none of this works, for sanity, do you have another 4K 60hz capable display you can try? Anything to get a different EDID will be helpful.

Did a reboot fix it and allow you to boot the VM again? With USB I agree things can be finnicky, a slightly more surefire system (and one that supports hotplug) is finding a 'group' of USB ports on your unRAID machine that can be passed through as a USB controller. Those ports will become unavailable to unRAID or other things on your server, but will in ideal circumstances, function as regular hotpluggable USB ports to the VM. I highly recommend considering copying the 'xml' (you don't need to use XML for most VM config tasks) at each stage as you're working through making the VM. It makes it much easier to revert to something that did work. Furthermore, as you're figuring this out, copying the vdisk image file for your VM at various stages is useful as well. It's a snapshot of the computer essentially and makes trying something out hassle free as you can always restore the working image. This is actually one of the reasons I *really* like the VM system (once it works, passing stuff through is always going to be a bit of trial and error), snapshotting and quickly switching through images can be helpful if you're trying things liable to break an OS, or if you're developing something for a specific config. As mentioned by others, passing through an iGPU isn't as trivial as it you'd think due to how IOMMU assignments get sliced up and parted out so to speak. That's why a supported dGPU is often easier to make work in a VM.

I'm not an expert, hopefully one of the more seasoned unRAID VM users will chime in. The only other thing I noticed was "pc-i440fx-6.2" . I've been using QXL with much better results when dealing with physical hardware. Try that. Searching on the forums leads to a few other people dealing with the same error.

I have a p400 in one of my unraid builds passed through to a VM for basic desktop accel (it used to be for transcoding). Works great. The vBios is probably what you're missing since you didn't mention it and it's easy to overlook. I just grabbed a vbios from TechPowerUp. The Quadro cards aren't as 'AIB'd' to death like consumer cards so finding a compatible vbios is easy. If you for some reason can't find your card on TechPowerUp, you might have to dump the vBios yourself. There's a script that allegedly works but hasn't for me in the past. The *easiest* way to reliably extract it is to toss it in a computer, boot up windows and use GPU-Z to save it to a file. Place the resulting file on your server in one of your shares (like isos alongside your OS install images), then on the VM config GUI in the GPU section, locate your bios file. If you're using it for transcode that means the GPU works (in theory) and that you probably have the same nvidia drivers for Unraid as I do. I don't *think* you need the Unraid nvidia plugin just to pass the GPU through but I figured I'd mention it since it is running in my setup. The p400 I have is most likely the same as yours and I was actually blown away at how easy it was to get working with a tiny bit of tinkering. As for passing iGPUs? I haven't played with it but that sounds like way too much of a headache. GPU prices are crashing so depending on what your goal is for pass through, something cheap might work wonders and be significantly easier to get working. I tried TrueNAS Scale on the first RC (so please take this with a grain of salt) and didn't like it. Docker configuration sucked, charts were meh, portainer helped a bit. I was getting really bizarre slow downs and lockups without much logic behind them and felt as though with my more 'JBOD' storage arrangement that it wasn't right for me. If you don't need ZFS and you already use unRAID, I can't think of a major reason to switch over IMO.

Curious too as i'm looking at Epyc builds.

Not an expert by any stretch but multifunction may help you here. The GUI doesn't have an option for it (so you'll have to edit XML, and if you use the GUI to make any changes, re-edit your XML) . In the XML, you're looking for the address block below your rom file, add to the end of it before the /> multifunction='on' <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/vm/Gigabyte.GT610.1024.130107.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> should be <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/vm/Gigabyte.GT610.1024.130107.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> Do you need the built in VNC? I've found having it as a device causes problems for my VMs with real GPUs occasionally.

I've had random SMB issues like this before, especially dealing with specific hardware / software combos. Can you try to make another unraid user with read access to the media share?

AVAHI is harder than it seems to get running on some containers, at least with the tiny bit I played with it. Sucks but what can you do. Sort of related, a docker that can essentially act as an internal reverse proxy that supports broadcasting a bunch of .local mDNS domains and then routing said requests would be absurdly useful. Does that exist?