Description of problem: I installed oVirt Node using the ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso on a Dell PowerEdge R410 with an Intel I340-T4 4-port gigabit Ethernet card. The on-board, Broadcom NIC's were recognized by the OS, but the Intel interfaces were not. Version-Release number of selected component (if applicable): ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso How reproducible: Hardware-specific Steps to Reproduce: 1. Boot to ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso 2. Install ovirt-node 3. Reboot 4. eth0 and eth1 show up correctly, p1p1/2/3/4 do not. 5. Observe the igb driver attempting to load four times, once for each GbE interface: dmesg | grep igb [ 2145.332816] igb: Unknown symbol i2c_new_device (err 0) [ 2145.332859] igb: Unknown symbol i2c_bit_add_bus (err 0) [ 2145.332936] igb: Unknown symbol i2c_del_adapter (err 0) [ 2145.333052] igb: Unknown symbol i2c_smbus_write_byte_data (err 0) [ 2145.333075] igb: Unknown symbol i2c_smbus_read_byte_data (err 0) [ 2145.333176] igb: Unknown symbol i2c_new_device (err 0) [ 2145.333210] igb: Unknown symbol i2c_bit_add_bus (err 0) [ 2145.333266] igb: Unknown symbol i2c_del_adapter (err 0) [ 2145.333381] igb: Unknown symbol i2c_smbus_write_byte_data (err 0) [ 2145.333398] igb: Unknown symbol i2c_smbus_read_byte_data (err 0) [ 2145.333554] igb: Unknown symbol i2c_new_device (err 0) [ 2145.333593] igb: Unknown symbol i2c_bit_add_bus (err 0) [ 2145.333662] igb: Unknown symbol i2c_del_adapter (err 0) [ 2145.333773] igb: Unknown symbol i2c_smbus_write_byte_data (err 0) [ 2145.333826] igb: Unknown symbol i2c_smbus_read_byte_data (err 0) [ 2145.333919] igb: Unknown symbol i2c_new_device (err 0) [ 2145.333953] igb: Unknown symbol i2c_bit_add_bus (err 0) [ 2145.334008] igb: Unknown symbol i2c_del_adapter (err 0) [ 2145.334117] igb: Unknown symbol i2c_smbus_write_byte_data (err 0) [ 2145.334138] igb: Unknown symbol i2c_smbus_read_byte_data (err 0) Actual results: yum update ... --> Processing Dependency: python-inotify for package: vdsm-4.12.1-2.el6.x86_64 --> Running transaction check ---> Package perl-hivex.x86_64 0:1.3.3-4.2.el6 will be installed ---> Package vdsm.x86_64 0:4.12.1-2.el6 will be an update --> Processing Dependency: python-inotify for package: vdsm-4.12.1-2.el6.x86_64 --> Finished Dependency Resolution Error: Package: vdsm-4.12.1-2.el6.x86_64 (ovirt-stable) Requires: python-inotify You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Expected results: NIC's expected to be identified, drivers to load, etc. Additional info: [root@kvmc1n2 ~]# modinfo igb filename: /lib/modules/3.10.10-200.fc19.x86_64/kernel/drivers/net/ethernet/intel/igb/igb.ko version: 5.0.3-k license: GPL description: Intel(R) Gigabit Ethernet Network Driver author: Intel Corporation, <e1000-devel.net> srcversion: 8251E5B658798814C71FD34 alias: pci:v00008086d000010D6sv*sd*bc*sc*i* alias: pci:v00008086d000010A9sv*sd*bc*sc*i* alias: pci:v00008086d000010A7sv*sd*bc*sc*i* alias: pci:v00008086d000010E8sv*sd*bc*sc*i* alias: pci:v00008086d00001526sv*sd*bc*sc*i* alias: pci:v00008086d0000150Dsv*sd*bc*sc*i* alias: pci:v00008086d000010E7sv*sd*bc*sc*i* alias: pci:v00008086d000010E6sv*sd*bc*sc*i* alias: pci:v00008086d00001518sv*sd*bc*sc*i* alias: pci:v00008086d0000150Asv*sd*bc*sc*i* alias: pci:v00008086d000010C9sv*sd*bc*sc*i* alias: pci:v00008086d00000440sv*sd*bc*sc*i* alias: pci:v00008086d0000043Csv*sd*bc*sc*i* alias: pci:v00008086d0000043Asv*sd*bc*sc*i* alias: pci:v00008086d00000438sv*sd*bc*sc*i* alias: pci:v00008086d00001516sv*sd*bc*sc*i* alias: pci:v00008086d00001511sv*sd*bc*sc*i* alias: pci:v00008086d00001510sv*sd*bc*sc*i* alias: pci:v00008086d00001527sv*sd*bc*sc*i* alias: pci:v00008086d0000150Fsv*sd*bc*sc*i* alias: pci:v00008086d0000150Esv*sd*bc*sc*i* alias: pci:v00008086d00001524sv*sd*bc*sc*i* alias: pci:v00008086d00001523sv*sd*bc*sc*i* alias: pci:v00008086d00001522sv*sd*bc*sc*i* alias: pci:v00008086d00001521sv*sd*bc*sc*i* alias: pci:v00008086d00001538sv*sd*bc*sc*i* alias: pci:v00008086d00001537sv*sd*bc*sc*i* alias: pci:v00008086d00001536sv*sd*bc*sc*i* alias: pci:v00008086d00001533sv*sd*bc*sc*i* alias: pci:v00008086d00001539sv*sd*bc*sc*i* alias: pci:v00008086d00001F45sv*sd*bc*sc*i* alias: pci:v00008086d00001F41sv*sd*bc*sc*i* alias: pci:v00008086d00001F40sv*sd*bc*sc*i* depends: i2c-core,ptp,dca,i2c-algo-bit intree: Y vermagic: 3.10.10-200.fc19.x86_64 SMP mod_unload signer: Fedora kernel signing key sig_key: 6A:93:3B:96:F3:46:C5:24:79:A9:13:1F:6A:E6:DD:D3:9F:99:39:20 sig_hashalgo: sha256 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int)
The i2c modules seem to be missing.
Could you please try if this test build recognizes the igb card? http://jenkins.ovirt.org/job/node-devel/1013/distro=fedora19/artifact/ovirt-node-iso-3.1.0-0.999.999.20131017125613git86aff29.1013.fc19.iso
I've rebuilt that system. I can give it a shot - is it something that can be exercised from the ISO-boot environment? Or will it require a full OS install to test?
(In reply to important from comment #3) > I've rebuilt that system. I can give it a shot - is it something that can > be exercised from the ISO-boot environment? Or will it require a full OS > install to test? Hey, it should be enough to boot that image as an ISO or trough PXE and then in the installer: 1. Drop to shell by pressing f2 2. On the console run modprobe igb 3. Look at the end of dmesg for errors.
I was able to boot the system to this new ISO run the recovery-node boot option modprobe igb dmesg | grep igb There were no errors - it looks like all four NIC's were detected and loaded correctly. There were no "unknown symbol" errors.
Thanks, that sounds good.
oVirt gerrit 20267 is merged, can you set target release, fixed in version and move this to modified/on qa/closed accordingly?
This fix is landing in the next ovirt-node respin for 3.3
Target Release: --- → 3.3 Fixed In Version: ovirt-node-3.0.2 closing.