VirtualBox running slow/black screen on Surface Book 3

[Seri]

Hello there

this week i started studying IT, for class we use a Debian Linux VM on VirtualBox.

Long story short i cant get it to work properly... My VM always runs slow. I tried changing the 3D stuff to my GPU which is more powerfull than my Intel-processor but it doesnt seem to be working anyways, task manager shows my CPU beeing used instead of my GPU. Even though i changed it on the nvidia control pannel...

Did anyone ever have the same issue? VirtualBox+Surface devices

Kind regards
Christian

[Martin]

Same problem as in the post before yours:
Hyper-V is active, slowing down your guest VMs in Virtualbox (see the green turtle icon in the lower right corner of the guest window).
viewtopic.php?f=1&t=62339

Also your CPU only has 4 physical cores and you have assigned 4 virtual cores to your guest, leaving the host no free core to handle the environment when your guest gets a timeslice to run.
Try running the guest with only 2 virtual CPUs.

[Seri]

i dont have hyper-v activated but i really have no clue how to get into the bios to activate vt-x of the surface book because theres only UEFI... and yet i didnt find out how run bios :/

[scottgus1]

Other things in Windows 10 besides official "Hyper-V" use Hyper-V. The link Martin posted showed these other things.

Your log shows the exact wording that indicates Hyper-V is enabled, even if the checkbox in the screenshot is unchecked.

Since Hyper-V is on, VT-x is already enabled, so you should not have to go into the BIOS.

Look through the link again for the 'bcdedit' command, or for a step-by-step list, see HMR3Init: Attempting fall back to NEM (Hyper-V is active)

[Seri]

thanks for your help it worked, sort of i mean the turtle is still on there doing his, slowing it down thing, but at least i can use my vm now

[scottgus1]

Sorry we couldn't get rid of the turtle altogether, but if the guest is performing well enough then that's at least something. Glad you're up and running!

[Seri]

well i guess ill try and return my surface book and buy a not by microsoft created hardware product

[scottgus1]

You will run into Hyper-V on practically every Windows 10-based device, regardless of manufacturer. Better to keep plugging away at the attempts to remove Hyper-V, and look out for fully-Hyper-V-compatible Virtualbox.

Folks usually have success when they properly implement the bcdedit command. A few have further troubles and find that a few other things in post #2 of the 64-bits tutorial have to be handled too, then they have success.