I'm getting this error while loading a Puppet image from a Oracle virtual box. How can I fix it?
Failed to open a session for the virtual machine learn-puppet-centos-6.4-pe-3.1.0.
VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED).
Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
In addition, I see that the acellerate-tab in Virtual Box is disabled.
I believe VirtualBox is throwing this error for a number of reasons. Very annoying that it's one error for so many things but, I guess it's the same requirement it's just that the root cause is different.
Potential gotchas:
So for my little mess around machine that I'm resurrecting that has 8GB RAM but only a ye-olde Core i3, I'm having success if I install: 32 bit version of linux, allocating 2.5GB RAM.
Oh, and wherever I say "VT-x" above, that obviously applies equally to AMD's "AMD-V" virtualization tech.
I hope that helps.
That's pretty simple problem to fix as you can see in the error message
You don't have to go with the previous version of virtual box, rather try this
go to your BIOS setting...
inside the virtualization tab enable the virtualiation techniuqe
restart your PC and you will have your Virtual Box up and running.
There is an option in the Virtual Box itself. If you look in the Oracle VM Virtual Box Manager. Select the Virtual Box you want to start. Go to System, the second from above item in the right pane. In System go to the third tab called acceleration. In that tab the first check box is called something like: 'VT-x/AMD-V' (I have the Dutch version, so I don't know the exact string) UNCHECK And then start. That worked for me.
I also got this problem after an upgrade. And I did not have the problem before. But I fail to see the exact connection between the update and the check/unchecking of that option.
By the way, I have no idea where the hell that 'virtualization tab' should be in my 'BIOS'. Maybe I was looking in my PC's BIOS not the System page here which is the BIOS of the VM Machine maybe and that is what you meant Veer7? If it was, it was pretty unclear you meant this. Maybe it's because I have OVM in Dutch not English. But there was nothing called BIOS in the Oracle VM Virtual Box Manager I could find.
I have "Intel Virtualization" set to enabled in my BIOS, and I still get this error.
It turns out the problem is that I had Hyper-V enabled in "Windows Features", and apparently VirtualBox and Hyper-V don't play nicely together.
I went to Control Panel -> Windows Features and unchecked Hyper-V. After a reboot, Hyper-V was gone, and I was now able to run my 64-bit VMs again in VirtualBox.
That error message also appeared into my VM. First of all, I tried to disable the option "Enable VT-x/AMD-V" (you can find it opening the settings of your VM: Settings->System->Acceleration), there was a warning saying that "Invalid settings detected (you accept the changes and the box was selected again).
Then I read this posts and I tried to enable the Virtualiation Techniuqe (used when you want to enable various VM in your computer (by default is set as Disabled because you don't need that property working.
I upgraded to Windows 10 x64 (from Windows 7 x64), had a VirtualBox Windows 10 x64 VM, but got the VT-x error. My BIOS was enabled, settings - everything in this post was addressed, but still got the VT-x error.
What fixed it for me was to go to Lenovo and install the latest BIOS for my W550s ThinkPad. Once the upgrade was installed, VirtualBox gave me the x64 options again with no more VT-x errors.
If you are running a W550s, the BIOS version I installed was from September 2015, "BIOS Update Utility" n11uj05w.exe, version 1.10 from the Lenovo website.
Recently I had this same problem on windows 10 - after installing Hyper-V & other windows features like:
Windows Projected File System, Windows Sandbox, Windows Subsystem for Linux, Work Folders Client,
And it stopped working for me;(
