Vagrant with Virtualbox 5.2.2

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Vagrant with Virtualbox 5.2.2

Carlos Morales
Hello,

I have Vagrant 2.0.1 and Virtualbox 5.2.2 and I have this mistake:

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

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

==> default: A newer version of the box 'ubuntu/xenial64' is available! You currently

==> default: have version '20171109.0.0'. The latest is version '20171201.0.0'. Run

==> default: `vagrant box update` to update.

==> 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: 80 (guest) => 8080 (host) (adapter 1)

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", "4942eee0-9109-4694-8aa4-c414453ebc34", "--type", "headless"]

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

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


What can I do?, with the previous virtualbox I could work but now nothing.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/937b7642-264b-4752-a26b-753520b43f9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Vagrant with Virtualbox 5.2.2

Alvaro Miranda Aguilera
Hello Carlos

Please try with Virtualbox 5.1.30


5.2 is not ready yet.

Thanks
Alvaro

On Sun, Dec 3, 2017 at 12:07 PM, Carlos Morales <[hidden email]> wrote:
Hello,

I have Vagrant 2.0.1 and Virtualbox 5.2.2 and I have this mistake:

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

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

==> default: A newer version of the box 'ubuntu/xenial64' is available! You currently

==> default: have version '20171109.0.0'. The latest is version '20171201.0.0'. Run

==> default: `vagrant box update` to update.

==> 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: 80 (guest) => 8080 (host) (adapter 1)

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", "4942eee0-9109-4694-8aa4-c414453ebc34", "--type", "headless"]

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

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


What can I do?, with the previous virtualbox I could work but now nothing.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/937b7642-264b-4752-a26b-753520b43f9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyzkmitzMVuxxLi5o6Swri1z9GcEm_NTewFbEmUpzx6oQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.