Failed to open a session for the virtual machine Linux Personal. VT-x is not available (VERR_VMX_NO_VMX). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}Intel-VT is enabled in the BIOS. I've checked Task Manager > Performance > CPU and saw that Windows did have access to hardware assisted virtualization. I haven't changed ANY settings since the last time I used VirtualBox, in or out of the program, other than installing a bunch of stuff like MySQL, Apache 2.4, Visual Studio 2017, Xenko, etc.
I don't quite understand where this all went wrong. I'm still looking into solving it myself but I would really appreciate if someone explained it to me.
And if you happen to know of any way the configuration files might cause this issue, then let me know. I've had times before where VBox would start with a somehow corrupted settings file and I'd have to go in and manually fix it (which just brought more errors whether I did it right or not.)
In case you're wondering about my CPU:
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz Base speed: 1.99 GHz Sockets: 1 Cores: 4 Logical processors: 8 Virtualization: Enabled L1 cache: 256 KB L2 cache: 1.0 MB L3 cache: 8.0 MB
Edit: Just FYI, I recently also installed some DirectX SDK stuff, Windows 10 SDK, etc. and I can't remember when but one of the recent tools I installed offered me something related to HyperV. And according to a StackExchange post (I can't share a link to it because this is a new account) HyperV causes conflict. |