virtualbox.org

I'm running a Windows 2011 VM on a Windows 8.1 host. Everything runs fine, but when I leave it alone for a few hours I find my VM back crashed and aborted. I left my host locked but I'm not sure if it won't crash if I keep attending my PC, since this only happens after a few hours. What can I do to fix this? It produces the log in the attachment.

It looks like it's the SATA background writes task that is crapping out. Why not try running with the drive on the IDE controller? I would suggest raising a BugTracker ticket, but I see that some Storage bugs were already fixed in 4.3.14, and I assume you are sticking with 4.3.12 because of the ongoing hardening issues.

Other notes:

• You have Win2K8 selected as the guest OS type. Would 2K12 be more appropriate?
• The 7GB RAM allocation seems excessive.

The 8GB was actually a requirement for the SBS I'm currently testing. I'm indeed on v4.3.12. Would you recommend trying to update to v4.3.14 first? Or switch to IDE?

Update: I actually switched to the newest v4.3.16 now. In a few hours we will know if this is has fixed my storage problems, or I will head to the bug tracker

Actually no, I did not recommend either 4.3.14 or 4.3.16 because of the known issues, but now that you've upgraded we may as well wait and see what the result is.

The crashing in v12 is totally unacceptable for me so hopefully the known issues introduced in v14 and v16 aren't worse. Wow. I was really enthusiastic about Virtualbox but suddenly this feels so immature... The download page doesnt say anything about critical known issues for v16.

The discussions about these issues can be found in the Windows Hosts forum. It should be hard to miss.

VirtualBox is quite mature - but it also just had a major new anti-hacking features introduced in 4.3.14, since when it has transpired that many "legit" applications employ the same "hacking techniques". These problems will be worked out with time, but if you find this disturbing and would be happier paying for a VMWare etc license then certainly no one here will stop you.

Haha no I'm actually really happy but I was rather confused that you advised against upgrading to a new version while the download page doesn't say anything about this. For me it's no problem to wait for v16 being fine tuned when my VM keeps running (its still running as we speak). So I just wait, hopefully this fixes it. Was wondering if it might as well be caused by some energy management or something, as the host is a consumer Windows version which might not be that fine tuned on default for running VMs for longer periods of time

It kept running this night so I guess updating fixed my issues