From owner-freebsd-xen@FreeBSD.ORG  Wed Jan 26 20:52:28 2011
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 06570106566C
	for <freebsd-xen@freebsd.org>; Wed, 26 Jan 2011 20:52:28 +0000 (UTC)
	(envelope-from joovke@joovke.com)
Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au
	[211.29.132.183])
	by mx1.freebsd.org (Postfix) with ESMTP id 8182E8FC0A
	for <freebsd-xen@freebsd.org>; Wed, 26 Jan 2011 20:52:27 +0000 (UTC)
Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au
	[122.106.11.245])
	by mail02.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id
	p0QKqOKf021298
	for <freebsd-xen@freebsd.org>; Thu, 27 Jan 2011 07:52:25 +1100
Message-ID: <4D408984.3030502@joovke.com>
Date: Thu, 27 Jan 2011 07:52:20 +1100
From: Alex <joovke@joovke.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: freebsd-xen@freebsd.org
References: <C29EBBC5-FDAA-463A-B16A-1BF05F28925D@kfu.com>
In-Reply-To: <C29EBBC5-FDAA-463A-B16A-1BF05F28925D@kfu.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Help! Network issue with freebsd + Xen
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
	<freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
	<mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 20:52:28 -0000

It's would be a logical conclusion that it's an issue with the "re" 
driver then. I cant get my 8.2-RC1 XENHVM kernel to boot so had to 
resort to GENERIC, the HVM kernel just panics and I remember seeing 
something along the lines of "do something smart?"

does this patch you mention fix that?

On 27/01/11 02:48, Nick Sayer wrote:
> I saw this same high collision count before I converted my RootBSD domU from GENERIC to XENHVM. I do not see any collisions show up in netstat -i with xn0/xn1 instead of re0/re1.
>
> Of course, I needed kern/154302's patch to make the XENHVM kernel work. I hope that gets committed and merged back in time for 8.2-RELEASE.
>
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"
>