qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KV


From: Shannon Nelson
Subject: Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
Date: Wed, 18 Mar 2015 15:06:34 -0700

On Wed, Mar 18, 2015 at 3:01 PM, Shannon Nelson
<address@hidden> wrote:
>
>
> On Wed, Mar 18, 2015 at 8:40 AM, jacob jacob <address@hidden> wrote:
> >
> > On Wed, Mar 18, 2015 at 11:24 AM, Bandan Das <address@hidden> wrote:
> > >
> > > Actually, Stefan suggests that support for this card is still sketchy
> > > and your best bet is to try out net-next
> > > http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git
> > >
> > > Also, could you please post more information about your hardware setup
> > > (chipset/processor/firmware version on the card etc) ?
> >
> > Host CPU : Model name:            Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
> >
> > Manufacturer Part Number:  XL710QDA1BLK
> > Ethernet controller: Intel Corporation Ethernet Controller XL710 for
> > 40GbE QSFP+ (rev 01)
> >  #ethtool -i enp9s0
> > driver: i40e
> > version: 1.2.6-k
> > firmware-version: f4.22 a1.1 n04.24 e800013fd
> > bus-info: 0000:09:00.0
> > supports-statistics: yes
> > supports-test: yes
> > supports-eeprom-access: yes
> > supports-register-dump: yes
> > supports-priv-flags: no
> >

Jacob,

It looks like you're using a NIC with the e800013fd firmware from last
summer, and from a separate message that you saw these issues with
both the 1.2.2-k and the 1.2.37 version drivers.  I suggest the next
step would be to update the NIC firmware as there are some performance
and stability updates available that deal with similar issues.  Please
see the Intel Networking support webpage at
https://downloadcenter.intel.com/download/24769 and look for the
NVMUpdatePackage.zip.  This should take care of several of the things
Stefan might describe as "sketchy" :-).

sln
(Sent again, hopefully without gmail adding html and thereby getting
it blocked from the kernel mailing lists...)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]