From owner-freebsd-xen@freebsd.org Thu May 12 09:35:37 2016 Return-Path: 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 75EE3B37D04 for ; Thu, 12 May 2016 09:35:37 +0000 (UTC) (envelope-from prvs=93319c3d4=roger.pau@citrix.com) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 144691358 for ; Thu, 12 May 2016 09:35:36 +0000 (UTC) (envelope-from prvs=93319c3d4=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,609,1454976000"; d="scan'208";a="353413084" Date: Thu, 12 May 2016 11:35:25 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Miguel C CC: Wei Liu , "freebsd-xen@freebsd.org" , Stephen Jones Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 Message-ID: <20160512093525.i6c64lqckyk3qgiq@mac> References: <20160503093211.hkmbbqr6t2fbxqqa@mac> <20160510144833.GJ12241@citrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-DLP: MIA1 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2016 09:35:37 -0000 Hello, On Tue, May 10, 2016 at 05:00:02PM +0100, Miguel C wrote: > See this PR from 2014 --> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 > > (there another earlier about the same error message on 9.X and that was > fixed on 10-CURRENT at the time, but was "broke" later) > > The issue happen with any NetBSD version from 5.x to 7.x with any xen > version but it only stared in FreeBSD 10-Current, so I was always inclined > to this being a regression in 10 not a NetBSD backend issue. Also I did > post in netbsd mailling list and the reply was something in the lines of > "was working fine, nothing changed at our side, so its probably FreeBSD > problem" > > Also as I posted in that PR I experienced a similar issue with Windows > GPLPV drivers and the dev fixed it, the issue was that certain features > were not supported and the frontend just assume they were cause that's how > it works on linux, and I'm no expert so I can go into much detail, but it > was related to checksum, tso and I think gso. > > I tried to bisect the git commits, but there was simply to much changes, > what I did find was that this never worked on 10.x +++ only 9, anyway > everything was reported there and eventually I got no replies back so I > gave up on NetBSD+FreeBSD-10. > > Unfortunately this needs someone with proper skills on either side > (netbsd/freeBSD) to be fixed, the perfect solution would be to add NetBSD > backend support for this things (just not sure if its worth the time for > the possible performance gain!? - also that's a question for the NetBSD > folks ofc) I think I have found what's causing the issue, but I don't have a NetBSD Dom0 in order to test the fix, could some of you please test the following patch and report back: https://people.freebsd.org/~royger/0001-xen-netfront-fix-feature-detection.patch It should apply cleanly against FreeBSD HEAD. Thanks, Roger.