VirtualBox 4.0.12 + FreeBSD 7.4-STABLE causes server hangs ...

[Rusty Nejdl]

I only had issues within the virtual system.  I haven't had any host 
system issues for over a year with virtualbox/nvidia/flash.  Knock on 
wood.  I think we're all running out of ideas so I was just chunking out 
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 … reading your note below, did this cause issues with your host
> OS (either a crash or hang?), or did it just cause problems within 
> 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 
>> start up (Fedora Core).  I ended up reinstalling the VM and that fixed 
>> the problem.  I also had the same issue with my FreeBSD VM and 
>> reinstalled that as a version 9 system and have no issues since.  I 
>> hadn't been maintaining those as well so I can't say when or why it 
>> 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 
>>> 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) = db7786a111db2e6176cb31c3efb654e9
>>> MD5 (linker.hints) = 3379a310e7e3b64272fb3b75ac5de1dc
>>> MD5 (vboxdrv.ko) = 8acb7a725c3e5ff7191be5281b003db5
>>> MD5 (vboxnetadp.ko) = 2198d3755cc63f774d7d9866d90eb016
>>> MD5 (vboxnetflt.ko) = 0842d0967ad97fd59591190f75af0d84
>>> pluto# tail -5 /root/pre-recompile-vbox
>>> MD5 (kqemu.ko) = db7786a111db2e6176cb31c3efb654e9
>>> MD5 (linker.hints) = 3379a310e7e3b64272fb3b75ac5de1dc
>>> MD5 (vboxdrv.ko) = 8acb7a725c3e5ff7191be5281b003db5
>>> MD5 (vboxnetadp.ko) = 2198d3755cc63f774d7d9866d90eb016
>>> MD5 (vboxnetflt.ko) = 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 
>>>> 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 
>>>> reboot …
>>>>
>>>>
>>>> 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 
>>>>>> after
>>>>>> starting up a VirtualBox guest?  I don't have anything to go on 
>>>>>> for
>>>>>> this … server seems to run fine up until I start up the guest 
>>>>>> OSs,
>>>>>> shortly afterwards the server just hangs …
>>>>>>
>>>>>> No errors in /var/log/messages, nothing on the remote console, 
>>>>>> it
>>>>>> just stops …
>>>>>>
>>>>>> This is with an Oct 26th 7.4-STABLE kernel … I saw the note on 
>>>>>> the
>>>>>> wiki about VIMAGE causing hangs, but I'm not using VIMAGE, so 
>>>>>> that
>>>>>> isn't it …
>>>>>>
>>>>>> These are 32bit OSs in the guest … I have three guests that I'm
>>>>>> trying to run … right now, I've just started up the one to see 
>>>>>> if
>>>>>> quantity makes a difference …
>>>>>>
>>>>>> I don't a serial console (remote server) that I can use to break 
>>>>>> into
>>>>>> the debugger ...
>>>>>
>>>>> You could try having a look at ~/VirtualBox 
>>>>> VMs/<machine>/logs/VBox.log
>>>>> and verify that the kernel module is build from the exact same 
>>>>> sources
>>>>> as your running kernel.
>>>>>
>>>>> --
>>>>> Bernhard Fröhlich
>>>>> http://www.bluelife.at/
>>>>
>>>> _______________________________________________
>>>> freebsd-emulation at freebsd.org mailing list
>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
>>>> To unsubscribe, send any mail to 
>>>> "freebsd-emulation-unsubscribe at freebsd.org"
>>>
>>> _______________________________________________
>>> freebsd-emulation at freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
>>> To unsubscribe, send any mail to 
>>> "freebsd-emulation-unsubscribe at freebsd.org"
>>
>> _______________________________________________
>> freebsd-emulation at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
>> To unsubscribe, send any mail to 
>> "freebsd-emulation-unsubscribe at freebsd.org"