Vagrant up --provision failing due to VBoxManage.exe: error

C:\Users\suraj\M103>cd m103-vagrant-env

C:\Users\suraj\M103\m103-vagrant-env>vagrant up --provision
Bringing machine ‘mongod-m103’ up with ‘virtualbox’ provider…
==> 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”, “f18f09aa-c58f-44c7-8579-627f1b27e6b4”, “–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


Please check our forum threads.Multiple threads on vagrant up issues

Error when running Vagrant Up

Hi @pushpak_pattewar,

As I can see, you have completed the Lab: Setting Up the Vagrant Environment. Please confirm that your issue has been resolved so that I can close this thread.

Shubham Ranjan
Curriculum Support Engineer

Yes i have completed …virtualisation was not enabled …provisioning worked after enabling

Closing this thread as the issue has been resolved.