From owner-freebsd-net@FreeBSD.ORG Sat May 2 15:03:52 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E97D11065686 for ; Sat, 2 May 2009 15:03:51 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mx1.freebsd.org (Postfix) with ESMTP id 2561A8FC14 for ; Sat, 2 May 2009 15:03:50 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so2223106qwe.7 for ; Sat, 02 May 2009 08:03:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=ez0k+HoP4BkmjJ4J8T3MuVq9g660zycSc5jE30Z0mkY=; b=rR+3k4onC+1k/pIUGzjFWyFtj9vsv7rqIeIXMlZnDq4RiXk5yEpnzrxjdoRm+lxXoO bSI4oWiJmsEF+aF+e2xbuFXeqSrCvytS7ZGEPNDHCIprzAEBQSFKQ1JefPcxOiVAB8W9 YfQg6kSMxYtoFpGXVnFB+55mDZ8OtroeC+hXo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xLV0nhzANDSCfSTQDqJvFBnB8AyjIKULzi9BuhLP1Fy2tuYpf7HHaNWiYB8FTw+WlP xeg0agyWnVmHN1pKtveHT9PzEAVPUMA3Q/tpxJZN35maJ/LYsleQjBFRP4Ka8qLNjNsk R47QW30j8QxCtjrvp0Ax5GvldGipOfxj1AdWA= MIME-Version: 1.0 Received: by 10.224.46.16 with SMTP id h16mr4210822qaf.179.1241276630387; Sat, 02 May 2009 08:03:50 -0700 (PDT) In-Reply-To: References: Date: Sat, 2 May 2009 08:03:50 -0700 Message-ID: <2a41acea0905020803s63b69b1awb39538f000f5bd5a@mail.gmail.com> From: Jack Vogel To: Ivan Voras Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: Regression: em driver in -CURRENT, "Invalid MAC address" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 May 2009 15:03:53 -0000 I'm willing to bet that its in fact the same problem that VMWare is having. Our method of getting the mac address changed, and the emulations seem to be unprepared for it. This was done for a real customer requirement to allow support of alternate mac addressing in firmware. What happens now is a warm reset of the hardware is done, followed by reading the RAR[0] register. In a real Intel NIC the mac address will be valid in that register, but in VMWare, and I'm willing to bet in VirtualBox as well, its 0. VMWare also has 3 choices of device (wow, amazing coincidence :), can you tell me when you pick e1000 what real adapter it claims to emulate? I am considering options for this problem. The one I lean toward right now is to make a "legacy" em driver, it will have support for ONLY pre-PCI Express hardware, it will be frozen as it were, the idea is that with no new work on it it will not suffer from any regression type failures. If I do this, there are some strategy issues, and its those I'm thinking about. In any case, I intend to have this problem resolved for 8's release. Stay tuned. Jack On Sat, May 2, 2009 at 5:25 AM, Ivan Voras wrote: > Hi, > > When I upgraded my 7-STABLE virtual machine under VirtualBox to 8-CURRENT, > the em driver stopped working. VirtualBox supports three different flavours > of emulated em devices, all of which result in the "Invalid MAC address" > error and cannot be used any more. > > The error was previously reported for VMWare, but since VirtualBox is as > different from VMWare as it can be, the problem is most likely in the > driver. > > I can provide more information if needed, I'll be at DevSummit with the > box. > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >