Hide Forgot
Description of problem: The information of eth0 can't be showed under RHEL5.7 64bit Xen and RHEL5.4 64bit Xen Version-Release number of selected component (if applicable): RHEL5.4 Xen and RHEL5.7Xen How reproducible: Steps to Reproduce: 1.Load the BIOS optimized default. 2.Install RHEL5.7 Xen 64bit via USB DVDROM. 3.Install ixgbe-3.5.14 for NIC under OS,and then restart network. 4.Statically set IP address and then restart network, but eth0 can not be activated-->FAIL 5.Type "#ethtool -i eth0" in Terminal, it is showed "Operation not supported"-->FAIL Actual results: Expected results: Additional info: 1.RHEL6.1 64bit -->eth0ð1 can be activated-->PASS 2.RHEL5.4 64bit XEN -->eth0 can not be activated -->FAIL 3.RHEL5.4 64bit XEN -->eth1 can be activated -->PASS 4.RHEL5.7 64bit XEN -->eth1 can be activated -->PASS 3.Change another MLB, the issue can be reproduced-->FAIL
Can you be more specific on fail case 1) exact commands you use 2) exact reported error 3) ip a output before and after fail
1. We use "ethtool -i eth0" to check eth0 information, like support WOL or autoneg., and in RHEL5.4 Non-Xen, when we run"ethtool -i eth0", to check NIC0 information, the eth0 information can be shown including driver, autoneg., WOL..etc, unfortunately, when we type the xen key and enter rhel5.4 Xen, without re-deploy the hardware configuration, and at the same server, when we check the eth0 information, it show "Operation not supported". 2. We check another intel NIC with chipset intel 82576, the issue mentioned also can be reproduced. The reported error is that: Type "#ethtool -i eth0" in Terminal, it is showed "Operation not supported" In fact, when we check RHEL5.4 non-xen and RHEL5.7 non-xen, the error didn't happen. 3. We first set IP, since eth1 cann't be reproduced, only eth0 occurred, we check eth0 and eth1 with the same procedure. Eth1 can be OK. 4. The issue also impact bonding validation,when we do the same procedure in rhel5.4 and rhel5.4 xen, cover Broadcom and intel NIC chipset, also cover different servers, the bonding always fail in xen mode, I doubt it is rhel5.4 and rhel5.7 xen issue, and also, the no-xen, all the bonding configuration rhel5.4 and rhel5.7 are workable. 5. We used PCI-e 10G fiber NIC, Intel X520-DA2 DUAL Port,the issue also can be reproduced.
We will also try OS embeded driver to test that issue, any further information, I will update it.
Please, can you provide your exact configuration. On xen with bridged network, eth0 is virtual device created by xen, physical device is peth0. Check if you are not mixing these two devices (as eth1 is ok).
Hello Chris, (I hope I managed to identify your first name correctly from your email address,) In reply to comment #0: > 3.Install ixgbe-3.5.14 for NIC under OS,and then restart network. Please open a Customer Portal case and work with GSS to determine if this is supported at all. RHEL-5 ships the ixgbe driver. As far as I can see, starting with kernel build 2.6.18-290.el5 the driver version is 3.4.8-k8. Kernel RPMs even newer than 2.6.18-290.el5 should be available to you through the usual channels. I think if you need a more recent ixgbe driver, you should file an RFE, after working with GSS and making sure your ethernet/bridge configuration is otherwise correct under Xen. Additionally, both netloop and netback support "ethtool -i" starting with build 2.6.18-243.el5 (bug 643872); ie. it was added from RHEL-5.6 to RHEL-5.7. Therefore, if your Xen networking is set up correctly under RHEL-5.7, then: - for all physical ethX interfaces "ethtool -i" should return the corresponding info, for example: driver: tg3 version: 3.116 firmware-version: 5761-v3.72 bus-info: 0000:03:00.0 - for the virtual (renamed) ethX interface participating in Xen networking "ethtool -i" should return: driver: netloop version: firmware-version: bus-info: vif-0-1 (Bus-info may be different.) If you see something else under RHEL-5.7 Xen, then your networking configuration is incorrect. Please work with GSS to examine that. Thank you.
1. The bridge or virt-bridge didn't exist. 2. When check eth0 information run"ethtool -i peth0", the eth0 information is OK. 3. Since eth0 information can be performed "ethtool -i peth0", suggest to close the issue, many thanks