Am using Vagrant 1.3.1 but had similar issues before as well.
So if I run Precise 64 as in:
config.vm.box = "precise64"
config.vm.box_url = "http://files.vagrantup.com/precise64.box"
I have no problems with my SQL setups from Salt with MySQL and PostgreSQL.
...
However if I run Raring 64 as in:
config.vm.box = "raring64-ubuntu-13.04LTS"
config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/raring/current/raring-server-cloudimg-amd64-vagrant-disk1.box"
I keep getting this error (mostly), although a few times it has NOT happened:
[dbmsSQL] Waiting for machine to boot. This may take a few minutes...
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.ssh.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.ssh.timeout") value.
...
I try to increase config.vm.timeout to 20 but that parameter is not accepted as saying timeout does not exists.
Any particular reason for this?
Thank you.
Am using Vagrant 1.3.1 but had similar issues before as well.
So if I run Precise 64 as in:
config.vm.box = "precise64"
config.vm.box_url = "http://files.vagrantup.com/precise64.box"
I have no problems with my SQL setups from Salt with MySQL and PostgreSQL.
...
However if I run Raring 64 as in:
config.vm.box = "raring64-ubuntu-13.04LTS"
config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/raring/current/raring-server-cloudimg-amd64-vagrant-disk1.box"
I keep getting this error (mostly), although a few times it has NOT happened:
[dbmsSQL] Waiting for machine to boot. This may take a few minutes...
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.ssh.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.ssh.timeout") value.
...
I try to increase config.vm.timeout to 20 but that parameter is not accepted as saying timeout does not exists.
Any particular reason for this?
Thank you.