December 8, 20205 yr Unraid 6.8.3 Intel X540-T2 NIC AMD firepro W2100 Windows 10 VM on vlan if that matters When I boot Unriad without the gfx card passedthrough my dashboard shows my 10gbe link and everything is all good. As soon as I passthrough the gfx card and start the VM the link shows 1gb on the dashboard. I will attach my diag files incase anyone can help me out. I will also include a clip of the logs after the passthough is set and the VM is booting. Dec 7 22:46:21 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Down Dec 7 22:46:21 Tower kernel: br0: port 1(eth0) entered disabled state Dec 7 22:46:21 Tower kernel: br0.100: port 1(eth0.100) entered disabled state Dec 7 22:46:24 Tower ntpd[3218]: Deleting interface #2 br0, 192.168.1.12#123, interface stats: received=1021, sent=1038, dropped=0, active_time=215923 secs Dec 7 22:46:24 Tower ntpd[3218]: 216.239.35.0 local addr 192.168.1.12 -> <null> Dec 7 22:46:24 Tower ntpd[3218]: 216.239.35.4 local addr 192.168.1.12 -> <null> Dec 7 22:46:24 Tower ntpd[3218]: 216.239.35.8 local addr 192.168.1.12 -> <null> Dec 7 22:46:24 Tower ntpd[3218]: 216.239.35.12 local addr 192.168.1.12 -> <null> Dec 7 22:46:40 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: None Dec 7 22:46:40 Tower kernel: br0: port 1(eth0) entered blocking state Dec 7 22:46:40 Tower kernel: br0: port 1(eth0) entered forwarding state Dec 7 22:46:40 Tower kernel: br0.100: port 1(eth0.100) entered blocking state Dec 7 22:46:40 Tower kernel: br0.100: port 1(eth0.100) entered forwarding state Dec 7 22:46:41 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Down Dec 7 22:46:41 Tower kernel: br0: port 1(eth0) entered disabled state Dec 7 22:46:41 Tower kernel: br0.100: port 1(eth0.100) entered disabled state Dec 7 22:46:45 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Up 10 Gbps, Flow Control: None Dec 7 22:46:45 Tower kernel: br0: port 1(eth0) entered blocking state Dec 7 22:46:45 Tower kernel: br0: port 1(eth0) entered forwarding state Dec 7 22:46:45 Tower kernel: br0.100: port 1(eth0.100) entered blocking state Dec 7 22:46:45 Tower kernel: br0.100: port 1(eth0.100) entered forwarding state Dec 7 22:46:47 Tower ntpd[3218]: Listen normally on 3 br0 192.168.1.12:123 Dec 7 22:46:47 Tower ntpd[3218]: new interface(s) found: waking up resolver Dec 7 22:46:58 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Down Dec 7 22:46:58 Tower kernel: br0: port 1(eth0) entered disabled state Dec 7 22:46:58 Tower kernel: br0.100: port 1(eth0.100) entered disabled state Dec 7 22:47:01 Tower ntpd[3218]: Deleting interface #3 br0, 192.168.1.12#123, interface stats: received=3, sent=9, dropped=0, active_time=14 secs Dec 7 22:47:01 Tower ntpd[3218]: 216.239.35.0 local addr 192.168.1.12 -> <null> Dec 7 22:47:01 Tower ntpd[3218]: 216.239.35.4 local addr 192.168.1.12 -> <null> Dec 7 22:47:01 Tower ntpd[3218]: 216.239.35.8 local addr 192.168.1.12 -> <null> Dec 7 22:47:01 Tower ntpd[3218]: 216.239.35.12 local addr 192.168.1.12 -> <null> Dec 7 22:47:18 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: None Dec 7 22:47:18 Tower kernel: br0: port 1(eth0) entered blocking state Dec 7 22:47:18 Tower kernel: br0: port 1(eth0) entered forwarding state Dec 7 22:47:18 Tower kernel: br0.100: port 1(eth0.100) entered blocking state Dec 7 22:47:18 Tower kernel: br0.100: port 1(eth0.100) entered forwarding state Dec 7 22:47:20 Tower ntpd[3218]: Listen normally on 4 br0 192.168.1.12:123 Dec 7 22:47:20 Tower ntpd[3218]: new interface(s) found: waking up resolver tower-diagnostics-20201207-2324.zip Edited December 9, 20205 yr by itskamel
December 9, 20205 yr Author anyone? @limetech could this be a driver issue? Btw I might add, when I was using the onboard nic (1gb) the passthough of the gfx card worked fine. No network issues. Edited December 9, 20205 yr by itskamel
January 4, 20215 yr Author bump, anyone? i have been searching and searching but i do not see anyone else with this issue. I have been told it could possibly be a pic lanes issue but not sure how to confirm.
Archived
This topic is now archived and is closed to further replies.