From mboxrd@z Thu Jan  1 00:00:00 1970
From: Horms <horms@verge.net.au>
Subject: Re: Maybe a bug of xen
Date: Tue, 8 Nov 2005 15:06:36 +0000 (UTC)
Message-ID: <dkqets$p6p$1@sea.gmane.org>
References: <1131456468.12463.39.camel@localhost>
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

geaaru <geaaru@gmail.com> wrote:
> 
> With mii-tool I can't read eth0, while is unload module of eth0 and the
> reload module e1000 there is a new interface eth2 that mii-tool see
> correctly. While eth0 had always same error message. I don't know!
> On another abnormal of this system is that if I see traffic with
> ethereal from a client see arp request, while from ethereal on server I
> can't see arp request!
> 
> I think that this is a problem of xen, but maybe is a problem with e1000
> kernel module or other. I don't know
> Thanks for your replies.

Is e1000 used for eth0 or some other driver. If it is some other driver,
perhaps it doesn't have ethtool support.