virtualbox.org

My first execution of virtualbox after an upgrade from fedora 23 to fedora 24 (fedup). After pressing "start" for a virtual XP, a text box popped up advising me of a serious error and to capture the contents of VBox.log and VBox.png (attached) for this web site and press quit. On pressing quit the system locked up - not just vbox, the entire system! I reinstalled everything and tried again with the same result.

I've been running linux since the mid 1990's and have never locked up the system before. I hope the attached shows a clear path to resolution.

OS: 4.7.4-200.fc24.x86_64
VirtualBox-5.1.6-1.fc24.x86_64
VirtualBox-kmodsrc-5.1.6-1.fc24.x86_64
Guest: Windows XP - 1990's vintage, but with all updates available before support dropped.
Oracle_VM_VirtualBox_Extension_Pack-5.1.6-110634.vbox-extpack

The virtualbox/XP combination has worked without problem for quite a long time and has survived multiple linux upgrades (fedup) such as this plus one scratch install after a hard drive failure.

The only thing I see (in the middle of the log) is:

00:00:24.542368 fatal error in recompiler cpu: Trying to execute code with memory type addr_code=00000000f6712020 addend=00007ff258c77000 at 00000000f67125c4. (iHandlerMemType=0x38 iMMIOMemType=0x30)
00:00:24.542368
00:00:24.542384 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:24.542399 Console: Machine state changed to 'GuruMeditation'

I'm hoping this is something obvious. Thanks!

I attempted to attach the log but get a "Sorry, the board attachment quota has been reached." message.

We are working on the quota error but in the mean time re-install VirtualBox and see if it clears the error.

The quota error should be fixed now if you want to try it again.

I did a reinstall but suffered the same freeze.

Correcting a statement I made - the system is locked up even BEFORE pressing the quit button. Locked up meaning there is no response to anything I do except the mouse pointer does move. I also couldn't kill the window system with ctrl-alt-backspace. I didn't think to try logging in from another system but will try that if this happens again.

I attached the log.

We do not support the rpmfusion version of VirtualBox, Fedora or rpmfussion does. You can ask them or you can remove theirs and install the official version from virtualbox.org.

I have a similar error when starting Windows XP guest in VirtualBox 5.1.6 (VirtualBox VM 5.1.6 r110634 win.amd64) on Windows 10.
This is the error from my vbox.log:

00:00:16.415856 fatal error in recompiler cpu: Trying to execute code with memory type addr_code=00000000f66db020 addend=ffffffff573bd000 at 00000000f66db423. (iHandlerMemType=0x38 iMMIOMemType=0x30)
00:00:16.415861
00:00:16.416677 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:16.416722 Console: Machine state changed to 'GuruMeditation'

When I uninstall the Avast virusscanner in the guest OS (or boot in safe mode), it boots without issues again. I wonder whether is a VirtualBox or Avast issue.
Do you have a virusscanner installed in the guest OS, if that's the case, you might try disabling or removing it. Note that I don't like this solution, especially on the Windows XP system I would like to have a virusscanner running.

Enabling VT-x would also fix that error I believe.

With VT-x enabled it works! Avast is now running fine on my Windows XP virtual machine, without crashes.
Initially I thought my laptop didn't have VT-x, but it does
Thanks.