Vagrant Up Fails

MongoDB University M310: MongoDB Security
#1

Virtual Box 6.0 Mini-GW Installation Manager and Vagrant all installed.
Vagrant-vbguest installed.
Vagrant Up - Fails, Trace is shown below.
Ideas?
:
Bringing machine ‘database’ up with ‘virtualbox’ provider…
Bringing machine ‘infrastructure’ up with ‘virtualbox’ provider…
==> database: Checking if box ‘ubuntu/trusty64’ version ‘20190206.0.0’ is up to date…
==> database: Clearing any previously set forwarded ports…
==> database: Clearing any previously set network interfaces…
==> database: Preparing network interfaces based on configuration…
database: Adapter 1: nat
database: Adapter 2: hostonly
==> database: Forwarding ports…
database: 22 (guest) => 2222 (host) (adapter 1)
==> database: Running ‘pre-boot’ VM customizations…
==> database: 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”, “72955bd7-93c5-4530-93a4-4478e082bd15”, “–type”, “headless”]

Stderr: VBoxManage.exe: error: The virtual machine ‘m310-vagrant-env_database_1550200169214_6716’ has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in ‘C:\Users\trrei\VirtualBox VMs\m310-vagrant-env_database_1550200169214_6716\Logs\VBoxHardening.log’
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
.

#2

Could you please verify that:

  • In the BIOS of your system, vt-x is ENabled
  • If you’re on Windows, that Hyper-V is DISabled.
#3

vt-x is Enabled
Hyper-V is disabled.

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

Command: [“startvm”, “09c3e913-fe18-4ed9-860e-e518a8cb2340”, “–type”, “headless”]

Stderr: VBoxManage.exe: error: The virtual machine ‘m310-vagrant-env_database_1550206297327_19845’ has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in ‘C:\Users\trrei\VirtualBox VMs\m310-vagrant-env_database_1550206297327_19845\Logs\VBoxHardening.log’
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

1 Like
#4

@ Ted_63853

Unfortunately errors like this are pretty local to your system and setup, so it’s hard to give any real help. Did you check the log as indicated? From your reply, my understanding is that you’re running Windows, which does seem to be a sensitive OS for these VMs. I’d try bringing up the VMs individually, starting with ‘infrastructure’ and also looking at your Oracle VM Virtualbox console. Good luck,

#5

Thanks.
I tend to agree.
I have used Virtual Box before without issue.

#6

I build the database in Hyper V (adjusting the vagrant files).
Then I got fed up. Turned off Hyper-V and put back virtual box.
Everything works now. Vagrant came up fine.

Thanks everyone.

1 Like
#7