Recently my motherboard died, and I replaced it with a new motherboard of the same model (same hardware rev, as well). I was hoping that Unraid would be able to just pick up and run without having to modify much, which it has, except that my windows VM, which was working perfectly, will no longer start the onboard ethernet adapter that I'm passing through.

 

Windows Device Manager gives "code 10" "cannot start". This is the case both in the VM I had been using, and a from scratch install I just tried.

 

I've noticed that Unraid (and windows) is showing my NIC as "(2)", as in this:

IOMMU group 15:	[8086:15b8] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V

I've also seen error messages that "eth4 is missing" when the system is booting, but I haven't been able to find that in the System Log. (I've got a 4 port intel nic that is eth0-3.)

 

This is the XML for the new win10 VM I just created: https://pastebin.com/sJtU0b9M

And I have this in my syslinux config at boot:

append pcie_acs_override=downstream vfio-pci.ids=8086:15b8 pci-stub.ids=10de:1aec,10de:1aed initrd=/bzroot 

 

Forgive me if I should have included more troubleshooting information - I'm fairly new at unraid. Thanks in advance for any help you might be able to provide!

unraid-diagnostics-20191014-2012.zip

Edited October 14, 20196 yr by supagold
Added Diagnostics

22 minutes ago, supagold said:

included more troubleshooting information

Tools - Diagnostics.

16 minutes ago, Squid said:

Tools - Diagnostics.

Added to my original post.

1 hour ago, supagold said:

I've also seen error messages that "eth4 is missing" when the system is booting

You need to edit the file network.cfg in the /config folder on your USB stick.

Remove this part

IFNAME[1]="eth1"
PROTOCOL[1]="ipv4"
USE_DHCP[1]="yes"
IFNAME[2]="eth4"
PROTOCOL[2]="ipv4"
USE_DHCP[2]="yes"

Change this part

SYSNICS="1"

You need to restart the system to make these changes effective.

 

1 hour ago, supagold said:

Windows Device Manager gives "code 10" "cannot start"

Is the ethernet controller selectable as a PCI device in the VM settings?

If yes, try to unselect and apply, and reselect and apply.

Thanks for the advice @bonienl - before I make the change, can I ask what the SYSNICS configuration does? 

SYSNICS tells how many active network interfaces are present.

In your case it is one (eth0)

OK, that did fix my issue. Thanks!

 

However, now the VNC adapter won't connect. It comes up, then nearly instantly fails with "Failed to connect to server". I'm not sure what logs to pull to diagnose this.

11 minutes ago, supagold said:

However, now the VNC adapter won't connect

Re-apply your VM settings and try again.

Yeah, I did that. I also disabled passthrough for the onboard NIC I was testing and have it just on br0, and tried updating the virtual MAC address. Any other ideas?