'vagrant up' is failing with the following errors--how can I troubleshoot?

Carl Gross

unread,

Nov 14, 2017, 12:18:33 PM11/14/17

to Vagrant

Hello. I recently had to re-install many programs on my computer (Win 10, x64), and VirtualBox was one of them. I re-installed without issue, but am now encountering an error when running 'vagrant up' (Vagrant version 1.8.6). The console output is:

$ vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Checking if box 'ubuntu/trusty64' is up to date...

==> default: Clearing any previously set forwarded ports...

==> default: Clearing any previously set network interfaces...

==> default: Preparing network interfaces based on configuration...

default: Adapter 1: nat

default: Adapter 2: hostonly

==> default: Forwarding ports...

default: 22 (guest) => 2222 (host) (adapter 1)

==> default: Running 'pre-boot' VM customizations...

==> default: 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", "09fb1b27-94cb-4eb8-9735-9c0dd82f5b49", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'sites' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\snarl\VirtualBox VMs\sites\Logs\VBoxHardening.log'

VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

Per the suggestion, I opened VBoxHardening.log. The last several lines are as follows:

2950.1f98: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxRT.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]

2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8ab0c0000 'C:\Program Files\Oracle\VirtualBox\VBoxRT.dll'

2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8e68e0000 'C:\WINDOWS\system32\Wintrust.dll'

2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8e4d80000 'C:\WINDOWS\system32\rsaenh.dll'

2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8e5be0000 'C:\WINDOWS\System32\crypt32.dll'

2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8e4d80000 'C:\WINDOWS\system32\rsaenh.dll'

2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8e5be0000 'C:\WINDOWS\System32\crypt32.dll'

2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8e5be0000 'C:\WINDOWS\system32\crypt32.dll'

2950.1f98: Error -1912 in supR3HardenedMainInitRuntime! (enmWhat=4)

2950.1f98: RTR3InitEx failed with rc=-1912

2850.1818: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 504 ms, the end);

a80.26f4: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 929 ms, the end);

Can anyone shed some light on this Error -1912? Do I have any options other than uninstalling/re-installing Vagrant?

Thanks in advance.

Alvaro Miranda Aguilera

unread,

Nov 15, 2017, 3:45:13 AM11/15/17

to vagra...@googlegroups.com

Hello

Try to use Virtualbox gui, and turn on/off/on VMs you see there.

The error is coming from VirtualBox, so Vagrant here is just failing.

If you can skip Vagrant you may find what the issue is.

Which virtualbox version are you using?

Thanks

Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/466114b2-7a6a-41d2-95f4-c16be5c8fcda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

Carl Gross

unread,

Nov 15, 2017, 12:10:17 PM11/15/17

to Vagrant

Thanks for the reply. Here are my replies.

>> Which virtualbox version are you using?

I am using Oracle VM VirtualBox v.5.1.30. As I mentioned, I recently uninstalled/reinstalled.

>> Try to use Virtualbox gui, and turn on/off/on VMs you see there.

OK I've opened my VirtualBox GUI, and there is indeed one VM there. It is the VM I expect to be present (named 'sites'--screenshot). It is powered off. Are you saying I should power it on? If so, then what? Or should I turn it on via the GUI, then try a 'vagrant up?'

Thanks!

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/466114b2-7a6a-41d2-95f4-c16be5c8fcda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Alvaro

Alvaro Miranda Aguilera

unread,

Nov 15, 2017, 5:20:16 PM11/15/17

to vagra...@googlegroups.com

turn it on as a way to test if there i any error from virtualbox.

the gui will possible show something that make more sense than those errors .

Alvaro.

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/742213f8-f887-460b-97de-e4ac9d198cc5%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

Carl Gross

unread,

Nov 16, 2017, 4:37:36 AM11/16/17

to Vagrant

OK I tried it. To be clear, I opened Oracle VM, right clicked on the only virtual machine in the list ("sites"), and clicked "Start." A separate window opened which began to display some text output. But it eventually displayed a login, and I successfully logged in using the credentials:

root

vagrant

It then took me to this prompt. I then exited and powered off the virtual machine.

Thoughts? Should I have conducted some tests from the command prompt? Or should I attempt to find a log of the output displayed during startup?

Thanks!

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/742213f8-f887-460b-97de-e4ac9d198cc5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Alvaro

Reply all

Reply to author

Forward