Error in executing VBoxManage

[Alex Dahlman]

Hey everyone.  Here is the error I get when trying to up my vagrant.  I've tried the vagrant destroy and then up and still receive this error.

There was an error while executing `VBoxManage`, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "e6cbeecf-93ee-4d27-a8b7-7290356983f4", "--type", "headless"]

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

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

Thanks!

[Alvaro Miranda Aguilera]

hello

try to use virtualbox gui to stop and start manually this box. 

can you start other boxes?

try hashicorp/precise64 to isolate the problem

--
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/665bb3ea-d566-475b-a13b-ad8e77d0f85c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Alex Dahlman]

The gui gives me the same error when trying to start headless: 

The virtual machine 'scotch-box_default_1474998580218_27139' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\adahlman\VirtualBox VMs\scotch-box_default_1474998580218_27139\Logs\VBoxHardening.log'.

Result Code:	E_FAIL (0x80004005)
Component:	MachineWrap
Interface:	IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

Also, no this happens to both boxes.

On Thursday, September 29, 2016 at 10:41:37 AM UTC-6, Alvaro Miranda Aguilera wrote:

hello

try to use virtualbox gui to stop and start manually this box. 

can you start other boxes?

try hashicorp/precise64 to isolate the problem

On Wed, Sep 28, 2016 at 9:26 PM, Alex Dahlman <cstri...@gmail.com> wrote:

Hey everyone.  Here is the error I get when trying to up my vagrant.  I've tried the vagrant destroy and then up and still receive this error.

There was an error while executing `VBoxManage`, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "e6cbeecf-93ee-4d27-a8b7-7290356983f4", "--type", "headless"]

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

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

Thanks!

--
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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/665bb3ea-d566-475b-a13b-ad8e77d0f85c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Alvaro Miranda Aguilera]

try a 32bit OS.

mkdir precise32

cd precise32

vagrant init -m hashicorp/precise32

There is not much info at this moment, but error is coming from Virtualbox.

If the 32bit VM can start, I will suggest check Virtualization VT enabled on bios. Buts strange that the Virtualbox gui is not giving any more insights.

Have you tried to create a VM manually?

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/6c48a7f7-e9b2-4ed7-8e9e-36a312990dac%40googlegroups.com.

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

--

Alvaro