[Solved] Backup under LinuxMint 17.2 does not work under Ubuntu 18.04.1 LTS

[Gringomg]

I backupped the complete .VirtualBox folder under LinuxMint 17.2
I restored the backup under Ubuntu 18.04.1 TLS. 64 bit.
Guest is Windows XP 32 bit.
I installed virtualbox-5.2_5.2.20-125813~Ubuntu~bionic_amd64.deb
On startup I got a critical error with the recommendation to seek the community.
Did the same in the past when I installed a more recent version of Linux Mint. Then it worked like a charm.

I attach the log file.
Any suggestion will be much appreciated.

[socratis]

Before I forget... you should ZIP your logs. It helps save a (virtual) tree or two...

VirtualBox VM 5.2.20 r125813 linux.amd64 (Oct 15 2018 14:36:50) release log
00:00:00.626575   Oracle VM VirtualBox Extension Pack (Version: 5.2.12 r122591; VRDE Module: VBoxVRDP)

The Extension Pack (ExtPack) has to match the VirtualBox version. You got to update your ExtPack at the same time you're updating your main VirtualBox installation.

00:00:00.700960 File system of '/home/jos/.VirtualBox/Machines/Virtual/Snapshots' (snapshots) is unknown
00:00:00.700980 File system of '/home/jos/.VirtualBox/HardDisks/Virtual.vdi' is ext4

Now, that's not something that you see these days any more. This is a layout from the VirtualBox 3.x days! It's amazing that it still works... At some point you might want to bite the bullet and "translate" it to the new format. Not now however, this is not your current problem...

This is your problem:

00:00:00.667249 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.
00:00:00.732613   HMEnabled         <integer> = 0x0000000000000001 (1)

You have VT-x enabled in the VM Settings » System » Acceleration, that's why VirtualBox talks about a 64-bit guest, even if it's the 32-bit version of WinXP. Your main issue however is this:

00:00:00.734580 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for all CPU modes
00:00:00.950254 Full Name: "Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz"

And this is "why" you're getting that error. You will need to address/fix the hardware virtualization availability. Your i5-3320M CPU most certainly supports hardware virtualization, so it's a matter of enabling it in the BIOS. See your PC's manufacturer help on how to do this. Also, make sure that nothing else has an exclusive hold on that.

Finally, I realized something that ties to the very first thing I said; ZIP the log... You butchered the log!!! You chopped it so that it would fit in the limit of 128 KB. Please do me a favor and delete the chopped log, and replace it with a complete log, from a complete run, but ZIPPED first. I bet you it will be way below the limit...

[Gringomg]

Thanks to your suggestions: it works like a charm.
Thank you so much for your help!

[socratis]

Please do me a favor and delete the chopped log, and replace it with a complete log

You did the first part (delete) alright, but you never replaced the log. Oh well...

Marking as [Solved].