Yeah, you're right. there is a log with the statement above. So what could I do?
- - - Updated - - -
Well, now I'm even more confused. I kept the vm with win 10 you wanted running, I was even able to complete the setup and boot into the desktop. When I'm adding one addition core (4 cores to be assigned are marked green in VBOX) the same issue occurs like before. The win7 vm with one core stuck as we know already. The image shouldn't be the problem, VMWare can handle it.
According to this microsoft page, it seems the Surface Book 3's does not support vt-x virtualization.
https://answers.microsoft.com/en-us/...4-90a3d44edd55
Edit: That's really a huge bummer about this device. Sounds like Virtualbox is going to be out of the game for you on that device. Best case you get the fallback feature, which is slow (when it does work) and crashes regularly.
That really stinks. i have buyers remorse, for you.
It feels a bit weird for a surface with i7 not to have VT-x.
i7-1065G7 has VT support on CPU:
Intel(R) Core™ i7-1065G7 Processor (8M Cache, up to 3.90 GHz) Product Specifications
If not Hyper-V is the issue here some other feature or option using it might still be to blame.
Got another idea: Check, if I'm not too late here, if 'Core Isolation' is enabled in Windows. I believe it so for a MS Surface.
Search in start menu for 'core isolation'.
If it is the case then Hyper-V is used in enhancing security by isolating kernel components through virtualization, hence VT is not visible to other apps. By disabling this feature and rebooting, you can test VirtualBox then and check.
As a side note, seems it works in VMware and not in VirtualBox...
Then they must be using some new 'tweaks' to make it work, just guessing here. In latest VirtualBox I recall that VT is a must. Though anywhere these days VT is a must.
Quote
