Date: Tue, 08 Nov 2011 15:02:45 -0600 From: Rusty Nejdl <rnejdl@ringofsaturn.com> To: Hub- FreeBSD <freebsd@hub.org> Cc: freebsd-emulation@freebsd.org Subject: Re: VirtualBox 4.0.12 + FreeBSD 7.4-STABLE causes server hangs ... Message-ID: <assp.02936d44d4.e923a8d33e8ddb28efa7ad52d5ae02fc@ringofsaturn.com> In-Reply-To: <BEA58A86-3F04-473C-9B10-B1DE0F2D6318@hub.org> References: <944EDF5B-A27C-4211-867A-A1BDD279D1DF@hub.org> <e8d42f2e98337e04b0932e190050d11a@bluelife.at> <8A10496B-CFC4-4B8E-BF26-7C390525D91B@hub.org> <5A714905-6EA0-443B-8E3D-E0B31D7B192D@hub.org> <82362029de9ec807dcc6321c11760d96@ringofsaturn.com> <BEA58A86-3F04-473C-9B10-B1DE0F2D6318@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I only had issues within the virtual system. I haven't had any host=20 system issues for over a year with virtualbox/nvidia/flash. Knock on=20 wood. I think we're all running out of ideas so I was just chunking out=20 what I could to help. Rusty Nejdl On 2011-11-08 14:58, Hub- FreeBSD wrote: > Doesn't that sort of defeat the purpose of virtualization if the > virtualized environment can still blow up the host system? :) > > But =E2=80=A6 reading your note below, did this cause issues with your ho= st > OS (either a crash or hang?), or did it just cause problems within=20 > the > guest OS, or the ability to start it up? > > > On 2011-11-08, at 3:33 PM, Rusty Nejdl wrote: > >> The only thing I have to add is that I had a VM that would barf on=20 >> start up (Fedora Core). I ended up reinstalling the VM and that fixed= =20 >> the problem. I also had the same issue with my FreeBSD VM and=20 >> reinstalled that as a version 9 system and have no issues since. I=20 >> hadn't been maintaining those as well so I can't say when or why it=20 >> broke and didn't lose much. >> >> Rusty Nejdl >> >> On 2011-11-08 14:29, Hub- FreeBSD wrote: >>> Just to be extra paranoid, I just did a rebuild, and they were=20 >>> identical: >>> >>> pluto# ls -lt >>> total 512 >>> -rw-r--r-- 1 root wheel 272 Nov 8 16:21 linker.hints >>> -r-xr-xr-x 1 root wheel 284736 Nov 8 16:21 vboxdrv.ko >>> -r-xr-xr-x 1 root wheel 8640 Nov 8 16:21 vboxnetadp.ko >>> -r-xr-xr-x 1 root wheel 25504 Nov 8 16:21 vboxnetflt.ko >>> -r-xr-xr-x 1 root wheel 173240 Sep 6 2010 kqemu.ko >>> pluto# cat /root/vbox.modules >>> total 512 >>> -rw-r--r-- 1 root wheel 272 Oct 26 14:25 linker.hints >>> -r-xr-xr-x 1 root wheel 284736 Oct 26 14:25 vboxdrv.ko >>> -r-xr-xr-x 1 root wheel 8640 Oct 26 14:25 vboxnetadp.ko >>> -r-xr-xr-x 1 root wheel 25504 Oct 26 14:25 vboxnetflt.ko >>> -r-xr-xr-x 1 root wheel 173240 Sep 6 2010 kqemu.ko >>> pluto# md5 * >>> MD5 (kqemu.ko) =3D db7786a111db2e6176cb31c3efb654e9 >>> MD5 (linker.hints) =3D 3379a310e7e3b64272fb3b75ac5de1dc >>> MD5 (vboxdrv.ko) =3D 8acb7a725c3e5ff7191be5281b003db5 >>> MD5 (vboxnetadp.ko) =3D 2198d3755cc63f774d7d9866d90eb016 >>> MD5 (vboxnetflt.ko) =3D 0842d0967ad97fd59591190f75af0d84 >>> pluto# tail -5 /root/pre-recompile-vbox >>> MD5 (kqemu.ko) =3D db7786a111db2e6176cb31c3efb654e9 >>> MD5 (linker.hints) =3D 3379a310e7e3b64272fb3b75ac5de1dc >>> MD5 (vboxdrv.ko) =3D 8acb7a725c3e5ff7191be5281b003db5 >>> MD5 (vboxnetadp.ko) =3D 2198d3755cc63f774d7d9866d90eb016 >>> MD5 (vboxnetflt.ko) =3D 0842d0967ad97fd59591190f75af0d84 >>> >>> >>> On 2011-11-08, at 3:12 PM, Hub- FreeBSD wrote: >>> >>>> >>>> 00:00:01.470 VirtualBox 4.0.12_OSE r72916 freebsd.amd64 (Oct 26=20 >>>> 2011 14:27:19) release log >>>> >>>> vs >>>> >>>> 7.4-STABLE FreeBSD 7.4-STABLE #14: Wed Oct 26 14:15:28 ADT 2011 >>>> >>>> I make sure I built Vbox after my make install world, and before=20 >>>> reboot =E2=80=A6 >>>> >>>> >>>> On 2011-11-08, at 3:26 AM, Bernhard Froehlich wrote: >>>> >>>>> On 08.11.2011 02:24, Hub- FreeBSD wrote: >>>>>> Has anyone experienced any issues where a server hangs shortly=20 >>>>>> after >>>>>> starting up a VirtualBox guest? I don't have anything to go on=20 >>>>>> for >>>>>> this =E2=80=A6 server seems to run fine up until I start up the gues= t=20 >>>>>> OSs, >>>>>> shortly afterwards the server just hangs =E2=80=A6 >>>>>> >>>>>> No errors in /var/log/messages, nothing on the remote console,=20 >>>>>> it >>>>>> just stops =E2=80=A6 >>>>>> >>>>>> This is with an Oct 26th 7.4-STABLE kernel =E2=80=A6 I saw the note = on=20 >>>>>> the >>>>>> wiki about VIMAGE causing hangs, but I'm not using VIMAGE, so=20 >>>>>> that >>>>>> isn't it =E2=80=A6 >>>>>> >>>>>> These are 32bit OSs in the guest =E2=80=A6 I have three guests that = I'm >>>>>> trying to run =E2=80=A6 right now, I've just started up the one to s= ee=20 >>>>>> if >>>>>> quantity makes a difference =E2=80=A6 >>>>>> >>>>>> I don't a serial console (remote server) that I can use to break=20 >>>>>> into >>>>>> the debugger ... >>>>> >>>>> You could try having a look at ~/VirtualBox=20 >>>>> VMs/<machine>/logs/VBox.log >>>>> and verify that the kernel module is build from the exact same=20 >>>>> sources >>>>> as your running kernel. >>>>> >>>>> -- >>>>> Bernhard Fr=C3=B6hlich >>>>> http://www.bluelife.at/ >>>> >>>> _______________________________________________ >>>> freebsd-emulation@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation >>>> To unsubscribe, send any mail to=20 >>>> "freebsd-emulation-unsubscribe@freebsd.org" >>> >>> _______________________________________________ >>> freebsd-emulation@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation >>> To unsubscribe, send any mail to=20 >>> "freebsd-emulation-unsubscribe@freebsd.org" >> >> _______________________________________________ >> freebsd-emulation@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation >> To unsubscribe, send any mail to=20 >> "freebsd-emulation-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?assp.02936d44d4.e923a8d33e8ddb28efa7ad52d5ae02fc>