[Solved] Crash in src/VBox/VMM/VMMR3/MM.cpp with linux kernel 4.6.1

[FredBezies]

Hello.

I'm facing a lot of guru meditations on my Archlinux with testing repositories enabled and VirtualBox 5.0.20.

Last time was with a Manjaro Linux ISO right on boot.

End of log right before Guru Meditation :

Code: Select all

00:00:52.151848 !! {vgasr}
00:00:52.151849 !!
00:00:52.151851 VGA Sequencer (3C5): SR index 3C4:04
00:00:52.151853  SR00:03 SR01:00 SR02:0F SR03:00 SR04:0A
00:00:52.151867 !!
00:00:52.151867 !! {vgatext}
00:00:52.151867 !!
00:00:52.151870 Not in text mode!
00:00:52.151872 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:52.151905 emR3Debug: rc=VERR_INVALID_STATE
00:00:53.152485 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:53.152520 Console: Machine state changed to 'GuruMeditation'

Linux kernel : 4.6-1
VirtualBox : 5.0.20-1

Simple question : my computer is powered by an AMD X2 215. I got a guru meditation only if I activate 2 CPUs in the virtualbox session. Related ?

[Perryg]

Since you only have 2 cores, assigning both to the guest could cause issues. Not to mention that you are using the Arch repo build which we have no idea what has changed and it makes it impossible to support here. I would ask the Arch folks.

[FredBezies]

Since you only have 2 cores, assigning both to the guest could cause issues. Not to mention that you are using the Arch repo build which we have no idea what has changed and it makes it impossible to support here. I would ask the Arch folks.

It happens right after linux 4.6 landed in testing repositories. So it likes an issue with this kernel. By the way, assigning 2 CPUs was working flawlessly until linux 4.6 arrival.

Maybe related hardened security in the new kernel ?

[Platypus]

Seems to be the same issue as described in ticket 15439 (sorry, cannot post URLs yet)

[FredBezies]

Seems to be the same issue as described in ticket 15439 (sorry, cannot post URLs yet)

Looks like the same problem here. Thanks for the ticket!

Looking at crash log, I can see that in my last crash log attached on ticket 15439 :

Code: Select all

00:05:34.719234 VMSetError: /build/virtualbox/src/VirtualBox-5.0.20/src/VBox/VMM/VMMR3/MM.cpp(685) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME

At least, we "know" where crash is happening ? Why ? Let's ask this to developers

[FredBezies]

Fixed since Virtual 5.0.22 (or 5.0.24 ?) release.