Description

I have a Arch Linux installed in VirtualBox, and the VirutalBox crashes every time when I tried to install some new packages or perform a system upgrade in it. I believe that it must have something to do with the heavy disk I/O.

I never came to this situation until about two weeks ago, so I believe that this is a latest introduced bug of VirtualBox.

It's a 4-5 day old installation of Arch on a dynamic 200gb .vmdk, which I just created by cloning a static 8gb .vmdk as by this tutorial. I ran gparted after the cloning to resize by /dev/sda3 and /dev/sda4 to be about 30gb and 10gb respectively. I was mucking around with the .xml config files for both .VirtualBox and my specific Arch VM previously, so I assumed this crash was caused by something I completely screwed up in the process, but it only seems to happen during intensive network operations (like wget).

It's a 4-5 day old installation of Arch on a dynamic 200gb .vmdk, which I just created by cloning a static 8gb .vmdk as by this tutorial. I ran gparted after the cloning to resize by /dev/sda3 and /dev/sda4 to be about 30gb and 10gb respectively. I was mucking around with the .xml config files for both .VirtualBox and my specific Arch VM previously, so I assumed this crash was caused by something I completely screwed up in the process, but it only seems to happen during intensive network operations (like wget).

It's a 4-5 day old installation of Arch on a dynamic 200gb .vmdk, which I just created by cloning a static 8gb .vmdk as by this tutorial. I ran gparted after the cloning to resize by /dev/sda3 and /dev/sda4 to be about 30gb and 10gb respectively. I was mucking around with the .xml config files for both .VirtualBox and my specific Arch VM previously, so I assumed this crash was caused by something I completely screwed up in the process, but it only seems to happen during intensive network operations (like wget).

I'm getting this issue, but with an install of Ubuntu. I'm trying to compile OpenELEC XBMC, but the VM session crashes with "VirtualBox Stopped Responding". It always does it whilst trying to download a package.

I also have "WSAEnumNetworkEvents tcp error 10038" in my log (which is how I found my way here).

This was on the latest release, and also the release prior. I'm now on 4.0.16 to see if that helps :(

Could you please download the build of VBoxDD.dll with enabled logging? After downloading please, replace original VBoxDD.dll from VirtualBox 4.1.15 r77799 with downloaded DLL (please, safe original DLL in safe place). Then please launch your VM in the following way

I'm pretty sure that in my case the VM Abort appears after sometime of using FileZilla to access some FTP server.
Unfortunately, I can't use the bridged mode and need to access the FTP server, which make this issue a real pain.

Could you please download the build of VBoxDD.dll with enabled logging? After downloading please, replace original VBoxDD.dll from VirtualBox 4.1.15 r77799 with downloaded DLL (please, safe original DLL in safe place). Then please launch your VM in the following way

Still log doesn't clarify what wrong is going on so could you please to apply instructions from comment 15 and use DDL with improved logging VBoxDD.dll. Additionally could you please, dump network traffic using following instructions.

Still log doesn't clarify what wrong is going on so could you please to apply instructions from comment 15 and use DDL with improved logging VBoxDD.dll. Additionally could you please, dump network traffic using following instructions.

Could you please attach the log? Could you please describe how do you generate huge load on the guest?

Sure, it doesn't always crash. When it crashes again I'll provide the log. FYI: I don't have any debugging DLLs insalled. I'm downloading on that machine OpenBSD snapshots quite often from various http or ftp mirrors. Nothing fancy really.

If you need me for testing, I get a systematic way to make it crash by downloading a FTP file with by 100Mb connection on my dedicated server. Trying to get now to collect "network dump"...

Thank you Eric for your help. Could you please send it to me (vasily _dot_ levchenko _at_ oracle _dot_ com) by mail?

My VB crashes typically after 400MB downloaded, which makes the capture very large. Could you provide me a debug version with logs to try?
I'm trying to setup a build environnement to help solving this issue with an instrumented slirp/socket classes to handle the 10038 (not a socket error WSAENOTSOCK). It will be faster if you do it by yourself...
Eric

I'm trying to setup a build environnement to help solving this issue with an instrumented slirp/socket classes to handle the 10038 (not a socket error WSAENOTSOCK). It will be faster if you do it by yourself...

Ok, I will build log enabled bits and share it with you. Btw, Does it change anything for you in case of single CPU guest?

After replacing VBoxDD.dll with VBoxDD.dll.4.1.20_10513 virtualbox fails to start, see previously attached file for details. Not sure is that related to the fact, that Oracle_VM_VirtualBox_Extension_Pack-4.1.20.vbox-extpack fails to install on my machine with error

Finally had a chance to look into this again. All below tests are done with 4.1.22 (the latest reported by Help->Check for Updates at the time of writing this). Enabled packet capturing on the guest, which look more or less as following command:

however file finished successfully. So I looked again at my previous downloads and noticed that on that particular mirror I was using FTP to trigger the crash. So I decided to download again the same file via:

Left VirtualBox unattended for a while. Came back and wget transfer was stalled. Disappointed decided to CTRL+C the transfer (which worked fine) and then typed 'halt -p' to power off the guest OS. In a moment my CPU fan kicked off like crazy. Windows' TaskMgr.exe showed that VBoxHeadless.exe is using more CPU than usual. Few seconds later I see crash report from Windows about VBoxHeadless.

So, this crash is different than previously reported. Not sure why. See file attached to this ticket very recently (log.gz) for the log from that session. The pcap file is around 330MB uncompressed, 289MB gzipped. I'm going to upload it to my web server and send you a link via email given in previous comments in this ticket. In Oracle VM VirtualBox Manager guest is reported as Aborted.

Left VirtualBox unattended for a while. Came back and wget transfer was stalled. Disappointed decided to CTRL+C the transfer (which worked fine)

Do I understand you right, that CTRL+C stopped the wget ?

and then typed 'halt -p' to power off the guest OS. In a moment my CPU fan kicked off like crazy. Windows' TaskMgr.exe showed that VBoxHeadless.exe is using more CPU than usual. Few seconds later I see crash report from Windows about VBoxHeadless.

And guest is really crashed on 'halt -p'?

I'm going to upload it to my web server and send you a link via email given in previous comments in this ticket. In Oracle VM VirtualBox Manager guest is reported as Aborted.

Thanks for a link. It looks like according to log that crashed VBoxSVC rather than guest.

I do not understand the question. I'm not sure did guest crashed. I think VirtualBox running the guest crashed. Not 100% sure. It crashed in usual way for me, however triggered in different way that always. This time not by constant network traffic.

Thanks for a link. It looks like according to log that crashed VBoxSVC rather than guest.

Not sure what VBoxSVC is. Is there anything more which I can test? I think I'll repeat the tests few times again.