Bug 679265

Summary: vf can't be determined ip automatically
Product: Red Hat Enterprise Linux 6 Reporter: Chao Yang <chayang>
Component: initscriptsAssignee: initscripts Maintenance Team <initscripts-maint-list>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: low Docs Contact:
Priority: low    
Version: 6.1CC: agospoda, arozansk, harald, juzhang, michen, mkenneth, notting, tburke, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-15 15:01:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 682269    
Attachments:
Description Flags
device message on Nehalem-ex
none
list of ifconfig and /etc/sysconfig/network-scripts/ none

Description Chao Yang 2011-02-22 04:48:18 UTC 
Description of problem:
vfs can't be determined ip when generated by 82576 nic card. If configure vfs manually under /etc/sysconfig/network-scripts/ and then restart network, vfs can get ip. This issue with 82576 happens on Nehalem-ex but not happen on Nehalem-ep. 

Version-Release number of selected component (if applicable):
both Nehalem-ex and Nehalem-ep have same kernel version.

# uname -r
2.6.32-115.el6.x86_64


How reproducible:


Steps to Reproduce:
1. modprobe -r igb;modprobe igb max_vfs=7
2. ifconfig -a to check vfs
  
Actual results:
After step 2:
1. on Nehalem-ex, vfs fail to determine ip.
2. on Nehalem-ep, vfs can be determined ip automatically.
Expected results:
vfs on Nehalem-ex can behave the same as on Nehalem-ep.

Additional info:
Comment 1 Chao Yang 2011-02-22 04:51:57 UTC 
Created attachment 480049 [details]
device message on Nehalem-ex
Comment 4 Stefan Assmann 2011-02-25 13:57:07 UTC 
chayang,

