Description of problem: 3820C NIC driver missing/obsolete from RHVH4.1.5 which is based upon RHEL7.4. However, in RHEV4.1.1 release which is based upon RHEL7.3 these drivers were present and we didn't require any manual intervention in terms of applying drivers manually. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. After i install RHVH node version 4.1.5 which is based upon kernel RHEL 7.4, i noticed that 3820C NIC which are configured for SRIOV was not detected on the RHEV-M GUI. 2. We ran the lspci command from the RHVH hosts and conform that PF was not detected on NIC's. Please see below. [root@host1 ~]# lspci -vvv | egrep "SR-IOV|Ethernet" 0c:00.0 Ethernet controller: Broadcom Limited BCM57840 NetXtreme II Ethernet Multi Function (rev 11) 0c:00.1 Ethernet controller: Broadcom Limited BCM57840 NetXtreme II Ethernet Multi Function (rev 11) 0c:00.2 Ethernet controller: Broadcom Limited BCM57840 NetXtreme II Ethernet Multi Function (rev 11) 0c:00.3 Ethernet controller: Broadcom Limited BCM57840 NetXtreme II Ethernet Multi Function (rev 11) 0c:00.4 Ethernet controller: Broadcom Limited BCM57840 NetXtreme II Ethernet Multi Function (rev 11) [root@host1 ~]# 3. Then i tried to install 3820C NIC driver manually on RHVH host via below link. But i couldn't install it because of other dependencies . Please see below. 3820C spec: https://www.hpe.com/h20195/v2/getpdf.aspx/c04815124.pdf?ver=1.0 3820C driver: http://h20564.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=1008615171&swLangOid=8&swEnvOid=4176 [root@host1 ~]# yum install kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64.rpm Loaded plugins: imgbased-persist, product-id, search-disabled-repos, subscription-manager Examining kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64.rpm: kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64 Marking kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package kmod-netxtreme2.x86_64 0:7.14.19-1.rhel7u3 will be installed --> Processing Dependency: kernel(zlib_inflate) = 0x881039d0 for package: kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64 --> Processing Dependency: kernel(zlib_inflateEnd) = 0x77ecac9f for package: kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64 --> Processing Dependency: kernel(zlib_inflateInit2) = 0x4211c3c1 for package: kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64 --> Finished Dependency Resolution Error: Package: kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64 (/kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64) Requires: kernel(zlib_inflate) = 0x881039d0 Installed: kernel-3.10.0-693.el7.x86_64 (installed) kernel(zlib_inflate) = 0x581f98da Installed: kernel-lt-4.4.84-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflate) = 0x581f98da Installed: kernel-ml-4.12.9-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflate) = 0x581f98da Error: Package: kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64 (/kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64) Requires: kernel(zlib_inflateEnd) = 0x77ecac9f Installed: kernel-3.10.0-693.el7.x86_64 (installed) kernel(zlib_inflateEnd) = 0x107e5878 Installed: kernel-lt-4.4.84-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflateEnd) = 0x107e5878 Installed: kernel-ml-4.12.9-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflateEnd) = 0x107e5878 Error: Package: kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64 (/kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64) Requires: kernel(zlib_inflateInit2) = 0x4211c3c1 Installed: kernel-3.10.0-693.el7.x86_64 (installed) kernel(zlib_inflateInit2) = 0x35a88f28 Installed: kernel-lt-4.4.84-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflateInit2) = 0x35a88f28 Installed: kernel-ml-4.12.9-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflateInit2) = 0x35a88f28 ********************************************************************** yum can be configured to try to resolve such errors by temporarily enabling disabled repos and searching for missing dependencies. To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf ********************************************************************** Error: Package: kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64 (/kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64) Requires: kernel(zlib_inflate) = 0x881039d0 Installed: kernel-3.10.0-693.el7.x86_64 (installed) kernel(zlib_inflate) = 0x581f98da Installed: kernel-lt-4.4.84-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflate) = 0x581f98da Installed: kernel-ml-4.12.9-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflate) = 0x581f98da Error: Package: kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64 (/kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64) Requires: kernel(zlib_inflateEnd) = 0x77ecac9f Installed: kernel-3.10.0-693.el7.x86_64 (installed) kernel(zlib_inflateEnd) = 0x107e5878 Installed: kernel-lt-4.4.84-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflateEnd) = 0x107e5878 Installed: kernel-ml-4.12.9-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflateEnd) = 0x107e5878 Error: Package: kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64 (/kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64) Requires: kernel(zlib_inflateInit2) = 0x4211c3c1 Installed: kernel-3.10.0-693.el7.x86_64 (installed) kernel(zlib_inflateInit2) = 0x35a88f28 Installed: kernel-lt-4.4.84-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflateInit2) = 0x35a88f28 Installed: kernel-ml-4.12.9-1.el7.elrepo.x86_64 (installed) kernel(zlib_inflateInit2) = 0x35a88f28 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles —nodigest Actual results: RHVH 4.1.5 hosts should have 3820C NIC drivers out of the box. Expected results: RHVH 4.1.5 hosts should have 3820C NIC drivers out of the box. Additional info:
which rpm used to deliver this driver in rhel-7.3.z ?
Apparently, when the end user customer did the installation, the drivers they needed just worked with 7.3. I'm told they did not install any specific RPMs to get what they needed. Looking at https://access.redhat.com/articles/2881171, I see it needed a driver installation disk for 7.2. But not for 7.3 or 7.4. Note that the raw card does show up. But what does not show up is SR-IOV support and that's what they need. Puneet just confirmed with the customer that they did not install anything special for SR-IOV support for this card.
No changes were made in the packages we pull from platform in 4.1.5, so I'd expect this to be the same. Did some platform switch for sr-iov change?
This is what we have done today so far: 1) we have updated the firmware (firmware-nic-qlogic-nx2-2.19.22-1.1.x86_64.rpm) as suggested by HP team. Please see below output of lspci command. 2) we also added parameter "add_efi_memmap? into the kernel boot parameters. Please see below. But still RHEV-M is not able to recognize 3820C NIC as SRIOV enabled interface. HP team also asked to update the driver (kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64.rpm) which is based upon RHEL7.3. But since 4.1.5 is based upon RHEL7.4 , we couldnt apply their driver to our setup. Kernel boot parameters: Current kernel CMD line:BOOT_IMAGE=/rhvh-4.1-0.20170815.0+1/vmlinuz-3.10.0-693.2.1.el7.x86_64 root=/dev/rhvh/rhvh-4.1-0.20170815.0+1 ro crashkernel=auto rd.lvm.lv=rhvh/rhvh-4.1-0.20170815.0+1 rd.lvm.lv=rhvh/tmp rd.lvm.lv=rhvh/var_log_audit rd.lvm.lv=rhvh/var_log rd.lvm.lv=rhvh/swap rd.lvm.lv=rhvh/var rd.lvm.lv=rhvh/home rhgb quiet LANG=en_US.UTF-8 img.bootid=rhvh-4.1-0.20170815.0+1 intel_iommu=on add_efi_memmap lspci output: [root@host2 firmware-nic-qlogic-nx2-2.19.22-1.1]# lspci -vvv -s 0c:00.0 0c:00.0 Ethernet controller: Broadcom Limited BCM57840 NetXtreme II Ethernet Multi Function (rev 11) Subsystem: Hewlett-Packard Company 3820C 10/20Gb Converged Network Adapter (NPAR 1.5) Physical Slot: 3 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 NUMA node: 0 Region 0: Memory at 93800000 (64-bit, prefetchable) [size=8M] Region 2: Memory at 93000000 (64-bit, prefetchable) [size=8M] Region 4: Memory at 97000000 (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at 97080000 [disabled] [size=512K] Capabilities: [48] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Product Name: Synergy 3820C 10/20Gb CNA Read-only fields: [PN] Part number: 763341-001 [EC] Engineering changes: A-5640 [MN] Manufacture ID: 31 30 33 43 [V0] Vendor specific: 12W PCIeGen3 [V1] Vendor specific: 7.15.16 [V3] Vendor specific: 7.14.37 [V5] Vendor specific: 0A [V6] Vendor specific: 7.14.10 [V7] Vendor specific: 3820C [SN] Serial number: MY570109CS [V2] Vendor specific: 5701 [V4] Vendor specific: 9CDC719DC2A0 [RV] Reserved: checksum good, 202 byte(s) reserved End Capabilities: [a0] MSI-X: Enable+ Count=32 Masked- Vector table: BAR=4 offset=00000000 PBA: BAR=4 offset=00001000 Capabilities: [ac] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd+ ExtTag+ PhantFunc- AuxPwr+ NoSnoop+ FLReset- MaxPayload 256 bytes, MaxReadReq 4096 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L1, Exit Latency L0s <1us, L1 <2us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP+ BadDLLP+ Rollover+ Timeout+ NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [13c v1] Device Serial Number 9c-dc-71-ff-fe-9d-c2-a0 Capabilities: [150 v1] Power Budgeting <?> Capabilities: [160 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [1b8 v1] Alternative Routing-ID Interpretation (ARI) ARICap: MFVC- ACS-, Next Function: 1 ARICtl: MFVC- ACS-, Function Group: 0 Capabilities: [220 v1] #15 Capabilities: [300 v1] #19 Kernel driver in use: bnx2x Kernel modules: bnx2x [root@host2 firmware-nic-qlogic-nx2-2.19.22-1.1]#
"vdsm does not recognize nic as a physical function" is a very different statement from "driver missing". What is the output of more /sys/bus/pci/devices/*/sriov_*
(In reply to Dan Kenigsberg from comment #5) > "vdsm does not recognize nic as a physical function" is a very different > statement from "driver missing". > > What is the output of > > more /sys/bus/pci/devices/*/sriov_* Hi Dan, I dont see this file on my host. Any idea why? [root@host2 devices]# more /sys/bus/pci/devices/*/sriov_* /sys/bus/pci/devices/*/sriov_*: No such file or directory [root@host2 devices]#
From your logs it looks like the bnx2x module is there. I checked anyway to make sure (using rhvh-4.1-20170816.2.el7_4), it is included in the image, and at the same module version also: modinfo -F version /lib/modules/3.10.0-693.1.1.el7.x86_64/kernel/drivers/net/ethernet/broadcom/bnx2x/bnx2x.ko.xz returns: 1.712.30-0 Which is the same module version that is shipped in 7.3 btw, while the rpm from hpe's site provides a kmod version of 1.714.2
(In reply to puneet from comment #6) > I dont see this file on my host. Any idea why? > > [root@host2 devices]# more /sys/bus/pci/devices/*/sriov_* > /sys/bus/pci/devices/*/sriov_*: No such file or directory > [root@host2 devices]# The only thing it tells me is that the problem lies underneath RHV (in kernel/driver/bios/hardware). The kernel does not recognize the devices as sr-iov ones.
Thats very interesting . So you meant to say this issue is more on the hardware side since kernel is not able to recognize the sriov devices ?If yes, HP claims this hardware is sriov enabled. So i'm bit puzzled here. (In reply to Dan Kenigsberg from comment #8) > (In reply to puneet from comment #6) > > > I dont see this file on my host. Any idea why? > > > > [root@host2 devices]# more /sys/bus/pci/devices/*/sriov_* > > /sys/bus/pci/devices/*/sriov_*: No such file or directory > > [root@host2 devices]# > > The only thing it tells me is that the problem lies underneath RHV (in > kernel/driver/bios/hardware). The kernel does not recognize the devices as > sr-iov ones.
Hi Yuval, Yes thats what HPE suggested to use kmod-netxtreme2-7.14.19-1.rhel7u3.x86_64.rpm along with firmware-nic-qlogic-nx2-2.19.22-1.1.x86_64.rpm. Not sure if it makes difference . (In reply to Yuval Turgeman from comment #7) > From your logs it looks like the bnx2x module is there. I checked anyway to > make sure (using rhvh-4.1-20170816.2.el7_4), it is included in the image, > and at the same module version also: > > modinfo -F version > /lib/modules/3.10.0-693.1.1.el7.x86_64/kernel/drivers/net/ethernet/broadcom/ > bnx2x/bnx2x.ko.xz > > returns: > > 1.712.30-0 > > Which is the same module version that is shipped in 7.3 btw, while the rpm > from hpe's site provides a kmod version of 1.714.2
What do you get when you do `modinfo bnx2x` ? Also, did you flash the firmware after you installed the firmware rpm ?
Ok so this is what we have discovered so far. SRIOV feature was disabled in the BIOS of the server because RMRR (Reserved memory region) or HP Shared Memory Features was enabled . Looks like this feature (RMRR) automatically disable the SRIOV feature!!!!! After disabling RMRR (Reserved memory region) or HP Shared Memory Features we were able to set SRIOV as enabled in the BIOS. Now we're building the server from scratch and see if SRIOV is detected on the RHEV-M GUI.
I will provide the output of modinfo bnx2x as soon as sever comes online . (In reply to Yuval Turgeman from comment #12) > What do you get when you do `modinfo bnx2x` ? Also, did you flash the > firmware after you installed the firmware rpm ?
Hi, Pls find below output. And i don't think i have flash the firmware. How to do that ? I just installed firmware RPM. [root@host2 ~]# [root@host2 ~]# modinfo bnx2x filename: /lib/modules/3.10.0-693.2.1.el7.x86_64/kernel/drivers/net/ethernet/broadcom/bnx2x/bnx2x.ko.xz firmware: bnx2x/bnx2x-e2-7.13.1.0.fw firmware: bnx2x/bnx2x-e1h-7.13.1.0.fw firmware: bnx2x/bnx2x-e1-7.13.1.0.fw version: 1.712.30-0 license: GPL description: QLogic BCM57710/57711/57711E/57712/57712_MF/57800/57800_MF/57810/57810_MF/57840/57840_MF Driver author: Eliezer Tamir rhelversion: 7.4 srcversion: D8AE61B75F94EB62743142D alias: pci:v000014E4d0000163Fsv*sd*bc*sc*i* alias: pci:v000014E4d0000163Esv*sd*bc*sc*i* alias: pci:v000014E4d0000163Dsv*sd*bc*sc*i* alias: pci:v00001077d000016ADsv*sd*bc*sc*i* alias: pci:v000014E4d000016ADsv*sd*bc*sc*i* alias: pci:v00001077d000016A4sv*sd*bc*sc*i* alias: pci:v000014E4d000016A4sv*sd*bc*sc*i* alias: pci:v000014E4d000016ABsv*sd*bc*sc*i* alias: pci:v000014E4d000016AFsv*sd*bc*sc*i* alias: pci:v000014E4d000016A2sv*sd*bc*sc*i* alias: pci:v00001077d000016A1sv*sd*bc*sc*i* alias: pci:v000014E4d000016A1sv*sd*bc*sc*i* alias: pci:v000014E4d0000168Dsv*sd*bc*sc*i* alias: pci:v000014E4d000016AEsv*sd*bc*sc*i* alias: pci:v000014E4d0000168Esv*sd*bc*sc*i* alias: pci:v000014E4d000016A9sv*sd*bc*sc*i* alias: pci:v000014E4d000016A5sv*sd*bc*sc*i* alias: pci:v000014E4d0000168Asv*sd*bc*sc*i* alias: pci:v000014E4d0000166Fsv*sd*bc*sc*i* alias: pci:v000014E4d00001663sv*sd*bc*sc*i* alias: pci:v000014E4d00001662sv*sd*bc*sc*i* alias: pci:v000014E4d00001650sv*sd*bc*sc*i* alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* depends: mdio,libcrc32c,ptp intree: Y vermagic: 3.10.0-693.2.1.el7.x86_64 SMP mod_unload modversions signer: Red Hat Enterprise Linux kernel signing key sig_key: 23:43:83:E8:47:F0:F1:6B:2F:41:5C:72:2D:D1:FF:69:86:3C:88:78 sig_hashalgo: sha256 parm: num_queues: Set number of queues (default is as a number of CPUs) (int) parm: disable_tpa: Disable the TPA (LRO) feature (int) parm: int_mode: Force interrupt mode other than MSI-X (1 INT#x; 2 MSI) (int) parm: dropless_fc: Pause on exhausted host ring (int) parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) parm: debug: Default debug msglevel (int) [root@host2 ~]# (In reply to Yuval Turgeman from comment #12) > What do you get when you do `modinfo bnx2x` ? Also, did you flash the > firmware after you installed the firmware rpm ?
As of today we're still not able to enable SRIOV on 3820C adaptor. We're now working with HPE Support/Engineering resources to enable SR-IOV on 3820C adapter.
(In reply to puneet from comment #15) > Hi, Pls find below output. > And i don't think i have flash the firmware. How to do that ? I just > installed firmware RPM. > > [root@host2 ~]# > [root@host2 ~]# modinfo bnx2x > filename: > /lib/modules/3.10.0-693.2.1.el7.x86_64/kernel/drivers/net/ethernet/broadcom/ > bnx2x/bnx2x.ko.xz > firmware: bnx2x/bnx2x-e2-7.13.1.0.fw > firmware: bnx2x/bnx2x-e1h-7.13.1.0.fw > firmware: bnx2x/bnx2x-e1-7.13.1.0.fw > version: 1.712.30-0 > license: GPL > description: QLogic > BCM57710/57711/57711E/57712/57712_MF/57800/57800_MF/57810/57810_MF/57840/ > 57840_MF Driver > author: Eliezer Tamir > rhelversion: 7.4 > srcversion: D8AE61B75F94EB62743142D > alias: pci:v000014E4d0000163Fsv*sd*bc*sc*i* > alias: pci:v000014E4d0000163Esv*sd*bc*sc*i* > alias: pci:v000014E4d0000163Dsv*sd*bc*sc*i* > alias: pci:v00001077d000016ADsv*sd*bc*sc*i* > alias: pci:v000014E4d000016ADsv*sd*bc*sc*i* > alias: pci:v00001077d000016A4sv*sd*bc*sc*i* > alias: pci:v000014E4d000016A4sv*sd*bc*sc*i* > alias: pci:v000014E4d000016ABsv*sd*bc*sc*i* > alias: pci:v000014E4d000016AFsv*sd*bc*sc*i* > alias: pci:v000014E4d000016A2sv*sd*bc*sc*i* > alias: pci:v00001077d000016A1sv*sd*bc*sc*i* > alias: pci:v000014E4d000016A1sv*sd*bc*sc*i* > alias: pci:v000014E4d0000168Dsv*sd*bc*sc*i* > alias: pci:v000014E4d000016AEsv*sd*bc*sc*i* > alias: pci:v000014E4d0000168Esv*sd*bc*sc*i* > alias: pci:v000014E4d000016A9sv*sd*bc*sc*i* > alias: pci:v000014E4d000016A5sv*sd*bc*sc*i* > alias: pci:v000014E4d0000168Asv*sd*bc*sc*i* > alias: pci:v000014E4d0000166Fsv*sd*bc*sc*i* > alias: pci:v000014E4d00001663sv*sd*bc*sc*i* > alias: pci:v000014E4d00001662sv*sd*bc*sc*i* > alias: pci:v000014E4d00001650sv*sd*bc*sc*i* > alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* > alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* > depends: mdio,libcrc32c,ptp > intree: Y > vermagic: 3.10.0-693.2.1.el7.x86_64 SMP mod_unload modversions > signer: Red Hat Enterprise Linux kernel signing key > sig_key: 23:43:83:E8:47:F0:F1:6B:2F:41:5C:72:2D:D1:FF:69:86:3C:88:78 > sig_hashalgo: sha256 > parm: num_queues: Set number of queues (default is as a number of > CPUs) (int) > parm: disable_tpa: Disable the TPA (LRO) feature (int) > parm: int_mode: Force interrupt mode other than MSI-X (1 INT#x; 2 > MSI) (int) > parm: dropless_fc: Pause on exhausted host ring (int) > parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) > parm: debug: Default debug msglevel (int) > [root@host2 ~]# > > > > (In reply to Yuval Turgeman from comment #12) > > What do you get when you do `modinfo bnx2x` ? Also, did you flash the > > firmware after you installed the firmware rpm ? Looks like the driver is not missing, it's seems to be a configuration issue. I am not familiar with it, but as for the flashing, I did see in the rpm that HPE provided for the firmware (firmware-nic-qlogic-nx2-2.19.22-1.1.x86_64.rpm) a "setup" executable (the post install script runs it if you export FIRMWARE_FLASH_NOW=1, do rpm -qp --scripts on the rpm for more details), but again, I'm not familiar with this rpm so I dont know if it would work, perhaps HPE support can give more details.
Closing, it looks like a configuration issue and the module is present in RHVH