Date: Mon, 6 May 2013 15:43:24 -0400 From: Zaphod Beeblebrox <zbeeble@gmail.com> To: "Marc G. Fournier" <scrappy@hub.org> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet Message-ID: <CACpH0MfXi_dAUOYW8kcY%2BzXFSFPGGCmn_FbCGABCsXW2XW_BNA@mail.gmail.com> In-Reply-To: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> References: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Heh. VirtualBox has (in my experience) been buggy as heck. Beyond buggy as heck. I have 3 virtualization platforms at my disposal (and the host here is win 7). VirtualBox, VMWare and Windows Virtual PC. I can report that under VirtualBox, every major type of guest caused stability problems with the host (Windows 7, Windows XP, FreeBSD, Linux). Stability problems would include crashing of the guest, crashing of the host, network bogons (from interfaces resetting to interfaces hanging --- like yours). I switched various guests to VMWare (the free "player" version) and everything was smooth. Really smooth. No problems running guests for _days_. No problems running multiple guests. I don't use virtual PC much --- it runs XP mode ... just because that's included with Windows 7... but it never causes problems either FWIW. It seemed to me that every update after Sun passed to Oracle brought more bugs. My advice: run away from VirtualBox. On Mon, May 6, 2013 at 3:12 PM, Marc G. Fournier <scrappy@hub.org> wrote: > > I'm having an odd issue with FreeBSD that I'm not sure how to trace / > where to look =85 > > I have 6 servers, all identical RAM / CPU / Ethernet / etc =85 4 of them = are > running VirtualBox, 2 are running Jails =85 one of the 4 I just switched = from > Jail -> Virtualbox =85 > > When running jail(s), the servers are rock solid =85 as soon as I switch = to > VirtualBox (the one I just switched is running one Vbox with a FreeBSD > Guest) =85 nothing else is running on the server =85 but I will get spora= dic > freezes of the Ethernet. One ran 46 days before it froze, then after a > reboot, it happened a few hours later, now its been running several hours > again without any issues =85 > > The machine itself is not frozen =85 I can connect via remote console, > login, do ps, etc =85 so its as if the Ethernet (bce device) just went > offline. > > I was pointed to a wiki about VirtualBox, and my current loader.conf look= s > like: > > =3D=3D=3D > aio_load=3D"YES" > kern.ipc.shm_use_phys=3D1 > accf_http_load=3D"YES" > if_bridge_load=3D"YES" > if_tap_load=3D"YES" > hw.pci.enable_msix=3D0 > vboxdrv_load=3D"YES" > net.graph.maxdata=3D65536 > =3D=3D=3D > > I'm running the latest version of 9-STABLE as well as the latest version > of vBox available in ports =85 the bce device is an older version of > Broadcom, so not dealing a new one with new features: > > bce0: <Broadcom NetXtreme II BCM5708 1000Base-T (B2)> > > And as I say, these work great with jail'd environments ALIASed onto them= =85 > > The vBox environments are all configured for network using: > > --nic1 bridged --bridgeadapter1 bce1 > > Maybe I'm setting up the network wrong? But, it does work for awhile =85 > > I'm not seeing any errors on the console when the ethernet stops working = =85 > nothing to indicate an buffer overflowing or something like that =85 but, > again, I can login and run commands, so if there is something I can run t= o > get more useful details =85 ? > > > _______________________________________________ > 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACpH0MfXi_dAUOYW8kcY%2BzXFSFPGGCmn_FbCGABCsXW2XW_BNA>