vagrant JujuBox times out

Bug #1289739 reported by kklepper
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

As given by https://juju.ubuntu.com/docs/config-vagrant.html:

-------------

vagrant box add JujuBox http://cloud-images.ubuntu.com/vagrant/precise/current/precise-server-cloudimg-amd64-juju-vagrant-disk1.box

-------------

Result:

-------------

D:\vagrant\juju>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'JujuBox'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[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] -- 22 => 2122 (adapter 1)
[default] -- 80 => 6080 (adapter 1)
[default] -- 8001 => 8001 (adapter 1)
[default] -- 80 => 8880 (adapter 1)
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
DL is deprecated, please use Fiddle
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.

-------------

config.vm.boot_timeout is set by default to 300. Changing to 600 didn't change anything, as expected, using the 32-bit-version either.

No way to use the box, although it is running:

-------------

D:\vagrant\juju>vagrant ssh
ssh_exchange_identification: Connection closed by remote host

D:\vagrant\juju>vagrant status
Current machine states:

default running (virtualbox)

The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.

Revision history for this message
kklepper (gmcgmx) wrote :

Oh, forgot: Running on XP. Vagrant runs fine otherwise, never had any problem with boxes.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.