Crash on save with Ubuntu Guest

[loukingjr]

I see the same problem when 3D acceleration is turned on.
I have Mint 17.1 cinnamon version 2.4.5 64 bit, on a Windows 7 64 host.

Saving state crashes the VM at the very end of saving, unless I first go to the Switch User screen.

VirtualBox is version 4.3.20
AMD 6870 graphics, with Catalyst 14.12

A couple things…
First Mint is not Ubuntu, Cinnamon is not Unity, so you really should have started your own thread.
I have Linux Mint 17.1 Cinnamon installed as a guest on a Mac host and it doesn't crash on Save State. Perhaps it's a problem with AMD graphics. I don't know. I have Intel graphics.

attach the vbox.log (compressed) for the guest.

On the other hand, Ubuntu has never returned from a saved state correctly for me. Of course I don't use Saved States.

[pfloding]

A Ubuntu derivative that doesn't use Unity, behaves pretty much exactly like Ubuntu using Unity.
Both use X11 for graphics.
The problem seems to be AMD graphics related.
I can see some commonality here -but making separate threads makes a lot more sense?

I'll fire up some Ubuntu to see if I have the same problem there, but my old Ubuntu VMs refuse to start with the new VirtualBox, so I'll have to install Ubuntu first before I can report back.

[pfloding]

I have now installed Ubuntu 14.04.1 64 bit in an otherwise identical VM to the Mint installation mentioned above.
The result was the same.
In fact trying to suspend the VM gives one invalid memory write error, whereas shutting down Linux gives a slightly different error.

In both cases not only does the VM crash, but Virtualbox also goes pear-shaped, and usually I have to kill all its processes to get back to normality.
Symptoms include: Virtualbox says the VM is still running after it has crashed, but any operation on the VM won't work. (And the window for the VM is gone.)

Fullscreen capture 30012015 162353 cropped.jpg (51.05 KiB) Viewed 2887 times

[pfloding]

Here are two logs: One is for a crashed save state VM with 3d enabled, the other for a normal save state with 3d not enabled.

[loukingjr]

A Ubuntu derivative that doesn't use Unity, behaves pretty much exactly like Ubuntu using Unity.

This is not correct.

FWIW, I have to clarify something. I have no trouble saving the state of any guest whether it's a Linux distro or a Windows guest. However, I have never been able to restore a Ubuntu guest correctly. None of my guests crash however. Ubuntu restores in an unresponsive state.

[pfloding]

When I said "behaves exactly like" I meant when it came to crashing Virtualbox.
For me the symptoms are the same for both.
When it comes to this type of issues there will be subtle variations.

[loukingjr]

Here are two logs: One is for a crashed save state VM with 3d enabled, the other for a normal save state with 3d not enabled.

Just had a look at the save state crash log. I don't know why having 3D enabled makes a difference but you are running into the security issues with VirtualBox for Windows.

00:00:02.146165 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x7 fAccess=0x2 \Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys:
00:00:02.146390 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: cached rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x2 fAccess=0x7 cHits=1 \Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys

Windows 4.3.20 specifically for errors due to security
As a workaround you could try uninstalling VirtualBox then install VirtualBox 4.3.12.

I was wondering why Saving State wasn't crashing on OSX or Linux hosts.

[mpack]

Those both looked like warnings to me, not errors: if it's a bad exe format then the OS can't load them so they can't be a threat. Certainly a switch to 4.3.12 will make the warnings disappear.

[loukingjr]

You could be right. I just don't know what else could be going on. The problem seems to plague Windows hosts only. I have multiple Macs and one Linux box and none of them have ever had the above mentioned problem.

[enric612]

Seem problem with windows host an debian 8 guest. Any news? Thanks!

[mhanor]

If you're using an AMD card, a Windows host and a 3D accelerated enabled guest, then you're triggering a bug in the AMD OpenGL driver, with the help of VirtualBox. Read this bug report

[mbonaci]

I found that this only happens with 3D Acceleration enabled. I have an AMD FirePro M5100. The Catalyst software is set up to use this card with both VirtualBox.exe and VBoxTestOGL.exe. If I change the Switchable Graphics Application Settings in Catalyst to force the usage of the onboard Intel graphics chip, the crash no longer occurs.

Thank you @landtuna, you saved my day!