Virtual box crashes

[djplayer]

Win 10 host, Linux Mint 18.2 guest.

I'm trying to install the development tools QtCreator and friends. Having alot of trouble. But that's not a VirtualBox problem. But I'm at a place now where the guest crashes the VM. I've never seen that before.

Can someone point me in the right direction to move past this?
This is my first guest crash, so I'm not clear on what's going on. I expected that any exceptions caused by a user program, such as QtCreator, would be caught by the guest os and never reach VirtualBox.

Crash Dialog from VirtualBox not the guest.

AS_000315x.jpg (33.25 KiB) Viewed 1514 times

Thanks,dj

[mpack]

Please provide a VM log file. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[djplayer]

Not clear which ones show crashes and which show normal shut downs. I've included 4 logs that were here.

[mpack]

3 out of the four logs you provided showed the abnormal termination. Only one of these was needed, hence I replaced your attachment with a smaller one.

Check if you still get a crash when 3D acceleration is disabled.

[djplayer]

Terminal activation of QtCreator

AS_000316.jpg (59.45 KiB) Viewed 1467 times

It works with 3D off. The last thing I did to get the environment working was install a package called qtbase5-dev-tools and this installation talked about removing things call mesa, which I recall may be an OpenGL implementation.

When I run this in one way it causes the same crash of the VM. Activating the program in a terminal gives the indicated messages. Not clear why the OS could trap the fault in one case, but not in the other.

[mpack]

Not clear why the OS could trap the fault in one case, but not in the other.

Rather obvious I'd have thought? When 3D accleration is enabled the GL calls are passed through to the host. When disabled it's handled by software rendering in the guest. So you get to choose which OpenGL driver errors out.

Also, one is a kernel (hardware driver) crash, the other is a software error, which is easier to do when using software rendering. All normal.

[djplayer]

Both the VM crash and the App crash were with 3D ENABLED with the same boot. SW App crash first, then tried it with another way and it crashed the VM.

So the VM is not supposed to crash, right? Bug? Right?

This is not an OS crash, right, but a VM supervisor crash? When the OS crashes on HW, it just reboots. And that did not happen here.

I have been using 3D enabled for YEARS now when using Linux in VirualBox. Never seen one of these crashes.

The same QtCreator software I'm running here works fine on a HW system with a 3D graphics card.

So how do I get this working on a VM?
Thanks a ton,
djp

[mpack]

So the VM is not supposed to crash, right? Bug? Right?

Wrong. The VM does not implement the host OpenGL drivers, your host's graphics card does. VirtualBox has no control over the quality of host graphics drivers, nor any way to prevent them from crashing.

Any crash which happens when a process is running will be reported by Windows as a crash in that process, which it is. However the information still needs to be used intelligently.