M103 - Lab: Setting Up the Vagrant Environment

Hi,
I am running virutal box in windows 10 pro 64 bit OS.
getting below error while running vagrant up --provision :slight_smile:

There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [“startvm”, “df06cb8d-a3b7-4bfa-87d2-1e1729ea5f10”, “–type”, “headless”]

Stderr: VBoxManage.exe: error: Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).
VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

I tried disabling hyper-v as well, still same error.
Kindly help/suggest.

Thanks

Hey @Sailesh_95952

Have you turned on Intel VT virtualization in BIOS settings and then restart the machine?

From the lecture on Troubleshooting Vagrant setup

Here is the possible solution:

  1. Enable virtualization in the BIOS.
  2. Make sure you have Hyper-V turned off in Windows 10 For Windows 10: Press Windows key. Type “Turn Windows features on or off” Deselect the checkbox next to Hyper-V. Select OK. Select Restart now.
1 Like

Thank you…Got this fixed after enabling virtualization in BIOS settings…

1 Like

Hi @natac143,

I have Virtualisation enabled in the BIOS, Hyper-V turned off (Windows 10); however, I still get that error.

Any further suggestions?

Regards
Ossie

Sorry @Ossie_35926 I don’t really. Perhaps rebooting your computer. then running

vagrant destroy
vagrant up --provision

To try again.

Can you open VirtualBox at all?

Hi @natac13

I have virtualization enabled in the BIOS and Hyper-V turned off (Windows 10).
I have also done vagrant destroy and vagrant up --provision
But still i cannot setup.

Please advise. Thank you.

Stderr: VBoxManage.exe: error: The native API dll was not found (C:\windows\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).
VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

C:\Users\scheowx\m103\m103-vagrant-env>vagrant destroy
mongod-m103: Are you sure you want to destroy the ‘mongod-m103’ VM? [y/N] y
==> mongod-m103: Destroying VM and associated drives…

C:\Users\scheowx\m103\m103-vagrant-env>vagrant up --provision
Bringing machine ‘mongod-m103’ up with ‘virtualbox’ provider…
==> mongod-m103: Importing base box ‘ubuntu/trusty64’…
==> mongod-m103: Matching MAC address for NAT networking…
==> mongod-m103: Setting the name of the VM: mongod-m103
==> mongod-m103: Clearing any previously set forwarded ports…
==> mongod-m103: Clearing any previously set network interfaces…
==> mongod-m103: Preparing network interfaces based on configuration…
mongod-m103: Adapter 1: nat
mongod-m103: Adapter 2: hostonly
==> mongod-m103: Forwarding ports…
mongod-m103: 22 (guest) => 2222 (host) (adapter 1)
==> mongod-m103: Running ‘pre-boot’ VM customizations…
==> mongod-m103: Booting VM…
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [“startvm”, “9e1d1a7b-3a59-4854-823e-46283fe06a13”, “–type”, “headless”]

Stderr: VBoxManage.exe: error: The native API dll was not found (C:\windows\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).
VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Hey @Katehlyn_93604

The only thing that keeps coming up is the step you mention you have done. See this post
https://forums.virtualbox.org/viewtopic.php?f=6&t=91207#p438419

Couple things from the post is to make sure all Hyper-V options are de-selected and Virtualization turned on in BIOS and to do a power cycle(restart) or the machine.

If this still does not work I a sure @Kanika will be able to help you out.

Hi @Katehlyn_93604,

Please take a look at the following posts as well for reference and get back to me if the issue persists.

Thank you i will give it a try