virtualbox.org

Folks,
I have been a VirtualBox user for a year or so. I run Ubuntu in my VB. Recently I made the apparent mistake of upgrading my VirtualBox to v4.1.18 and my Ubuntu installation to v12.01LTS. I did this both at the same time and since that time I am getting virtualbox crashes, especially it seems if there is heavy network activity originating from the VirtualBox (Ubuntu Session).

I get a windows dialog that points at Vboxdd.dll as being the culprit with some memory exception there. After I get this exception it seems the virtualbox continues to run but without network connectivity until I close the Windows Dialog I get at which time the session closes and lists as "Aborted" in the VirtualBox manager.

I have 1GB dedicated to this session.

I attach the log file I captured immediately after the most recent crash.

I would appreciate some hints.

Thanks for posting the log - it makes a nice change, not having to ask for it.

I don't see any sign of a crash, although I do see an error report. It seems to be having some problem resuming from a suspended state, because of some issue with the guest additions ISO. I suspect the old GA ISO was mounted in the VM when you suspended it, I also suspect that you upgraded the VirtualBox software while you had VMs suspended... not a great idea.

I suggest you right click the VM and choose "Discard saved state". You should then go into settings and unmount the GAs ISO, before you run the VM.

Being a developer supporting a board on another opensource project myself I know the importance of posting real information in order to get real help.

So here is the results I had with your suggestions.

First the "Discard saved state" pick in the menu was greyed out so I could not do this.
Second there is no "unmount" options anywhere in the settings so I did not know what to do with this instruction.

What I did do is start the VM and then under the devices menu I was able to unmount the GA iso file. I then restarted the VM and ran the process I know that is likely to cause a crash.

The result is that I still get what looks like the same crash. I get dialog boxes from windows which informs be of the crash. As I said previously the VM continues to run but it seems that network subsystem has crashed. As soon as I close these windows dialogs the VM closes and is listed as "Aborted".

I attached screen shots of the dialog boxes I get and a new log file.

An update.

I decided to uninstall and then re-install virtualbox on this computer. So far seems to be working better now.

I suspect that something went amiss when the 4.1.18 install attempted to upgrade my previous 4.1.6 install but I am not sure.