Alistair, does "vagrant ssh" work fine even though it can't connect on "up"? Have you tried launching with a GUI and logging in via the console and poking around?
On Fri, Jan 10, 2014 at 4:39 AM, <[email protected]> wrote: > I've been using vagrant 1.0.x with a .vagrant file but after upgrading to > vagrant 1.4.2 and VirtualBox 4.3.6 I get weird behaviour. I've converted > .vagrantfile to .vagrant/machines/ltkdev/virtualbox and added an id file. > The behaviour is: > > this works first time: > vagrant up > vagrant ssh > exit > vagrant halt > > doing it again, the box is unreachable: > > INFO retryable: Retryable exception raised: #<Timeout::Error: execution > expired> > INFO ssh: Attempting to connect to SSH... > INFO ssh: - Host: 127.0.0.1 > INFO ssh: - Port: 2222 > INFO ssh: - Username: vagrant > INFO ssh: - Key Path: > ["/Users/alistair/.vagrant.d/insecure_private_key"] > INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", > "04b46790-6ff6-4c1a-9202-34c2233b7bd1", "--machinereadable"] > > when I look at it in VirtualBox, it's running so I have to shut it down > from VirtualVox as vagrant can't ssh to it > > is there anything that would cause this behaviour? > > thanks, > > Alistair > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
