From: Shannon Nelson <shannon.nelson@intel.com>
To: jacob jacob <opstkusr@gmail.com>
Cc: kvm-devel <kvm@vger.kernel.org>,
netdev@vger.kernel.org,
Alex Williamson <alex.williamson@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Bandan Das <bsd@redhat.com>, Stefan Assmann <sassmann@redhat.com>
Subject: Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
Date: Thu, 19 Mar 2015 14:42:17 -0700 [thread overview]
Message-ID: <CAP-MU4MTf+kRvvBZYDdsJbDjA1ATe-4zuBCKoCyKpboB9+cD6g@mail.gmail.com> (raw)
In-Reply-To: <CA+AkT2gHKtz2bKSf2FB+3+XkDidBnUDQSZy_KPb1y-MG+QnSiw@mail.gmail.com>
On Thu, Mar 19, 2015 at 2:04 PM, jacob jacob <opstkusr@gmail.com> wrote:
> I have updated to latest firmware and still no luck.
[...]
> [ 61.554132] i40e 0000:00:06.0 eth2: the driver failed to link
> because an unqualified module was detected. <<<<<<<<<<<<<<<<<<<<
> [ 61.555331] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
>
So I assume you're getting traffic on the other port and it doesn't
complain about "unqualified module"? Does the problem move if you
swap the cables? The usual problem here is a QSFP connector that
isn't compatible with the NIC. I don't have a pointer handy to the
official list, but you should be able to get that from your NIC
supplier.
sln
next prev parent reply other threads:[~2015-03-19 21:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 16:17 [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM) jacob jacob
2015-03-12 16:26 ` Alex Williamson
2015-03-12 16:36 ` jacob jacob
2015-03-12 19:07 ` Bandan Das
2015-03-12 23:11 ` jacob jacob
2015-03-13 0:02 ` Bandan Das
2015-03-13 14:08 ` jacob jacob
2015-03-16 16:31 ` jacob jacob
2015-03-16 18:12 ` Bandan Das
2015-03-16 18:24 ` jacob jacob
2015-03-16 19:49 ` Bandan Das
2015-03-16 19:58 ` jacob jacob
2015-03-18 15:24 ` Bandan Das
2015-03-18 15:40 ` jacob jacob
2015-03-18 22:01 ` Shannon Nelson
2015-03-18 22:06 ` Shannon Nelson
2015-03-19 8:15 ` Stefan Assmann
2015-03-19 14:00 ` jacob jacob
2015-03-19 14:04 ` jacob jacob
2015-03-19 14:18 ` Stefan Assmann
2015-03-20 20:55 ` jacob jacob
2015-03-23 7:19 ` Stefan Assmann
2015-03-24 14:13 ` jacob jacob
2015-03-24 14:53 ` Shannon Nelson
2015-03-24 15:04 ` jacob jacob
2015-03-26 1:00 ` Shannon Nelson
2015-03-19 16:26 ` Shannon Nelson
2015-03-19 21:04 ` jacob jacob
2015-03-19 21:42 ` Shannon Nelson [this message]
2015-03-19 21:53 ` jacob jacob
2015-03-19 23:37 ` jacob jacob
-- strict thread matches above, loose matches on Subject: below --
2015-03-12 16:11 jacob jacob
2015-03-12 16:13 ` jacob jacob
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP-MU4MTf+kRvvBZYDdsJbDjA1ATe-4zuBCKoCyKpboB9+cD6g@mail.gmail.com \
--to=shannon.nelson@intel.com \
--cc=alex.williamson@redhat.com \
--cc=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opstkusr@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sassmann@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).