From owner-freebsd-net@FreeBSD.ORG Wed May 8 02:49:59 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F2555658; Wed, 8 May 2013 02:49:58 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id BF949ED9; Wed, 8 May 2013 02:49:58 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.188]) by hub.org (Postfix) with ESMTP id 4F6411E56DB9; Tue, 7 May 2013 23:49:51 -0300 (ADT) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.188]) (amavisd-maia, port 10024) with ESMTP id 21571-07; Wed, 8 May 2013 02:49:51 +0000 (UTC) Received: from Marc-Fourniers-Mac-mini.local (S01067cb21b2ff4ca.gv.shawcable.net [24.108.26.71]) by hub.org (Postfix) with ESMTPA id A0E861E56DB8; Tue, 7 May 2013 23:49:50 -0300 (ADT) Message-ID: <5189BD4D.70400@hub.org> Date: Tue, 07 May 2013 19:49:49 -0700 From: "Marc G. Fournier" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org, freebsd-net@freebsd.org Subject: Re: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet References: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> <51882568.4080402@informatik.uni-bremen.de> In-Reply-To: <51882568.4080402@informatik.uni-bremen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2013 02:49:59 -0000 On 2013-05-06 2:49 PM, Norbert Beckmann wrote: > To Marc G. Fournier > > I do not think it's an issue with VirtualBox. I am running VirtualBox > under Solaris. And I never had problems with it. > Guests: ubuntu, Windows 7, Linux Mint, FreeBSD, Chrome OS. > But the people of VirtualBox themselves state that Windows is somewhat > delicate (don't remember whether they meant as guest or as host, I > think both). > Which would be comprehensible, because Windows has never become a real > multi user / multi process system as Unix was by birth (nearly). > I can neither help concerning the freezing Ethernet nor did I encounter > similar things (as far as I remember). My first thought is that its something in the vboxnet kernel module when using a bridge ... I think the problem has been getting progressively worse, with each upgrade, but since I upgrade both vBox and the kernel in tandem, I'm currently working on going 'back in time' with the code, see if I can find some 'stable point' ... If anyone with more knowledge can suggest any commands I can run to provide debug info, or such ... ? I don't mind debugging, just dont' know what to provide that is useful ...