From owner-freebsd-net@FreeBSD.ORG Sat May 2 12:25:45 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 6CC0410656F4 for ; Sat, 2 May 2009 12:25:45 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 2B10C8FC12 for ; Sat, 2 May 2009 12:25:44 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1M0EHn-0006yK-Sj for freebsd-net@freebsd.org; Sat, 02 May 2009 12:25:44 +0000 Received: from 169-154.dsl.iskon.hr ([89.164.169.154]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 02 May 2009 12:25:43 +0000 Received: from ivoras by 169-154.dsl.iskon.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 02 May 2009 12:25:43 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-net@freebsd.org From: Ivan Voras Date: Sat, 02 May 2009 14:25:32 +0200 Lines: 12 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 169-154.dsl.iskon.hr User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) Sender: news Subject: 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 12:25:45 -0000 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.