get error while vagrant up

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

get error while vagrant up

774597851
Dear all,

I got an error while "vagrant up". Before I get back to the office, this works well. I don't know what have happend. I also have tried several answers in google, but they don't work well for me. I'd appreciate if someone could help. Here is the error information:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> 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: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> 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", "f29376ab-db69-4b7e-8895-21394af959a0", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'supersmart_default_1494145933288_33527' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

$ VBoxManage -v
5.1.22r115126
$ vagrant -v
Vagrant 1.9.4
$ cat /proc/version
Linux version 3.10.0-327.el7.x86_64 ([hidden email]) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu Nov 19 22:10:57 UTC 2015

Best Regards
Baolin

--
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/7b2f53ea-fbd6-4eed-a87d-dd51d3e0031b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: get error while vagrant up

Alvaro Miranda Aguilera
Hello

Open Virtualbox GUI and try to poweroff and turn on the box, it may share more information about the error.

It seems Vagrant is doing the right thing, but the error is coming from Virtualbox.

Also, update to latest version is good practice.

Alvaro

On Thu, Jul 27, 2017 at 3:01 PM, <[hidden email]> wrote:
Dear all,

I got an error while "vagrant up". Before I get back to the office, this works well. I don't know what have happend. I also have tried several answers in google, but they don't work well for me. I'd appreciate if someone could help. Here is the error information:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> 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: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> 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", "f29376ab-db69-4b7e-8895-21394af959a0", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'supersmart_default_1494145933288_33527' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

$ VBoxManage -v
5.1.22r115126
$ vagrant -v
Vagrant 1.9.4
$ cat /proc/version
Linux version 3.10.0-327.el7.x86_64 ([hidden email]) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu Nov 19 22:10:57 UTC 2015

Best Regards
Baolin

--
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/7b2f53ea-fbd6-4eed-a87d-dd51d3e0031b%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/CAHqq0ewV50xCJrk0SN9Pi1v-pYzjj9Jv6JbEoxJvvCN%3DAPp9Jg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: get error while vagrant up

774597851
Dear Alvaro,

Thanks for the response. What you said is try this command: VBoxManage startvm 70053a71-dc99-4f4d-a270-1e1aebc96e5a --type gui
If is true, then the same error was get:

Waiting for VM "70053a71-dc99-4f4d-a270-1e1aebc96e5a" to power on...
VBoxManage: error: The virtual machine 'supersmart_default_1501215066529_55213' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

I also tried to destroy and create the box. But they did't work for me. I also tried the following command. It seems like the broken link happened. I didn't try anything beacause I'm afraid I could mess up the system badly. I know little about the linux system.
$ VBoxManage startvm 70053a71-dc99-4f4d-a270-1e1aebc96e5a --type headless
Waiting for VM "70053a71-dc99-4f4d-a270-1e1aebc96e5a" to power on...
VBoxManage: error: The virtual machine 'supersmart_default_1501215066529_55213' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

$ VBoxHeadless 70053a71-dc99-4f4d-a270-1e1aebc96e5a
VBoxHeadless: Error -610 in supR3HardenedMainInitRuntime!
VBoxHeadless: dlopen("/usr/lib/virtualbox/VBoxRT.so",) failed: /lib64/libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

VBoxHeadless: Tip! It may help to reinstall VirtualBox.

#### Note: reinstall the newest VirtualBox don't work!

$ ldd -r /usr/lib/virtualbox/VBoxRT.so
        linux-vdso.so.1 =>  (0x00007ffd70775000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fb6a1c8c000)
        libz.so.1 => /lib64/libz.so.1 (0x00007fb6a1a75000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fb6a1859000)
        librt.so.1 => /lib64/librt.so.1 (0x00007fb6a1651000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fb6a144c000)
        libxml2.so.2 => /lib64/libxml2.so.2 (0x00007fb6a10e2000)
        libcurl.so.4 => /usr/local/lib/libcurl.so.4 (0x00007fb6a0e8e000)
        libssl.so.10 => /lib64/libssl.so.10 (0x00007fb6a0c1f000)
        libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007fb6a0835000)
        libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fb6a052c000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fb6a0315000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fb69ff54000)
        libfreebl3.so => /lib64/libfreebl3.so (0x00007fb69fd51000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fb6a234b000)
        liblzma.so.5 => /lib64/liblzma.so.5 (0x00007fb69fb2a000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fb69f827000)
        libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007fb69f5d9000)
        libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007fb69f2f1000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fb69f0ed000)
        libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007fb69eebb000)
        libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007fb69ecab000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fb69eaa7000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fb69e88d000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fb69e665000)
        libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x00007fb69e43e000)
symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference      (/lib64/libm.so.6)
symbol __strtod_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference       (/lib64/libm.so.6)
symbol __strtof_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference       (/lib64/libm.so.6)

In an another system, these commands work fine.

Do you have any clues? It will be better if you can give any detail commands.

Thanks for the help,

Best regards,
Baolin

在 2017年7月28日星期五 UTC+8上午1:08:20,Alvaro Miranda Aguilera写道:

Hello

Open Virtualbox GUI and try to poweroff and turn on the box, it may share more information about the error.

It seems Vagrant is doing the right thing, but the error is coming from Virtualbox.

Also, update to latest version is good practice.

Alvaro

On Thu, Jul 27, 2017 at 3:01 PM, <<a onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;" href="javascript:" target="_blank" rel="nofollow" gdf-obfuscated-mailto="mYTatWkzAgAJ">7745...@...> wrote:
Dear all,

I got an error while "vagrant up". Before I get back to the office, this works well. I don't know what have happend. I also have tried several answers in google, but they don't work well for me. I'd appreciate if someone could help. Here is the error information:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> 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: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> 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", "f29376ab-db69-4b7e-8895-21394af959a0", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'supersmart_default_1494145933288_33527' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

$ VBoxManage -v
5.1.22r115126
$ vagrant -v
Vagrant 1.9.4
$ cat /proc/version
Linux version 3.10.0-327.el7.x86_64 (<a style="color: rgb(30, 84, 148); text-decoration: underline;" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;" href="javascript:" target="_blank" rel="nofollow" gdf-obfuscated-mailto="mYTatWkzAgAJ">bui...@....org) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu Nov 19 22:10:57 UTC 2015

Best Regards
Baolin

--
This mailing list is governed under the HashiCorp Community Guidelines - <a onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" href="https://www.hashicorp.com/community-guidelines.html" target="_blank" rel="nofollow">https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: <a onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" href="https://github.com/mitchellh/vagrant/issues" target="_blank" rel="nofollow">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 <a onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;" href="javascript:" target="_blank" rel="nofollow" gdf-obfuscated-mailto="mYTatWkzAgAJ">vagrant-up+...@googlegroups.com.
To view this discussion on the web visit <a onmousedown="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/7b2f53ea-fbd6-4eed-a87d-dd51d3e0031b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/7b2f53ea-fbd6-4eed-a87d-dd51d3e0031b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" href="https://groups.google.com/d/msgid/vagrant-up/7b2f53ea-fbd6-4eed-a87d-dd51d3e0031b%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow">https://groups.google.com/d/msgid/vagrant-up/7b2f53ea-fbd6-4eed-a87d-dd51d3e0031b%40googlegroups.com.
For more options, visit <a onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" href="https://groups.google.com/d/optout" target="_blank" rel="nofollow">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/55d7d5f9-b552-4635-bf69-336723252b99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: get error while vagrant up

Alvaro Miranda Aguilera
Hello

Actually my suggestion was to open the virtual box gui.

and stop/start from there

Test that virtualbox work, create vm, put an iso, see if you can get that working.

Vagrant requires virtualbox to be working

check the attachment for what i mean by virtualbox gui





On Fri, Jul 28, 2017 at 11:06 AM, <[hidden email]> wrote:
Dear Alvaro,

Thanks for the response. What you said is try this command: VBoxManage startvm 70053a71-dc99-4f4d-a270-1e1aebc96e5a --type gui
If is true, then the same error was get:

Waiting for VM "70053a71-dc99-4f4d-a270-1e1aebc96e5a" to power on...
VBoxManage: error: The virtual machine 'supersmart_default_1501215066529_55213' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

I also tried to destroy and create the box. But they did't work for me. I also tried the following command. It seems like the broken link happened. I didn't try anything beacause I'm afraid I could mess up the system badly. I know little about the linux system.
$ VBoxManage startvm 70053a71-dc99-4f4d-a270-1e1aebc96e5a --type headless
Waiting for VM "70053a71-dc99-4f4d-a270-1e1aebc96e5a" to power on...
VBoxManage: error: The virtual machine 'supersmart_default_1501215066529_55213' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

$ VBoxHeadless 70053a71-dc99-4f4d-a270-1e1aebc96e5a
VBoxHeadless: Error -610 in supR3HardenedMainInitRuntime!
VBoxHeadless: dlopen("/usr/lib/virtualbox/VBoxRT.so",) failed: /lib64/libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

VBoxHeadless: Tip! It may help to reinstall VirtualBox.

#### Note: reinstall the newest VirtualBox don't work!

$ ldd -r /usr/lib/virtualbox/VBoxRT.so
        linux-vdso.so.1 =>  (0x00007ffd70775000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fb6a1c8c000)
        libz.so.1 => /lib64/libz.so.1 (0x00007fb6a1a75000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fb6a1859000)
        librt.so.1 => /lib64/librt.so.1 (0x00007fb6a1651000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fb6a144c000)
        libxml2.so.2 => /lib64/libxml2.so.2 (0x00007fb6a10e2000)
        libcurl.so.4 => /usr/local/lib/libcurl.so.4 (0x00007fb6a0e8e000)
        libssl.so.10 => /lib64/libssl.so.10 (0x00007fb6a0c1f000)
        libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007fb6a0835000)
        libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fb6a052c000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fb6a0315000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fb69ff54000)
        libfreebl3.so => /lib64/libfreebl3.so (0x00007fb69fd51000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fb6a234b000)
        liblzma.so.5 => /lib64/liblzma.so.5 (0x00007fb69fb2a000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fb69f827000)
        libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007fb69f5d9000)
        libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007fb69f2f1000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fb69f0ed000)
        libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007fb69eebb000)
        libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007fb69ecab000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fb69eaa7000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fb69e88d000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fb69e665000)
        libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x00007fb69e43e000)
symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference      (/lib64/libm.so.6)
symbol __strtod_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference       (/lib64/libm.so.6)
symbol __strtof_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference       (/lib64/libm.so.6)

In an another system, these commands work fine.

Do you have any clues? It will be better if you can give any detail commands.

Thanks for the help,

Best regards,
Baolin

在 2017年7月28日星期五 UTC+8上午1:08:20,Alvaro Miranda Aguilera写道:

Hello

Open Virtualbox GUI and try to poweroff and turn on the box, it may share more information about the error.

It seems Vagrant is doing the right thing, but the error is coming from Virtualbox.

Also, update to latest version is good practice.

Alvaro

On Thu, Jul 27, 2017 at 3:01 PM, <[hidden email]> wrote:
Dear all,

I got an error while "vagrant up". Before I get back to the office, this works well. I don't know what have happend. I also have tried several answers in google, but they don't work well for me. I'd appreciate if someone could help. Here is the error information:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> 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: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> 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", "f29376ab-db69-4b7e-8895-21394af959a0", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'supersmart_default_1494145933288_33527' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

$ VBoxManage -v
5.1.22r115126
$ vagrant -v
Vagrant 1.9.4
$ cat /proc/version
Linux version 3.10.0-327.el7.x86_64 ([hidden email]g) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu Nov 19 22:10:57 UTC 2015

Best Regards
Baolin

--
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/7b2f53ea-fbd6-4eed-a87d-dd51d3e0031b%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/55d7d5f9-b552-4635-bf69-336723252b99%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/CAHqq0exXmwDKqFvT%3DL_-M3dkPuGXj6kQAqohVZ%2Bo9a5TY_m%3Dtw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.