1. Proposed title of this feature request Add qlogic 8.0.0 driver in RHEV-H builds 3. What is the nature and description of the request? To add in the 8.0.0 firmware from http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=Y4XN5&fileId=3457978414&osCode=RH60&productCode=poweredge-m620&languageCode=EN&categoryId=NI which resolves firmware hangs. 4. Why does the customer need this? (List the business requirements here) To resolve firmware hangs 5. How would the customer like to achieve this? (List the functional requirements here) Build the module into the latest RHEVH-6 and RHEVH-7 builds 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Use the new build as normal and watch for hangs 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? As soon as possible in an upcoming RHEV-H build release 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages or components. qlogic 8.0.0 firmware, upgraded from the current qlcnic Driver v5.3.59, firmware v4.18.4 11. Would the customer be able to assist in testing this functionality if implemented? Yes
The process to follow here is got get the required firmware shipped in RHEL. Once it lands there, RHEV-H is usually picking up with one of the following builds. Does RHEL already incldue the required firmware?
Thanks Fabian, let me confirm this and I'll close this and re-open the bug for RHEL if necessary.
Fabian, looking into this it seems that https://bugzilla.redhat.com/show_bug.cgi?id=1110658 has this added into RHEL 6.6 and is proposed for 6.7 in https://bugzilla.redhat.com/show_bug.cgi?id=1148019 so in that case we should be able to get this into a RHEV-H build, as the current version seems to be 5.3.59. Regards, Robert McSwain
Test version: rhev-hypervisor6-6.7-20150609.0 kernel-2.6.32-565.el6.x86_64 As #c3 said, qlogic driver has been added into RHEL6.6 and is proposed for 6.7. so this bug is RHEV-H only issue. so I will verify this bug after RHEV-H include the fixed kernel version. Thanks!
Testing is done by ensuring that the requested driver package (give in the description) is available in the build.
According to bug 1148019 comment 11 this bug is fixed in kernel-2.6.32-573.el6 . We must ensure that we include this or a higher kernel. However, the version "8.0.0" as given in the description is not named. Robert, can you check if the driver in bug 1148019 suites the customer? If not, then the request for the specific driver in the description needs to be filed against RHEL.
I will verify this bug after #c8 getting confirmed.
GA is getting closer, we can not wait more for reporter response, we will verify this bug according to comment 11 and comment 14. If here need future support on this bug, please reopen this one OR new one for further tracing. Acked by fabian and ycui on weekly meeting, then change it to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1713.html
We are still getting firmware hangs. This server has QME8262-k card. I do not see evidence of newer qlcnic module loaded in 20150828.0.el6ev hypervisor. [root@tulhv1p06 Linux_Binary]# cat /etc/redhat-release Red Hat Enterprise Virtualization Hypervisor release 6.7 (20150828.0.el6ev These are the qlogic packages shown installed: [root@tulhv1p06 Linux_Binary]# rpm -qa | grep ql2 ql2200-firmware-2.02.08-3.1.el6.noarch ql2500-firmware-7.03.00-1.el6.noarch ql2100-firmware-1.19.38-3.1.el6.noarch ql23xx-firmware-3.03.27-3.1.el6.noarch ql2400-firmware-7.03.00-1.el6.noarch [root@tulhv1p06 ~]# ethtool -i p1p1 driver: qlcnic version: 5.3.62.1 firmware-version: 4.18.4 bus-info: 0000:04:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no [root@tulhv1p06 ~]# ethtool -i p1p2 driver: qlcnic version: 5.3.62.1 firmware-version: 4.18.4 bus-info: 0000:04:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no [root@tulhv1p06 dell]# modinfo qlcnic filename: /lib/modules/2.6.32-573.3.1.el6.x86_64/kernel/drivers/net/qlcnic/qlcnic.ko firmware: phanfw.bin version: 5.3.62.1 license: GPL description: QLogic 1/10 GbE Converged/Intelligent Ethernet Driver srcversion: 4EC524B914D4C6A28325A00 alias: pci:v00001077d00008440sv*sd*bc02sc00i00* alias: pci:v00001077d00008040sv*sd*bc02sc00i00* alias: pci:v00001077d00008430sv*sd*bc02sc00i00* alias: pci:v00001077d00008830sv*sd*bc02sc00i00* alias: pci:v00001077d00008030sv*sd*bc02sc00i00* alias: pci:v00001077d00008020sv*sd*bc02sc00i00* depends: vermagic: 2.6.32-573.3.1.el6.x86_64 SMP mod_unload modversions parm: qlcnic_mac_learn:Mac Filter (0=disabled, 1=enabled) (int) parm: use_msi:MSI interrupt (0=disabled, 1=enabled) (int) parm: use_msi_x:MSI-X interrupt (0=disabled, 1=enabled) (int) parm: auto_fw_reset:Auto firmware reset (0=disabled, 1=enabled) (int) parm: load_fw_file:Load firmware from (0=flash, 1=file, 2=POST in fast mode, 3= POST in medium mode, 4=POST in slow mode) (int) Files within the Dell tarball at [http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=Y4XN5&fileId=3457978414&osCode=RH60&productCode=poweredge-m620&languageCode=EN&categoryId=NI] do not seem to be present. Thanks Doug
Created attachment 1072362 [details] files missing
My mistake. It looks like this Host is using qlcnic version 5.3.62.1, which is the same version provided by Dell in their RPM "kmod-qlgc-qlcnic-5.3.62-1.x86_64.rpm." I will speak with Dell to determine why we are still experiencing firmware hangs.
Douglas, we also had to look very careful to verify that we are shipping the right version, the versioning between the different files is making it a bit hard.
Fabian, Are there any updates regarding this bug and Doug's last update? Regards, Robert McSwain
No, there were no further updates. Is there still something missing?
My apologies, I missed an update in there and we can close this out.