Posted May 12, 2016
It must be something you're doing or some other problem at your end that's causing this because I cannot reproduce these problems on any of my systems. I've even tested on my Windows install in case it's an issue with VirtualBox on Windows, but it works fine for me there too.
What exactly do you do before it breaks? Here are the details for my main system:
Host:
i7 2600k @ 4.4GHz
16GB RAM
Nvidia GTX 750Ti
Windows 7 Ultimate 64 bit / Linux Mint 17.3 Cinnamon 64 bit
VirtualBox 5.0.20 (with extensions installed)
VM:
Type: Linux
Version: Ubuntu 64 bit
2048MB RAM, 16GB VHDD (dynamic .vdi)
2 cores, PAE/NX enabled
Video memory maxed, 3D Acceleration enabled
All else at default settings
I installed Linux Mint 17.2 into the VM from mounted .iso: linuxmint-17.2-cinnamon-64bit.iso
MD5: b8a0651bb0086519fbf7a70fc12db17e
SHA-256: 9eca98efa8917d56985aeb0671fba63dc540f6350210fa2838b1ddf89317468d
Rebooted VM after installing and tested everything, all works perfectly as expected. Installed all available level 1-3 updates, rebooted then tested again - everything still works fine. Left it to sit for a while, everything still works fine.
There is no reason why it should be any different on your systems... as you've tried several systems with identical symptoms a hardware fault can be ruled out, and as it's running in a VM the environment should be fairly consistent.
What exactly do you do before it breaks? Here are the details for my main system:
Host:
i7 2600k @ 4.4GHz
16GB RAM
Nvidia GTX 750Ti
Windows 7 Ultimate 64 bit / Linux Mint 17.3 Cinnamon 64 bit
VirtualBox 5.0.20 (with extensions installed)
VM:
Type: Linux
Version: Ubuntu 64 bit
2048MB RAM, 16GB VHDD (dynamic .vdi)
2 cores, PAE/NX enabled
Video memory maxed, 3D Acceleration enabled
All else at default settings
I installed Linux Mint 17.2 into the VM from mounted .iso: linuxmint-17.2-cinnamon-64bit.iso
MD5: b8a0651bb0086519fbf7a70fc12db17e
SHA-256: 9eca98efa8917d56985aeb0671fba63dc540f6350210fa2838b1ddf89317468d
Rebooted VM after installing and tested everything, all works perfectly as expected. Installed all available level 1-3 updates, rebooted then tested again - everything still works fine. Left it to sit for a while, everything still works fine.
There is no reason why it should be any different on your systems... as you've tried several systems with identical symptoms a hardware fault can be ruled out, and as it's running in a VM the environment should be fairly consistent.