David,

Just to clarify something.

You're running Oracle Enterprise Linux 5 and the guest OS is Red Hat Enterprise 
Linux 5.5?

We're having trouble reproducing this so I want to make sure we're using the 
right setup.

Thanks,

- Greg

> -----Original Message-----
> From: Rose, Gregory V [mailto:gregory.v.r...@intel.com]
> Sent: Thursday, January 05, 2012 8:06 AM
> To: Kirsher, Jeffrey T; david.ye...@oracle.com
> Cc: e1000-devel; Allan, Bruce W; Brandeburg, Jesse; Steve Sarvate
> Subject: Re: [E1000-devel] Question about ixgbevf driver
> 
> > -----Original Message-----
> > From: Kirsher, Jeffrey T
> > Sent: Wednesday, January 04, 2012 7:58 PM
> > To: david.ye...@oracle.com; Rose, Gregory V
> > Cc: Brandeburg, Jesse; Allan, Bruce W; Steve Sarvate; e1000-devel
> > Subject: Re: Question about ixgbevf driver
> >
> > Adding e1000-devel mailing list as well as Greg Rose (ixgbevf
> > maintainer)...
> 
> I've never noticed this before but then I can't say as how I was looking
> for it either.  Let me check it out and I'll get back to you.
> 
> - Greg
> 
> >
> > On Wed, 2012-01-04 at 17:26 -0800, David Yeung wrote:
> > > Hi  Bruce/Jeffrey/Jesse/,
> > >
> > > How do you do?
> > > We are using the  ixgbevf  driver ( version: 2.4.0-NAPI ) to test the
> > > VLAN interfaces of Twinville NICs inside the OEL 5 virtual machine, it
> > > looks like the bi-directional network traffic ran properly on the VLAN
> > > interfaces of Twinville NICs  inside the OEL 5 virtual machine for
> > > hours, but the ifconfig command reports strange amount ( it is 0 all
> > > the time )  of  RX packets and RX bytes of VLAN interfaces of
> Twinville:
> > >
> > > [root@Twinville_VM_156 ~]# ifconfig
> > > .........................................
> > > eth6.10   Link encap:Ethernet  HWaddr F2:54:11:05:72:7C
> > >            inet addr:192.6.10.156  Bcast:192.6.10.255
> > Mask:255.255.255.0
> > >            UP BROADCAST RUNNING MULTICAST  MTU:9210  Metric:1
> > >            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >            TX packets:111332155 errors:0 dropped:0 overruns:0
> carrier:0
> > >            collisions:0 txqueuelen:0
> > >            RX bytes:0 (0.0 b)  TX bytes:2565278846027 (2.3 TiB)
> > >
> > > eth6.11   Link encap:Ethernet  HWaddr F2:54:11:05:72:7C
> > >            inet addr:192.6.11.156  Bcast:192.6.11.255
> > Mask:255.255.255.0
> > >            UP BROADCAST RUNNING MULTICAST  MTU:9210  Metric:1
> > >            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >            TX packets:111289098 errors:0 dropped:0 overruns:0
> carrier:0
> > >            collisions:0 txqueuelen:0
> > >            RX bytes:0 (0.0 b)  TX bytes:2562582125939 (2.3 TiB)
> > >
> > > eth6.12   Link encap:Ethernet  HWaddr F2:54:11:05:72:7C
> > >            inet addr:192.6.12.156  Bcast:192.6.12.255
> > Mask:255.255.255.0
> > >            UP BROADCAST RUNNING MULTICAST  MTU:9210  Metric:1
> > >            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >            TX packets:111287930 errors:0 dropped:0 overruns:0
> carrier:0
> > >            collisions:0 txqueuelen:0
> > >            RX bytes:0 (0.0 b)  TX bytes:2564949229588 (2.3 TiB)
> > >
> > > eth6.13   Link encap:Ethernet  HWaddr F2:54:11:05:72:7C
> > >            inet addr:192.6.93.156  Bcast:192.6.93.255
> > Mask:255.255.255.0
> > >            UP BROADCAST RUNNING MULTICAST  MTU:9210  Metric:1
> > >            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >            TX packets:111070858 errors:0 dropped:0 overruns:0
> carrier:0
> > >            collisions:0 txqueuelen:0
> > >            RX bytes:0 (0.0 b)  TX bytes:2566358628283 (2.3 TiB)
> > >
> > > eth6.14   Link encap:Ethernet  HWaddr F2:54:11:05:72:7C
> > >            inet addr:192.6.14.156  Bcast:192.6.14.255
> > Mask:255.255.255.0
> > >            UP BROADCAST RUNNING MULTICAST  MTU:9210  Metric:1
> > >            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >            TX packets:111362848 errors:0 dropped:0 overruns:0
> carrier:0
> > >            collisions:0 txqueuelen:0
> > >            RX bytes:0 (0.0 b)  TX bytes:2566349976603 (2.3 TiB)
> > > .........................................
> > >
> > > [root@Twinville_VM_156 ~]# ethtool -i eth6
> > > driver: ixgbevf
> > > version: 2.4.0-NAPI
> > > firmware-version: N/A
> > > bus-info: 0000:00:09.0
> > > [root@Powerville_VM_156 ~]#
> > >
> > > [root@Twinville_VM_156 ~]# cat   /etc/*release
> > > Enterprise Linux Enterprise Linux Server release 5.5 (Carthage) Red
> > > Hat Enterprise Linux Server release 5.5 (Tikanga)
> > > [root@Twinville_VM_156 ~]#
> > >
> > > Do you have any idea about this problem? Any workaround/fix for this
> > > problem?
> > >
> > >
> > > Thanks,
> > >
> > > David
> > >
> >
> 
> --------------------------------------------------------------------------
> ----
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> E1000-devel mailing list
> E1000-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
> To learn more about Intel® Ethernet, visit
> http://communities.intel.com/community/wired

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to