From owner-freebsd-virtualization@FreeBSD.ORG Wed May 8 10:16:04 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C66FEF0F for ; Wed, 8 May 2013 10:16:04 +0000 (UTC) (envelope-from nbari@inbox.im) Received: from ca2.route.mx (ca2.route.mx [72.55.175.69]) by mx1.freebsd.org (Postfix) with ESMTP id 7D0A932A for ; Wed, 8 May 2013 10:16:04 +0000 (UTC) Received: (route-mx 8260 invoked from network); 8 May 2013 10:09:21 -0000 Received: from unknown (HELO nbari-z200.diz.la) (nbari@inbox.im@route.mx) (envelope-sender ) by ca2.route.mx (route-mx) with CAMELLIA256-SHA encrypted SMTP for ; 8 May 2013 10:09:21 -0000 Message-ID: <518A244C.3010601@inbox.im> Date: Wed, 08 May 2013 11:09:16 +0100 From: Nicolas de Bari Embriz Garcia Rojas User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 MIME-Version: 1.0 To: "Marc G. Fournier" Subject: Re: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet References: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> <51882568.4080402@informatik.uni-bremen.de> <5189BD4D.70400@hub.org> In-Reply-To: <5189BD4D.70400@hub.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2013 10:16:04 -0000 When using bridge mode, use tap interfaces otherwise you will get problems when using more than one VM. regards On 05/08/2013 03:49, Marc G. Fournier wrote: > 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 ... > > > _______________________________________________ > 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"