Vagrant up database failed

C:\Users\josef_000\Downloads\m310-vagrant-env>vagrant up database
Bringing machine ‘database’ up with ‘virtualbox’ provider…
==> database: Box ‘ubuntu/trusty64’ could not be found. Attempting to find and install…
database: Box Provider: virtualbox
database: Box Version: >= 0
==> database: Loading metadata for box ‘ubuntu/trusty64’
database: URL: https://vagrantcloud.com/ubuntu/trusty64
==> database: Adding box ‘ubuntu/trusty64’ (v20190514.0.0) for provider: virtualbox
database: Downloading: https://vagrantcloud.com/ubuntu/boxes/trusty64/versions/20190514.0.0/providers/virtualbox.box
database: Download redirected to host: cloud-images.ubuntu.com
database:
==> database: Successfully added box ‘ubuntu/trusty64’ (v20190514.0.0) for ‘virtualbox’!
==> database: Importing base box ‘ubuntu/trusty64’…
==> database: Matching MAC address for NAT networking…
==> database: Checking if box ‘ubuntu/trusty64’ version ‘20190514.0.0’ is up to date…
==> database: Setting the name of the VM: m310-vagrant-env_database_1573749607167_3716
==> database: Clearing any previously set forwarded ports…
Vagrant is currently configured to create VirtualBox synced folders with
the SharedFoldersEnableSymlinksCreate option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:

https://www.virtualbox.org/manual/ch04.html#sharedfolders

This option can be disabled globally with an environment variable:

VAGRANT_DISABLE_VBOXSYMLINKCREATE=1

or on a per folder basis within the Vagrantfile:

config.vm.synced_folder ‘/host/path’, ‘/guest/path’, SharedFoldersEnableSymlinksCreate: false
==> 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”, “416b4e45-78c2-47fb-a43a-68a5ca2f91bd”, “–type”, “headless”]

Stderr: VBoxManage.exe: error: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

C:\Users\josef_000\Downloads\m310-vagrant-env>

What does vagrant status show?

Just run vagrant up

C:\Users\xyz\M310\m310-vagrant-env>vagrant up
Bringing machine ‘database’ up with ‘virtualbox’ provider…
Bringing machine ‘infrastructure’ up with ‘virtualbox’ provider…
==> database: Importing base box ‘ubuntu/trusty64’…

CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

then vagrant up --remove database…

still trying…

before turn on ypervisorlaunchtype, vagrant ssh database does not work.

database: After this operation, 225 MB of additional disk space will be used.
database: WARNING: The following packages cannot be authenticated!
database: mongodb-enterprise-shell mongodb-enterprise-server mongodb-enterprise-mongos
database: mongodb-enterprise-tools mongodb-enterprise
database: E
database: :
database: There are problems and -y was used without --force-yes
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

C:\Users\josef_000\Downloads\m310-vagrant-env>vagrant status
Current machine states:

database running (virtualbox)
infrastructure poweroff (virtualbox)

This environment represents multiple VMs. The VMs are all listed
above with their current state. For more information about a specific
VM, run vagrant status NAME.

C:\Users\josef_000\Downloads\m310-vagrant-env>vagrant ssh database
Welcome to Ubuntu 14.04.6 LTS (GNU/Linux 3.13.0-170-generic x86_64)

System information disabled due to load higher than 1.0

UA Infrastructure Extended Security Maintenance (ESM) is not enabled.

0 updates can be installed immediately.
0 of these updates are security updates.

Enable UA Infrastructure ESM to receive 64 additional security updates.
See https://ubuntu.com/advantage or run: sudo ua status

New release ‘16.04.6 LTS’ available.
Run ‘do-release-upgrade’ to upgrade to it.

vagrant@database:~$

this is really doesn’t make sense.

Why do you want to remove database?
It is up and running and you are able to login to the database box as the prompt shows

Just try to start infrastructure by below command and see if it comes up
vagrant up infrastructure

Course instructors can help more on this

1 Like