Change PC due to malfunction. VM with win7 loads very slow and load processor 100%.

[Yakov]

Hello.
I replace my PC due to malfunction. So I just copied the VM to a new PC from back up of old PC.
I have VM with several snapshots (win7), so I want to restore the VM.
For the machine was defined 1 core.
To load the VM takes something like 40 minutes.... and the machine works very low. The processor looks load 100%.

When I add more cores to the machine , it load it heavily on my PC , but the VM looks stuck in windows startup state.

How can I resolve the problem ?
Thank you in advance.

[scottgus1]

Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

So I just copied the VM to a new PC

How did you do this? There are several wrong ways and one right way.

[Yakov]

I attached the logs.
The previous PC dead , so I didn't able to copy the VM by export/import. I copy it by copying files from old HD to a new PC.

Thanks.

[mpack]

You have a 6 core host, why only 1 core for the VM? Obviously that's going to slow things down. Usually 2 cores is ideal.

But, the main reason for slowness is that you have Hyper-v enabled on your new host.

00:00:06.564771 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:06.727978 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

Related FAQ (especially posts #2 and later): FAQ: I have a 64bit host, but can't install 64bit guests.

[Yakov]

I already checked every thing in all FAQs.
BIOS, Windows Defender, Hyper-v, Credential Guard , Device Guard, .....

The last thing , may be some resident anti-virus applications blocks it , but I don't know to check it..... (I can't delete Antivirus on this PC).
Already exhausted with this issue

BTW: if I add more cores , the VM stuck at the beginning.

[mpack]

If you followed everything in all FAQs then that line would not still be present in the log.

Please don't try to persuade us otherwise - we have had this conversation dozens of times, and it always ends the same way: something missed from the FAQ, usually it's the "bcdedit /set hypervisorlaunchtype off" thing.

Leave the adding of CPUs until VT-x is available.

[Yakov]

1. I enabled it in BIOS.
2. Hyper-v disabled.
3. Windows Defender > Device Security > Core Isolation Details turned off.
4. HKLM|SYSTEM|CurrentControlSet|Control|DeviceGuard|EnableVirtualizationBasedSecurity|Enabled set to 0.
5. Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security to Disabled.
6. "bcdedit /set hypervisorlaunchtype off"
7. Credential Guard (check):
Credential-Guard is not running.
HVCI is not running.
Config-CI is not running. (Not Enabled)
Not all services are running.
8. Windows Sandbox - not found on my PC.
9. "Turn on fast startup" - disabled.

Antivirus McAfee.
did I miss something ?

[scottgus1]

The only way for us to possibly tell you what's wrong with your computer is for us to remote into it or for you to ship it to one of us. And we don't do either of those things, so we will not know what is wrong with your computer.

All we have is the 64-bits tutorial. You need to go through it line by line, letter by letter, until you find the thing that has been missed.

Or install the host OS fresh on another drive, install Virtualbox, and test a guest. Then add one of your other programs, test Virtualbox again. Rinse & repeat until everything is installed. Once you find Virtualbox not working again, the last program you installed is the culprit.

I copy it by copying files from old HD to a new PC.

A bit more detail would have been clearer, for there's more than one way to copy a guest. If you brought just the guest's disk file, then that would not be enough. If you brought the guest folder with the guest's .vbox file too and all the other files therein, along with the guest disk file, then used the old .vbox file to register the guest, that would be the right way.

[Yakov]

Can you do remote session to my PC in order to identify the issue ?

[scottgus1]

No thanks, remoting in is something I wouldn't want to bother with. We are all fellow users and volunteers on the forum. No official tech support is available for free Virtualbox.

Antivirus McAfee.

What about this? Antivirus can interfere with Virtualbox's use of 'virtualization technology': VT-x/AMD-V. Windows 10 does not need extra antivirus. Try uninstalling it, not just disabling it.

Otherwise, the 64-bits tutorial contains absolutely everything we know of to fix no-VT-x/Hyper-V issues on Windows hosts.

All we have is the 64-bits tutorial. You need to go through it line by line, letter by letter, until you find the thing that has been missed.