Date: Wed, 8 May 2013 09:32:14 -0700 From: "Marc G. Fournier" <scrappy@hub.org> To: Nicolas de Bari Embriz Garcia Rojas <nbari@inbox.im> Cc: freebsd-net@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet Message-ID: <E83E2EC1-5618-4EC9-BF51-04234ED8CC43@hub.org> In-Reply-To: <518A244C.3010601@inbox.im> References: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> <51882568.4080402@informatik.uni-bremen.de> <5189BD4D.70400@hub.org> <518A244C.3010601@inbox.im>
next in thread | previous in thread | raw e-mail | index | archive | help
Do you happen to know of a HowTO for doing this? =20 figure there are a few extra steps then simply: ifconfig tapX plumb --bridgeadapter tapX Thx .. On 2013-05-08, at 03:09 , Nicolas de Bari Embriz Garcia Rojas = <nbari@inbox.im> wrote: > When using bridge mode, use tap interfaces otherwise you will get > problems when using more than one VM. >=20 > regards >=20 > On 05/08/2013 03:49, Marc G. Fournier wrote: >> On 2013-05-06 2:49 PM, Norbert Beckmann wrote: >>> To Marc G. Fournier >>>=20 >>> 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' ... >>=20 >> 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 ... >>=20 >>=20 >> _______________________________________________ >> 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" >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E83E2EC1-5618-4EC9-BF51-04234ED8CC43>