My vagrant boxes are no longer accessible.

[Joris Mulliez]

Hi all,

I'm using vagrant for 5 months and I never had problems until now.
I didn't change my vagrant configuration.

And the result is that my boxes are no longer accessible by ssh.

If I try a fresh box intallation :

$ vagrant init michaelward82/trusty64-php7
$ vagrant up

The result is  :

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'michaelward82/trusty64-php7'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'michaelward82/trusty64-php7' is up to date...
==> default: Setting the name of the VM: test_vagrant_default_1480861619865_57514
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

I can't figure how to solve this annoying problem...
 

Any help would be appreciated,

Thanks,

[Joris Mulliez]

I forgot to provide system informations :

I'm running vagrant 1.9, virtualbox 5.1.10 under linux mint 17.1

[Alvaro Miranda Aguilera]

can you test a different box ?

hashicorp/precise64

if still fail, can you test vagrant 1.8.6 ?

On Sun, Dec 4, 2016 at 3:42 PM, Joris Mulliez <joris....@gmail.com> wrote:

I forgot to provide system informations :

I'm running vagrant 1.9, virtualbox 5.1.10 under linux mint 17.1

--
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/1ffbd6e0-8497-4462-b9c3-9f72d57d179c%40googlegroups.com.

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

--

Alvaro

[Joris Mulliez]

Hi Alvaro,

Thanks for your reply.

I just try the "precise64" box, and i've got an error :

$ vagrant up

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

==> default: Box 'hashicorp/precise64' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'hashicorp/precise64'
    default: URL: https://atlas.hashicorp.com/hashicorp/precise64
==> default: Adding box 'hashicorp/precise64' (v1.1.0) for provider: virtualbox
    default: Downloading: https://atlas.hashicorp.com/hashicorp/boxes/precise64/versions/1.1.0/providers/virtualbox.box
==> default: Successfully added box 'hashicorp/precise64' (v1.1.0) for 'virtualbox'!
==> default: Importing base box 'hashicorp/precise64'...

==> default: Matching MAC address for NAT networking...

==> default: Checking if box 'hashicorp/precise64' is up to date...
==> default: Setting the name of the VM: test_vagrant_default_1480886295616_60136

==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2200 (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", "9c49521e-3d45-405c-ab19-64c3cd7e5cf9", "--type", "headless"]

Stderr: VBoxManage: error: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

So there is probably a problem with virtualization and my BIOS, but the problem wasn't there some days ago... and I don't remember any modifications made by myself at this point.

About the "vagrant version" : I was with an older vagrant version this morning (1.8.*), and I update Virtualbox and vagrant in order to try to resolve this connection problem.

Thanks again for your help !

Le dimanche 4 décembre 2016 18:17:18 UTC+1, Alvaro Miranda Aguilera a écrit :

can you test a different box ?

hashicorp/precise64

if still fail, can you test vagrant 1.8.6 ?

On Sun, Dec 4, 2016 at 3:42 PM, Joris Mulliez <joris....@gmail.com> wrote:

I forgot to provide system informations :

I'm running vagrant 1.9, virtualbox 5.1.10 under linux mint 17.1

--
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/1ffbd6e0-8497-4462-b9c3-9f72d57d179c%40googlegroups.com.

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

--

Alvaro

[Alvaro Miranda Aguilera]

On Sun, Dec 4, 2016 at 10:28 PM, Joris Mulliez <joris....@gmail.com> wrote:

is disabled in the BIOS for all CPU mode

Hello.

Correct, the VT-x is a error that presents sometimes.

If you have updated Virtualbox, I would suggest reinstall, and check the BIOS still have the option enabled.

I have a dell xps 15, and I update BIOS quite often, one of those updates, did require enable the option again.

Hopefully you are close to get this working.

Alvaro.

--

Alvaro

[Joris Mulliez]

Yeehaa !

I've enabled VT-x support in my bios, and it seems to be ok for now...
but I'm not convinced that it was the problem on my own box.... because I've never seen the "vt-x" error on it.
This error appears only with the "hashicorp/precise64" box...

Anyway... that works now, it's the most important :)

Thanks for your help Alvaro,

[Alvaro Miranda Aguilera]

vt-x is needed for 64 bit guest.

if your box or other you use were 32bit, then they should run fine.

--
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/6d3b0db7-b63c-41ed-96af-2decf59060a0%40googlegroups.com.

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

--

Alvaro