Open demiph opened 3 years ago
Also worth mentioning we would see a failure in the vmkernel log files regarding "unable to assign BAR resources for device 0000:44:00.0" The BAR allocation policy was changed from 2 to 1, and we no longer see the error, but the original problem is still unfixed
Some additional troubleshooting info:
vmkdevmgr.log
Module 'atlantic' load by uid=0 who=root successful
Successfully bound device 0x790243054340328a to driver atlantic (module 45) for bus=pci addr=s00000001:02.00 id=1d6a80b116b872e5020000
Failed to set driver for 0x54ed430543403adf: Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.: Not found
Device 0x54ed430543403adf was not bound to driver atlantic (module 45) for bus=pci addr=s00000002:02.00 id=1d6a80b116b872e5020000
vmkernel.log
Device: 400: Found driver atlantic for device 0x790243054340328a
Device: 1585: Registered device: 0x430543401220 pci#s00000001:02.00#0 com.vmware.uplink (parent=0x790243054340328a)
atlantic: Claiming PCI device [0x1d6a:0x80b1 0x72e5:0x16b8]
Device: 2813: Module 45 did not claim device 0x54ed430543403adf
Hi @demiph, Could you please share log when you see issue ?
The BAR allocation policy was changed from 2 to 1 How did you change policy?
Hi,
I am testing using 2 Marvell Felicity Network Adapters with ESXi 7.0 U2, and I am unable to get it to work as expected. Only one of the Network Adapters shows up on ESXi while the other can only be seen with a lspci
We are running the latest firmware version on the NICs, and we are able to get ESXi to recognize each adapter separately but not both at the same time