fatal error in recompiler cpu

[DonVetOne]

Hello All

I have copied a virtual machine (XP) from Windows Vista Host to a Windows 10 host using a .OVA file

I have read a number of posts which advocate turning off HyperThread and Enabling VT-x in the host BIOS. I do not see these options in the BIOS!

I have uploaded the Vbox log file.... and would appreciate any assistance (Oh the XP guest starts up OK in Safe Mode )

Thanks

[socratis]

Your Celeron @ 2.80GHz does not have the VT-x capability.

The latest Win10 hosts require the latest VirtualBox, but the latest VirtualBox requires VT-x to run WinXP as a guest. There's not that much you can do.

[DonVetOne]

Thanks for the quick response - saves me from hacking and sweating the whole weekend.
TIme to upgrade the HW then!
Why does the VB start in safe mode though?

[socratis]

Because it goes into... safe mode, instruction-wise to the CPU. No fancy CPU tricks required in safe mode => VirtualBox can work in the old software rendering mode without hitting any "weird" instructions.

[mpack]

If you issue the following command (with the VM shut down) :-

Code: Select all

c:\Program Files\Oracle\VBoxManage modifyvm "Windows XP" --hwvirtex off

Then this should force VT-x use off in the VM and allow you to start your XP VM on this PC.

[DonVetOne]

Thanks. It did not work on the first try.... will try again after rebooting.

[mpack]

You can be quite certain that this tip works, I last tested it on Friday, using VirtualBox 5.2.6.

[DonVetOne]

Sadly there is still a problem after the command line fix.... which has a subfolder to Oracle by the way - VirtualBox ... so my command reads -- c:\program files\oracle\virtualbox\vboxmanage modifyvm "Windows XP" -- hwvirtex off -- Also there is no feedback on success or not?

I have attached the log file.

Thanks.

[mpack]

You can see in the log, the vbox file, and the vbox settings to confirm that the command was successful.

The new error is not the same. Was this VM always given such a resource limited recipe? Or did you take a working VM and try to squeeze it?

00:02:35.609099 00000000ffff0000-00000000ffffffff 00000000 PC BIOS - 0xffffffff
00:02:35.617705 fatal error in recompiler cpu: Trying to execute code with memory type addr_code=00000000fb75f020 addend=000000000c346000 at 00000000fb75f0fb. (iHandlerMemType=0x38 iMMIOMemType=0x30)
00:02:35.617714
00:02:35.617910 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:02:35.617986 Console: Machine state changed to 'GuruMeditation'
00:02:35.620523 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:02:35.620529 !!
00:02:35.620530 !! VCPU0: Guru Meditation -2301 (VERR_REM_VIRTUAL_CPU_ERROR)
00:02:35.620995 !!
00:02:35.621114 !!
00:02:35.621116 !! {mappings, <NULL>}
00:02:35.621119 !!

[mpack]

Looking around... perhaps upgrading the hardware is the best option to go for at this time. A single core PC running Win10, with 711MB free... even if you got XP running you probably wouldn't like the result.

[socratis]

VT-x is disabled:

00:00:19.512663   HMEnabled         <integer> = 0x0000000000000000 (0)

[DonVetOne]

Thanks, this VM was running successfully on another machine - and exported to the current machine using an .OVA file.
Just looked at the mainboard specs - and I cannot increase the RAM on board to beyond 2GB

[socratis]

this VM was running successfully on another machine

Let me take a wild guess... different hardware, right? Did you see mpack's advice? And I'm not talking only for the available memory...