virtualbox.org

Where to even begin. Before VirutalBox 4.2.12 I had Mint 14 Cinnamon running with VirtualBox 4.2 .10 without issue. It ran so well, I would usually have it running days at a time without any issues.

A few weeks ago, 4.2.12 comes out, I decide to break the golden rule; "If it ain't broke, don't fix it!". I upgraded, I noticed that my copy of VB 4.2.10 was uninstalled from my Y: drive then 4.2.12 was installed on my C: drive. I figured I missed some option that created this unusual behavior. The update seemed to work for about a day or so then one day after entering my login info, VB crashed. To make a long story short, the only session I can use now is Cinnamon 2d, which is worthless because of the lack of 3d acceleration. Every other session does the same exact thing, as soon as I type in my password to login VB crashes. I tried uninstalling, reinstalling 4.2.12 with the newer Guest Addons and with the older 4.2.10. I have even tried uninstalling 4.2.12 and going back to 4.2.10 but they all produce the same problem. My settings, I have tried allocating 2 and even 4 GB of memory, 4X CPU, Enabling & Disabling PAE/NX, I have even tried disabling USB/Network/Audio but everything produces the same result.

In desperation I downloaded linuxmint-15-mate-dvd-64bit-rc build, which will boot into Live. However VB will crash after I try to install. The Live seems to work, until I load FireFox which also crashes VB.

I really don't know what to do, here are the two logs. I was running 4.2.10 when I produced the logs. One log is VB crashing when I try to boot Mint 14/Cinnamon after I login. The other log is from Mint 15 Live when I try to load FireFox. Maybe somebody will see something I missed.

Thanks!

Neither of the provided logs are complete. Make sure you shut down the VM before copying log files. You should still get a complete log even if the guest crashes. It's only if VBox itself crashes that the log might be truncated... and you have been rather vague about the nature of the crash.

A couple of things: it IMHO isn't a good idea to assign 4 cores to the VM when your CPU only has 4 cores total. You might starve the host of resources. Likewise, unless your VM really needs more than 2GB RAM, I'd stick with 2GB (max).

mpack wrote:Neither of the provided logs are complete. Make sure you shut down the VM before copying log files. You should still get a complete log even if the guest crashes. It's only if VBox itself crashes that the log might be truncated... and you have been rather vague about the nature of the crash.

A couple of things: it IMHO isn't a good idea to assign 4 cores to the VM when your CPU only has 4 cores total. You might starve the host of resources. Likewise, unless your VM really needs more than 2GB RAM, I'd stick with 2GB (max).

I just tried 2X CPU / 2 GB RAM, same problem.

Sorry about the log, this is all I get because it's the VM that is crashing when I try to login Mint 14, Mint 15 the VM crashes when I either finishing installing from LIve(on reboot) or load FireFox from Live. I get the infamous "Oracle VM Virtual Manger stopped..." message from Windows.

The only other thing I would try is turning off 3D acceleration. That and returning to 4.2.12 (no way bugfixes from .10 to .12 made your problem worse).

With truncated logs there isn't much else I can say. All you can do, if the problem persists with v4.2.12 is to post a BugTracker ticket.

mpack wrote:The only other thing I would try is turning off 3D acceleration. That and returning to 4.2.12 (no way bugfixes from .10 to .12 made your problem worse).

With truncated logs there isn't much else I can say. All you can do, if the problem persists with v4.2.12 is to post a BugTracker ticket.

I have not put v4.2.12 back on yet but just tried disabling 3d acceleration, this worked. All the previous sessions that were crashing VBox are now working. I thought I had tried this myself before posting here, clearly I did not.

Any suggestions how to get back 3D acceleration? I am running on a ATI/7850 w/ Cat 13.4 drivers. My thought was first upgrade back to v4.2.12, this time uninstall but manually remove anything that the uninstall did not remove, file & reg entries in Windows. Any other advice or a list of keys in the registry I should be looking for?

Thanks!

Why do you think you need to mess with registry keys? I would just upgrade as normal. Upgrading from .10 to .12 is very minor.

If you are saying that these VMs ever worked well, then you might want to consider what changed outside of VBox to make the 3D API unreliable. For example, did you upgrade the ATI host drivers?

mpack wrote:Why do you think you need to mess with registry keys? I would just upgrade as normal. Upgrading from .10 to .12 is very minor.

If you are saying that these VMs ever worked well, then you might want to consider what changed outside of VBox to make the 3D API unreliable. For example, did you upgrade the ATI host drivers?

Well, a few months back I upgraded my video card from ATI 5770 to a 7850 and also upgraded my Cat drivers. However, after the upgrade I was running perfectly stable for weeks. It was not until I upgraded VBox did everything go sideways. This is why I inquired about the registry, wondering if something might have gotten corrupted. You are right, it does point back at my system, but everything else on the system is perfectly stable except VBox.

Thanks again for all the help.