virtualbox.org

I have a new PC with Windows 10 Home v operating system 1809.
I installed the ORACLE VM VirtualBox program in the latest version 6.0.4-128413-win and the Extension Pack-6.0.4 fully functional.
I state that on the old PC with Windows 7 Pro operating system (64Bit) I had created a fully functional virtual machine with Windows XP Pro (32Bit) operating system that also used the Guest Additions.
Now I was trying to rebuild the same machine on the new PC using the same configuration used in the old PC.
The machine is created without problems.
Start the machine after inserting the Windows XP operating system CD into the optical drive.
The loading of the operating system begins but unfortunately almost immediately the machine goes into critical error and is stopped.
I would like to have help with the problem if possible.
I have related Log files if they can be useful.
Where can I put it to allow you to see it ?
I remain available for any further clarifications regarding the configuration adopted and I thank you for your kind attention.
Giulio.

Giulio wrote:Now I was trying to rebuild the same machine on the new PC using the same configuration used in the old PC.

If you still have access to your old PC/data, then it may be easier to simply copy the VM over to the new PC. See the FAQ "Moving a VM" and interpret it as "Backing up a VM" or "Copying a VM".

If that's not possible, then we need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

Thanks for the diligent answer.
From the old PC I exported the VM to a .ova file.
I imported it to the new PC and the new VM was created correctly.
The problem arises when the start-up occurs, the loading form of the operating system is displayed correctly but after a short time the machine goes into critical error without finishing loading it.
I recovered the VBOXLOG file I sent you in ZIP format.
Giulio

socratis did not advise you to export the vm. He advised you to move it, and gave you a reference to a "howto" to help you do so.

Thanks for the advice.
I'm sorry but I forgot to mention the fact that the old PC is no longer working and therefore I can't access it.
I then tried to use the exported file that I had saved separately.
Now I tried again to create the VM again and as highlighted in the first post it doesn't work.
I then proceeded to save the log file that I attach.
thanks for your posts.
Giulio.

00:00:01.818647 CPUM: No hardware-virtualization capability detected
00:00:04.542182 Full Name: "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz"

I don't know why the first message comes up, but can you check your BIOS that hardware virtualization is enabled?

Thank you Socratis for finding out where the problem lies.
I investigated and found where windows 10 has a flag that enables hardware virtualization.
For versions of windows 10 where Hyper-V is not provided, this flag is not enabled.
After enabling it, virtualization was successful.
Problem solved.
The path to get to the flag is as follows:
- Windows key + x
- App and features
- Programs and features
- Enable or disable the Windows feature
- Locate the Virtual Machine Platform option enable it and then press OK
At this point some programs will be loaded and then after restarting the machine the virtualization can be used.
Thank you again for your kind attention.
Giulio.

Giulio wrote:Locate the Virtual Machine Platform option enable it and then press OK

I'm sorry, but that doesn't make sense to tell you the truth. If anything, I would expect this to be a restriction, as I believe it enables Hyper-V on your Windows Host, or it will at some point, see "Microsoft plans to add native support for Virtual Machines in Windows 10" and/or search for "Virtual Machine Platform", with the quotes...

Strange as it may seem, it did not seem (at first) to trouble VirtualBox. I have an Insider build (Version 1903 build 18356) with VirtualBox running on it. The feature is now called Windows Hypervisor Platform with a popup description Enables virtualization software to run on the Windows hypervisor. With this enabled, the Vista 32-bit guest still ran normally (no turtle, just a V).

I then realized that I had not rebooted. I checked bcdedit, and sure enough hypervisorlaunchtype was now set to Auto. After a reboot, the vm failed to run (no doubt because the hypervisor was now loaded). My guess is that this feature activates the hypervisor without adding the Hyper-V program modules, so it should still block VirtualBox, not enable it, as the OP claimed.