Ubuntu-Mint guest not booting up when more than 1 CPUs are specified in the Settings

[vatsan]

Looks like with my VBOX v6.1.32 on Windows 10 x64 (Professional) Host, I am forced to use only 1 CPU for my guests. If I assign more than 1 CPU, the Guest OS (Linux Mint 20.3 x64) doesn't start up at all - I just keep seeing the black screen (not even the initial Mint Logo) endlessly. Any fixes / workarounds? Thanks in advance.

[AndyCot]

Do you have hyper-v enabled? Turn if off and see if this helps. If it does not then please supply a VB log.

If you need hyper-V try VB 6.1.30.

[vatsan]

Thanks for the reply. No; I don't have Hyper-V. I have been burnt by it in the past and am fully aware that there are issues running VBox with Hyper-V enabled. PFA the VBox log

[fth0]

No; I don't have Hyper-V. I have been burnt by it in the past and am fully aware that there are issues running VBox with Hyper-V enabled.

00:00:06.317565 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:06.369924 NEM:  info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:06.370036 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

Well, if you're fully aware, you'll recognize that VirtualBox disagrees with you.

[AndyCot]

Got to love-v and MS making it hard to turn on and off.

I use a program called "HyperVSwitch.exe" to switch it on and off. It's github page is https://github.com/ygoe/HyperVSwitch. This may help with getting hyper-v disabled.

[vatsan]

Screenshot 2022-02-11 152958.png (55.24 KiB) Viewed 1388 times

Screenshot 2022-02-11 152832.png (52.05 KiB) Viewed 1388 times

That's confounding. I have ensured that relevant optional features are not selected - please refer to the PNG Images I have attached herewith

[scottgus1]

There are a lot more services than official 'Hyper-V' that use the Hyper-V engine. That's why we recommend not using Windows Features to try to turn off Hyper-V. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[AndyCot]

1000% AGREE and have been burnt in the past with "trying" to use the Windows features to turn hyper-v off.

[vatsan]

Thanks to all for suggesting ways to disable Hyper-V completely. I tried all the ways to the letter but unfortunately I am unable to disable it. Now I remember something - a couple of months back I had installed WSL2 and then removed it. My problem with VBox started only after then. But the consolation is, I am able to run the VMs with just 1 CPU so, I am not lost in the sea. Once again, thanks to all those who chipped in.

[scottgus1]

I tried all the ways to the letter but unfortunately I am unable to disable it

If you don't get the standard virtualization icon, post back exactly what you did and we'll try to help some more.

If your computer is running in a corporate environment with IT overlords, they may have forced Hyper-V, and none of the above will help. You will have to get IT to turn off Hyper-V so that you can run Virtualbox.

Note the first underlining, and confirm the second underlining does or does not apply.