5.1 has a problem with crashing VM

[ChuckDMan:-)]

Hello, I upgraded to 5.1.x on CentOS 7(fully patched), but it crashed the VM's so much I switched back to 5.0.x. The crashes were random and I will monitor to see if 5.0.x has a problem, but I think it is related to the QT interface changes.

Environment: CentOS 7(Fully Patched) Old Install CentOS 7(Fully Patched) New Install iSCSI attached storage for VM and local storage on SSDs All VM's crashed at random times with 5.1.x installed

[ChuckDMan:-)]

Latest release(5.1.4 r110228(QT5.6.1)) seems to be stable.

[ChuckDMan:-)]

Well, that did not last. Random aborted VM. It crashed in VM with W7x64, on a sound pop-up when receiving outlook webmail alert for new message....

[chrijm]

There have been a few bugs about the guests aborting. With 5.1.4 r110228 it seemed to be fewer aborts, until today. Now I can not keep my Windows7 guest running for more than a min or two. Running w/ Null Audio Driver. Nothing suspicious in the logs, though they all end with lines like this:

00:00:25.130823 RTC: period=0x100 (256) 128 Hz 00:00:25.185097 RTC: period=0x200 (512) 64 Hz 00:00:27.061327 RTC: period=0x20 (32) 1024 Hz 00:00:27.075942 RTC: period=0x100 (256) 128 Hz

Host is OSX 10.11.6. Guest, Win7, Win10 seem to abort, win10 much less often, so far.

[Frank Mehnert]

Please test the latest 5.1.x test build from here. There were a number of fixes for audio-related crashes.

[chrijm]

Still crashes with Version 5.1.6 r110634

Crash while running:

The VM session was aborted.


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
SessionMachine
Interface: 
ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

Crash while restoring:

Failed to open a session for the virtual machine Win7_Dev.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

[chrijm]

Crash report from OSX for v 5.1.6 crash on restore VM

[chrijm]

One other thing I noticed on OSX hosts (didn't notice on Win or Linux host as don't use them very often, but will check next time) is that after it crashes, the mouse is invisible. It's there, just not actually displayed. Once you click the button, it reappears.