Re: [vagrant-up] change nic name ?

2017-12-03 Thread Alvaro Miranda Aguilera 
if you disable the new predictable naming you can end with eth0/eth1 etc

you may need to repackage the box or create one from iso.

check about net.ifnames=0 on boot kernel parameter.



On Sun, Dec 3, 2017 at 9:40 PM, Mathew Abraham 
wrote:

> Hi Alvaro,
>>
>
> Thanks, I was trying to keep the  nic name same for all the developers as
> my Ansible job configure the VM system  based on the nic name provided. If
> it differs for each VM then I have to make is as a parameter via data vars.
> I was just trying to reduce that parameter if possible.
>
> Thanks,
> Mathew
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/0274468b-314c-4de3-b5ff-a1ec1c9bafdc%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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyvj93mefZH4yQYeFwCOdhgArBQROhR15HOid71rkcr2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] change nic name ?

2017-12-03 Thread Mathew Abraham 

>
> Hi Alvaro,
>

Thanks, I was trying to keep the  nic name same for all the developers as 
my Ansible job configure the VM system  based on the nic name provided. If 
it differs for each VM then I have to make is as a parameter via data vars. 
I was just trying to reduce that parameter if possible.

Thanks,
Mathew

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/0274468b-314c-4de3-b5ff-a1ec1c9bafdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Downloading boxes from atlas.hashicorp.com is very slow

2017-12-03 Thread Christopher Carr 
Ah, OK. Thanks. 

I shall redirect my complaints. 

On Sunday, December 3, 2017 at 3:38:07 AM UTC-8, Alvaro Miranda Aguilera 
wrote:
>
> Hello
>
> that box is externally hosted, so you should contact canonical. Is not 
> hosted in vagrant cloud/hashicorp
>
> the box is a redirect from:
>
> Location: 
> https://app.vagrantup.com/ubuntu/boxes/trusty64/versions/20171128.0.0/providers/virtualbox.box
>
>
> to:
>
>
> Location: 
> http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box
>
>
>
> virtualbox Externally hosted (cloud-images.ubuntu.com)
>
>
>
> On Sun, Dec 3, 2017 at 7:23 AM, Christopher Carr <
> christop...@pdxwebguy.com > wrote:
>
>> This seems to still be a frequent problem 3 years later. I'm not getting 
>> over 200Kb/s downloading 
>> https://vagrantcloud.com/ubuntu/boxes/trusty64/versions/20171128.0.0/providers/virtualbox.box
>>
>> Run into a bandwidth limit and being throttled, or something? Shouldn't 
>> have to wait 90+ minutes after 'vagrant up'.
>>
>> On Wednesday, December 17, 2014 at 2:45:15 PM UTC-8, Mitchell Hashimoto 
>> wrote:
>>>
>>> Frank, 
>>>
>>> The location of these boxes hasn't changed in nearly a year. I'd say 
>>> that this is probably just due to transient issues. 
>>>
>>> Best, 
>>> Mitchell
>>>
>>> On Wed, Dec 17, 2014 at 2:43 PM, Frank Patz-Brockmann 
>>>  wrote: 
>>> > After month I've returned to using vagrant and find downloading base 
>>> boxes 
>>> > like hashicorp/precise32 extremely slow. 
>>> > It literally takes hours, where it took just minutes a while ago. I am 
>>> sure 
>>> > it's not my internet connection, other downloads 
>>> > work as expected. Is there some bandwidth throttling at work? Waiting 
>>> hours 
>>> > makes "Getting Started" really hard ... 
>>> > 
>>> > -- 
>>> > 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. 
>>> > For more options, visit https://groups.google.com/d/optout. 
>>>
>> -- 
>> 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/27447da2-643e-4682-add0-25e330b91d39%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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/129ef0f8-c0be-442d-a597-5f72d34df837%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] dynamically change the sshd port in guest

2017-12-03 Thread Alvaro Miranda Aguilera 
hello

vagrant expect the ssh to be in the port 22
I think you better using an intermediate tool to do that changes before
vagrant.

if you are using virtualbox, have a look at packer virtualbox-ovf

that can start from an existing vm, however change the port yes may work,
you build them in 2 steps.

step 1, from existing vm with sshd on port 22, change it to 222, poweroff
step 2, existing vm with sshd on port 222 install the app that uses port
22, poweroff create vagrant box with vagrant file that says use port 222


but in all is not a normal use case for vagrant, so i think the best is to
build boxes that are ready to use for vagrant.

you can use packer to build from an iso, so there are options.

for vagrant itself i think is a bit hard

Alvaro.

On Sat, Dec 2, 2017 at 11:03 PM, Marcin Dulak 
wrote:

> 1. I have an official box that uses sshd on port 22, that could be
> https://app.vagrantup.com/centos/ https://app.vagrantup.com/fedora/
> https://app.vagrantup.com/ubuntu, anything
> 2. I start guest using that box with Vagrant and reconfigure sshd on the
> guest to listen on a different port (222). This is for example due to
> starting another service on port 22 on the guest. The new service on port
> 22 does not need to exposed to the Vagrant host.
> 3. I want now Vagrant to know about this change after I reload the same
> box, by passing environment variables to Vagrantfile or some other way
> 4. After creating a set of scripts that configure my box (ansible, puppet,
> docker, ...) this way, I can now use them on a physical host, VM not
> managed by Vagrant, or a VM managed by Vagrant, all having sshd on port 222
>
> I think I'm clear enough, if not try my Vagrantfile.
>
> Best regards,
>
> Marcin
>
> On Saturday, December 2, 2017 at 4:41:37 PM UTC+1, Alvaro Miranda Aguilera
> wrote:
>>
>> Vagrant will create a local port say on  for the first box
>>
>> When tries for the 2nd port, will try  used? Then 2223 or other
>>
>> So still not clear whats the benefit or requirement on doing this.
>>
>> Is this really needed? Why?
>>
>> And what are those boxes you mention?
>>
>> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/23c69ff1-0157-419d-b548-fddabaa2b876%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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0exkaJcpJJ2hfw6rBVeM5GBzm%2BruszBXPKENaE3DXBYE3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Downloading boxes from atlas.hashicorp.com is very slow

