Vagrant was unable to communicate with the guest machine

[sushi takashi]

Hello,

Sorry for my English I'm not a native speaker.

I'm begginner in vagrant and I get a error when i lauch my VM with ''vagrant up''.

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. This can
mean a number of things.

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.

My host is Windows 7 64bits and my guest is Ubuntu 12.04 64 bits. (I use this box: http://files.vagrantup.com/precise64.box ) and my VirtualBox version is 4.3.6.

I've not problem to access at my VM with SSH but i can't use my sync folder.

[Bogdan Bezuz]

Do you use any kind of provisioning ? It might be the case when the machine waits some input from you (while booting with vagrant) ...like doing apt-get upgrade or such.

--
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/groups/opt_out.

[Rich Burroughs]

Yeah it's odd to me that SSH would work when you get that error. When that's happened to me it's been network problems where Vagrant couldn't connect to sshd.

I'd try turning on the debug log if you haven't:

http://docs.vagrantup.com/v2/other/debugging.html

Rich

[sushi takashi]

Ok, thanks for your answer.

Now, when i lauch "vagrant up", the program block in this step:

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] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
DL is deprecated, please use Fiddle

I enter Ctrl-C and the program return this:

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/ui.rb:184:in `
synchronize': can't be called from trap context (ThreadError)
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u
i.rb:184:in `say'
        from (eval):3:in `warn'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u
i.rb:215:in `block (2 levels) in <class:BasicScope>'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a
ction/runner.rb:62:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u
til/busy.rb:49:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u
til/busy.rb:49:in `block in fire_callbacks'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u
til/busy.rb:49:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u
til/busy.rb:49:in `fire_callbacks'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u
til/busy.rb:33:in `block (2 levels) in register'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/b
atch_action.rb:76:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/b
atch_action.rb:76:in `join'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/b
atch_action.rb:76:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/b
atch_action.rb:53:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/b
atch_action.rb:53:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/e
nvironment.rb:213:in `block (2 levels) in batch'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/e
nvironment.rb:208:in `tap'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/e
nvironment.rb:208:in `block in batch'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/e
nvironment.rb:207:in `synchronize'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/e
nvironment.rb:207:in `batch'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/comma
nds/up/command.rb:55:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/c
li.rb:38:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/e
nvironment.rb:484:in `cli'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/bin/vagrant:1
27:in `<top (required)>'
        from C:/HashiCorp/Vagrant/bin//../embedded/../embedded/gems/bin/vagrant:
23:in `load'
        from C:/HashiCorp/Vagrant/bin//../embedded/../embedded/gems/bin/vagrant:
23:in `<main>'


I use a shell script for provisioning but for the test I comment my vagrant file for just lauch and use my sync folder.

[sushi takashi]

Le vendredi 27 décembre 2013 01:13:04 UTC-5, sushi takashi a écrit :

I set VAGRANT_LOG at debug and I join a file with the error list that return vagrant up,

[sushi takashi]

I destroy my VM and I remove my vagrantfile and I create a new vagrantFile with "vagrant init".

After to edite VagrantFile, I do a vagrant up and its work. I use the default sync folder.

So the problem is done...