From owner-freebsd-xen@freebsd.org  Tue Jun  7 13:15:00 2016
Return-Path: <owner-freebsd-xen@freebsd.org>
Delivered-To: freebsd-xen@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 A3CD3B6DE70
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Tue,  7 Jun 2016 13:15:00 +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 944281A3D
 for <freebsd-xen@FreeBSD.org>; Tue,  7 Jun 2016 13:15:00 +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 u57DF0ZI026814
 for <freebsd-xen@FreeBSD.org>; Tue, 7 Jun 2016 13:15:00 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-xen@FreeBSD.org
Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic
 for other Xen PV guests on same Dom0 Host.
Date: Tue, 07 Jun 2016 13:15:00 +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: 9.2-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kpielorz@tdx.co.uk
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-188261-23905-IS7QGH5hy2@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-188261-23905@https.bugs.freebsd.org/bugzilla/>
References: <bug-188261-23905@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2016 13:15:00 -0000

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

--- Comment #17 from kpielorz@tdx.co.uk ---
(In reply to Roger Pau Monn=C3=83=C2=A9 from comment #16)

Hi,

I've tested these patches now. I installed a HEAD snapshot, and updated it =
to
r301543M.

The VM can route traffic with '-rxcsum -txcsum -tso -lro' applied to xn0 / =
xn1.

I applied the patches - rebuilt / installed the kernel / rebooted and sadly=
 it
still cannot forward traffic - unless I again set the above ifconfig option=
s on
both interfaces.

The patches only affect the kernel right - I don't need to buildworld again?

Cheers,

-Karl

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