From owner-freebsd-net@freebsd.org  Wed Sep  9 16:39:15 2015
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23AFFA00C76
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Wed,  9 Sep 2015 16:39:15 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0FF551DCD
 for <freebsd-net@FreeBSD.org>; Wed,  9 Sep 2015 16:39:15 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t89GdEri001706
 for <freebsd-net@FreeBSD.org>; Wed, 9 Sep 2015 16:39:14 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 202875] ixv driver in 11.0-CURRENT doesn't pass traffic using
 KVM hypervisor
Date: Wed, 09 Sep 2015 16:39:15 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: IntelNetworking
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: jeffrey.e.pieper@intel.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-202875-2472-qbYLIsKOQQ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-202875-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-202875-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2015 16:39:15 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202875

--- Comment #8 from Jeff Pieper <jeffrey.e.pieper@intel.com> ---
(In reply to Patrick Kelsey from comment #6)

After performing some additional testing, this is what I have discovered:

- Reverting r285590 and r285592 do not fix the issue.
- I can reproduce the issue using our OOT driver on CURRENT.
- in ALL failing scenarios, I see the following in dmesg on the host after
init:

ixgbe 0000:08:00.0 eth0: VF max_frame 1522 out of range

So I think it's safe to say that it isn't the driver causing this, but
something else that is causing oversized frames.

In summary:

- 10.2 works using in-kernel and OOT drivers.
- CURRENT fails using in-kernel and OOT drivers.

-- 
You are receiving this mail because:
You are the assignee for the bug.