which system did you use that shows the error? Also are you sure the systems igb NIC has a cable connected and detects link?
Comment 7 Chao Yang 2011-02-28 04:42:14 UTC 
Created attachment 481302 [details]
list of ifconfig and /etc/sysconfig/network-scripts/
Comment 8 Stefan Assmann 2011-02-28 08:03:40 UTC 
What's the hostname of the system? Also if you want to test without biosdevname just install RHEL6.0 and see how that behaves.
Comment 10 Chao Yang 2011-03-01 11:24:40 UTC 
(In reply to comment #8)
> What's the hostname of the system? Also if you want to test without biosdevname
> just install RHEL6.0 and see how that behaves.

Stefan,
 I tried with RHEL6.0, all of vfs have determined ip and pf can determine ip, too.
Comment 11 Stefan Assmann 2011-03-01 14:54:53 UTC 
I've installed the latest RHEL6 kernel on the box, but it didn't come up after the reboot. Could you please check what's the problem. Maybe the default route is messed up...
If VFs and PF are able to acquire an IP please let us know.

Also please confirm that you did not specify biosdevname=1 on the kernel command line when you installed the RHEL6.1 nightly.

We need to figure out why biosdevname got enabled in your first install attempt. Feel free to re-install the latest nightly.
Comment 12 Chao Yang 2011-03-02 09:17:14 UTC 
(In reply to comment #11)
> I've installed the latest RHEL6 kernel on the box, but it didn't come up after
> the reboot. Could you please check what's the problem. Maybe the default route
> is messed up...
> If VFs and PF are able to acquire an IP please let us know.
> 
> Also please confirm that you did not specify biosdevname=1 on the kernel
> command line when you installed the RHEL6.1 nightly.
> 
> We need to figure out why biosdevname got enabled in your first install
> attempt. Feel free to re-install the latest nightly.

I found that you forgot to install kernel-firmware-2.6.32-118.el6.noarch.rpm, I installed it and reboot, PF and VFs can acquire an IP. 

I am sure I did not specify biosdevname=1 on the kernel command line, before I installed the RHEL6.1 nightly, I even don't know what is biosdevname.
Comment 13 Stefan Assmann 2011-03-02 14:55:24 UTC 
Ok so this is a Dell machine which has biosdevname enabled by default. This can be checked by
cat /sys/class/dmi/id/sys_vendor
Dell Inc.

Chayang can you please re-install the latest RHEL6 nightly?
Comment 14 Stefan Assmann 2011-03-03 14:02:09 UTC 
This problem is not kernel related and probably an issue with the network scripts, re-assigning to initscripts, not sure if that's the right component. Feel free to redirect.
Comment 15 Bill Nottingham 2011-03-03 16:17:14 UTC 
What errors do you get when you can't get an IP address?
Comment 16 Chao Yang 2011-03-08 12:03:58 UTC 
(In reply to comment #15)
> What errors do you get when you can't get an IP address?

Problem is the VFs cannot acquire IP automatically once they are generated by PF, I need to configure VF to make them get IP, they should acquire ip automatically without any configuration. I think dmesg have recorded something when I generate VFs. If you need more info, let me know. Thanks.
Comment 17 Bill Nottingham 2011-03-08 16:17:51 UTC 
The network init script does not set up devices without configuration (it never has), and we don't automatically write configuration for new devices (in RHEL 6).

So, what exactly are you expecting to work that does not work here?
Comment 18 Chao Yang 2011-03-09 02:15:11 UTC 
(In reply to comment #17)
> The network init script does not set up devices without configuration (it never
> has), and we don't automatically write configuration for new devices (in RHEL
> 6).
> 
> So, what exactly are you expecting to work that does not work here?
I am expecting VFs to be setup once they are generated. Cause on Nehalem-ep, VFs can be determined ip automatically, so I am expecting on Nehalem-ex VFs can behave the same as on Nehalem-ep.
Comment 19 Bill Nottingham 2011-03-09 16:05:44 UTC 
What happens on EP? Are configuration files written?
Comment 20 Chao Yang 2011-03-10 01:48:19 UTC 
(In reply to comment #19)
> What happens on EP? Are configuration files written?

On Nehalem-ep, no need to write any configuration files for VFs, once VFs are generated, they can acquire their IP without configuration files.
Comment 21 Bill Nottingham 2011-03-10 17:37:27 UTC 
... via what mechanism? How are you bringing them up?
Comment 22 Chao Yang 2011-03-11 10:10:40 UTC 
(In reply to comment #21)
> ... via what mechanism? How are you bringing them up?

I have no idea, but once VFs are generated, they can bring up themselves automatically.
Comment 23 Bill Nottingham 2011-03-11 15:33:22 UTC 
Automatically... as soon as they're generated? On reboot? <some other way>?

Are you bringing them up with '/etc/init.d/network start'? Are you using NetworkManager?
Comment 24 Andy Gospodarek 2011-03-11 16:08:28 UTC 
I suspect with NetworkManager.  I sometimes VFs get IP addresses automatically and it appears to happen on systems with NetworkManager installed and enabled by default.

Only some configurations/installs have NetworkManager enabled by default, right?
Comment 25 Bill Nottingham 2011-03-11 16:21:53 UTC 
Correct, NM will bring up any device with a link; it's installed with desktop installs (or if you explicitly do 'yum install NetworkManager', of course.
Comment 26 Chao Yang 2011-03-14 03:06:22 UTC 
(In reply to comment #25)
> Correct, NM will bring up any device with a link; it's installed with desktop
> installs (or if you explicitly do 'yum install NetworkManager', of course.

Base on your comments, I will have a try. Thanks for your clue.
Comment 27 Chao Yang 2011-03-15 02:44:44 UTC 
(In reply to comment #25)
> Correct, NM will bring up any device with a link; it's installed with desktop
> installs (or if you explicitly do 'yum install NetworkManager', of course.

Hi Bill,
Yes, you are right, with NM enabled VFs can get ip as soon as they are generated. Thank you.
Comment 28 Bill Nottingham 2011-03-15 15:01:11 UTC 
OK, so closing - things appear to be working as expected.