2017-12-03 Thread Alvaro Miranda Aguilera 
Hello

that box is externally hosted, so you should contact canonical. Is not
hosted in vagrant cloud/hashicorp

the box is a redirect from:

Location:
https://app.vagrantup.com/ubuntu/boxes/trusty64/versions/20171128.0.0/providers/virtualbox.box


to:


Location:
http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box



virtualbox Externally hosted (cloud-images.ubuntu.com)



On Sun, Dec 3, 2017 at 7:23 AM, Christopher Carr <
christopher.c...@pdxwebguy.com> wrote:

> This seems to still be a frequent problem 3 years later. I'm not getting
> over 200Kb/s downloading https://vagrantcloud.com/ubuntu/boxes/trusty64/
> versions/20171128.0.0/providers/virtualbox.box
>
> Run into a bandwidth limit and being throttled, or something? Shouldn't
> have to wait 90+ minutes after 'vagrant up'.
>
> On Wednesday, December 17, 2014 at 2:45:15 PM UTC-8, Mitchell Hashimoto
> wrote:
>>
>> Frank,
>>
>> The location of these boxes hasn't changed in nearly a year. I'd say
>> that this is probably just due to transient issues.
>>
>> Best,
>> Mitchell
>>
>> On Wed, Dec 17, 2014 at 2:43 PM, Frank Patz-Brockmann
>>  wrote:
>> > After month I've returned to using vagrant and find downloading base
>> boxes
>> > like hashicorp/precise32 extremely slow.
>> > It literally takes hours, where it took just minutes a while ago. I am
>> sure
>> > it's not my internet connection, other downloads
>> > work as expected. Is there some bandwidth throttling at work? Waiting
>> hours
>> > makes "Getting Started" really hard ...
>> >
>> > --
>> > 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.
>> > For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/27447da2-643e-4682-add0-25e330b91d39%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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0exBopJP-s%3DefcUfrjO1RcHLH5eQh9hFVvht0sCVvhL9iA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] rdp for remote vagrant?

2017-12-03 Thread Alvaro Miranda Aguilera 
Hello

vbox extension on the host need to be installed.

this works for me:

Vagrant.configure("2") do |config|

  config.vm.box = "hashicorp/precise64"

  config.vm.provider "virtualbox" do |v|

v.customize ["modifyvm", :id, "--vrde", "on"]

v.customize ["modifyvm", :id, "--vrdeport", "3389-3389"]

  end

end


no need to ssh into the VM if you have direct access, just rdp to the
hostip:port

enjoy!
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eysSSY-cQd0PoBrafAAYc9dN88eNU-ZAr4kvxXfXihKVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] New Vagrant Setup

2017-12-03 Thread Alvaro Miranda Aguilera 
Hello

At some point you or someone did configure a proxy in the machine you are
using.

I don't have all the information.

usually is a variable like

http_proxy=
https_proxy=

the value to test:

http://connsvr.abcdcom:8080 

On Sun, Dec 3, 2017 at 5:41 AM, Rajasekhar Reddy 
wrote:

> can you tell me how do i do that ?
>
> On Sat, Dec 2, 2017 at 7:39 AM, Alvaro Miranda Aguilera  > wrote:
>
>> Hello
>>
>> Here is the error:
>> URL: ["https://vagrantcloud.com/nrel/CentOS-6.5-x86_64;]
>> Error: Unsupported proxy 'https://connsvr.abcdcom:8080', libcurl is
>> built without the HTTPS-proxy support.
>>
>> Can you try to set the proxy var to be http instead of https ?
>>
>> Alvaro.
>>
>>
>> On 1 Dec 2017, at 21:18, Rajasekhar Reddy Anumula 
>> wrote:
>>
>> URL: ["https://vagrantcloud.com/nrel/CentOS-6.5-x86_64;]
>> Error: Unsupported proxy 'https://connsvr.abcdcom:8080', libcurl is
>> built without the HTTPS-proxy support.
>>
>>
>> --
>> 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 a topic in the
>> Google Groups "Vagrant" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/vagrant-up/TXWsPecleII/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> vagrant-up+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/vagrant-up/746A2BC3-BD36-41C4-96CC-F4B8DE137965%40gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Cheers,
>
> Rajasekhar Reddy.A
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/CACYbpTm3p9VA2%3DQyJ6wfxQGWRePvu-
> dMBQgEvF5Wnk9%3Dpn3a5w%40mail.gmail.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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewh-ibYi84jTueJgT6VRg7EVf%3DiZjmkYh%2BSkW0uqwzDVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant with Virtualbox 5.2.2

2017-12-03 Thread 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 <
carlosmoralesdi...@gmail.com> 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) =>  (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_15105
> 57259464_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 vagrant-up+unsubscr...@googlegroups.com.
> 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 vagrant-up+unsubscr...@googlegroups.com.
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.

[vagrant-up] Vagrant with Virtualbox 5.2.2

2017-12-03 Thread 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) =>  (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 vagrant-up+unsubscr...@googlegroups.com.
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.