[Solved]Win10 running extremely slow

[Olympus]

Hi all,

I have an issue running win10. When I start the VM, the display appears to be loading extremely slowly / with lag. These are some of the steps I've taken to try and resolve this:

• increase the processor count from 1 to 2
  increase video ram to 128 MB and 256 MB (started with 8 MB only)
  increase base memory from 3072 MB - 4096 MB (started with 2048 MB)
  enabled 3D acceleration
  disable nested paging
  tried different graphics controllers

The task manager shows about 30% CPU usage when the machine is up and running but it shows a very high power usage. On the rare occasion, I've managed to enter the password but at this stage, the machine is too slow to continue and the task manager still shows very high power usage. It could be that a certain combination of settings might solve it but I haven't been able to figure this out. I can run kali with no problems at all and the task manager output seems fine for that. I've also attached some logs however this time, I couldn't get to the password screen so there might not be enough information.

Any suggestions would be much appreciated, many thanks.

[multiOS]

You seem to have Hyper-V installed/enabled on your Windows Host and this, currently, blocks the necessary accesss to VT-x support which third-party virtualisation software such as VirtualBox needs to perform effectively.

00:00:03.529581 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:03:13.198382 /Devices/VMMDev/LargeReqBufAllocs 0 count

and

00:00:03.529364 Provider <string> = "HyperV" (cb=7)
00:00:03.562507 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
00:00:03.564779 MM: cbHyperHeap=0x200000 (2097152)
00:00:03.599195 GIM: Using provider 'HyperV' (Implementation version: 0)
00:00:03.599223 GIM: HyperV: Reporting vendor as 'VBoxVBoxVBox'
00:00:03.599228 CPUM: SetGuestCpuIdFeature: Enabled Hypervisor Present bit
00:00:04.218902 GIMDev: Registered Hyper-V hypercall page
00:00:04.218928 GIMDev: Registered Hyper-V TSC page
00:00:04.219526 APIC: Enabling Hyper-V x2APIC compatibility mode
00:00:04.219751 HTT - Hyper-Threading Technology = 1 (1)
00:00:04.219788 HVP - Hypervisor Present (we're a guest) = 1 (1)
00:00:04.219876 Raw Hypervisor CPUID Leaves
00:00:12.104245 GIM: HyperV: Guest OS reported ID 0x1040a0000271b
00:00:12.104289 GIM: HyperV: Open-source=false Vendor=0x1 OS=0x4 (Windows NT or derivative) Major=10 Minor=0 ServicePack=0 Build=10011
00:00:12.104383 GIM: HyperV: Enabled hypercall page at 0x000000000020e000
00:00:12.107583 GIM: HyperV: Queried extended hypercall capabilities 0x1 at 0x0000000000007000
00:00:12.107724 GIM: HyperV: Enabled TSC page at 0x000000000000c000 - u64TscScale=0xe1acd700000000 u64TscKHz=0x2c4fbd (2 903 997) Seq=1
00:00:12.107827 GIM0: HyperV: Enabled APIC-assist page at 0x000000000000d000
00:03:13.199388 /GIM/HyperV/0/Stimer0_Fired 0 times
00:03:13.199392 /GIM/HyperV/0/Stimer1_Fired 0 times
00:03:13.199395 /GIM/HyperV/0/Stimer2_Fired 0 times
00:03:13.199399 /GIM/HyperV/0/Stimer3_Fired 0 times
00:03:13.199402 /GIM/Hypercalls 1 times
00:03:13.200317 /MM/HyperHeap/cbFree 1970320 bytes
00:03:13.200328 /MM/HyperHeap/cbHeap 2096832 bytes
00:03:13.201277 /PDM/CritSects/MM-HYPER/ContentionR3 0 times
00:03:13.201284 /PDM/CritSects/MM-HYPER/ContentionRZLock 0 times
00:03:13.201289 /PDM/CritSects/MM-HYPER/ContentionRZUnlock 0 times
00:03:13.212232 GIM: HyperV: Resetting MMIO2 regions and MSRs

Have a look at the advice posed here: viewtopic.php?f=25&t=99390

The VirtualBox developers are working on the compatibility issues (and have been for a long time) but hitting Microsoft's continually moving target is quite complex. Your experience actually shows some progress has been made on the the issues if you are now able to run a Linux VM with reasonable performance.

[Olympus]

Turning off Hyper-V has solved the issue. Many thanks!

[fth0]

Additionally, do not disable nested paging. Nested paging has been a major breakthrough for virtualization performance over 10 years ago.

[Olympus]

Thanks for the suggestion. I will keep that in mind!

[OzKenny83]

You seem to have Hyper-V installed/enabled on your Windows Host and this, currently, blocks the necessary accesss to VT-x support which third-party virtualisation software such as VirtualBox needs to perform effectively.

OMG thank you so much for this pure-platinum piece of advice!! I thought I was going out of my mind; had turned off "Windows Hypervisor Platform" in the "Turn Windows Features On or Off" control panel, but missed "Virtual Machine Platform". That was the critical "feature" (more like absolute @#$%ing nuisance) that needed to be turned off.

With that disabled and VT-x enabled, my VM is literally around 30x faster...booting into initial Windows setup took well over an hour before, just to end up with a frozen screen. Now it loads setup within a few minutes!

So once again, thank you for saving what little hair I had left haha!