VT-x is disabled in the BIOS for all CPU modes.

[Schottenrock]

How can one enable VT-x again? It worked fine for months before I installed VB 6.1 My computer is a HP Elitebook 2570p running under Windows 10 Pro.

Logfile:
Für die virtuelle Maschine XP konnte keine neue Sitzung eröffnet werden. (Could not open a new session for virtual XP machine,)

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Fehlercode: E_FAIL (0x80004005) (Error code)
Komponente: ConsoleWrap

[scottgus1]

Look carefully through I have a 64bit host, but can't install 64bit guests. If you follow each thing to look for and cannot get running, zip and post one guest's vbox.log, using the forum's Upload Attachment tab.

[fth0]

It worked fine for months before I installed VB 6.1

VirtualBox versions up to 6.0.x can execute VMs without VT-x/AMD-V, whereas VirtualBox 6.1.x requires VT-x/AMD-V. Therefore I suggest to:

1. Check if your CPU provides VT-x at all, by searching with Google for "i7-3520M site:ark.intel.com" (replace "i7-3520M" with your CPU name in the search string). If your CPU doesn't provide VT-x, use VirtualBox 6.0.x.
2. Check for BIOS updates and check if your BIOS supports VT-x at all, by searching with Google. If your BIOS doesn't provide VT-x, use VirtualBox 6.0.x.
3. Check your BIOS for settings to enable VT-x. If your BIOS doesn't have a corresponding setting, VT-x is typically enabled by default.

Let us know what you find out ...

[VBoB13]

Hi technical people!

I have just tried to follow a course that uses Vagrant + VirtualBox to deploy a virtual ubuntu/bionic64 for development purposes.
While trying to set up the server, I run into the problem explained above.
I went into the BIOS and checked so that the VT-x option was enabled, and it is.
Just to make extra sure I was right, I checked for my processor (i7-6700) online and found out that it should support the feature.
I even tried to delete the previous set up virtual system and re-create an even later version through it, but that didn't work either.
Since nothing worked and I am still stuck at the very same error, I figured that I'd do as the pros here say: upload the log file

Hope someone is able to figure out what is going on and do please tell me if I've missed something.

[BillG]

All the tricks which we know of are listed in the reference you were given. Any new ones we learn of are added to the file.

I suspect that it was never available on your computer. VirtualBox 6.1 now requires hardware virtualization for all guests. If it is not available on your system (for whatever reason) go back to 6.0 where it is optional and you should be OK if the guest ran previously in 6.0.

[VBoB13]

Hi Bill
Thanks for the answer.. even if it was a little disheartening
However, my current version of VirtualBox is: 6.0.18 r136238 (Qt5.6.2)

Does this mean something else, or do I need to go further back than just 6.0?

[scottgus1]

@VBoB13:

I went into the BIOS and checked so that the VT-x option was enabled, and it is.

make sure that no other host apps are already using VT-x/AMD-v. The usual culprits are system level debuggers, other VM platforms, and some resident anti-virus applications.

Win2k12 and Win10, as these may enable Microsoft's Hyper-v VM platform by default: this grabs ownership of VT-x and won't play nice with VirtualBox

See what you can make of these.