Re: Vagrant debian/jessie64 8.6.0 not bootable any more
Le 21/09/2016 à 15:31, Łukasz Zaremba a écrit :
> On 21/09/16 14:58, Marcin Kulisz wrote:
>> I think I had something similar. In my case box it self was up but
>> vagrant
>> couldn't connect to ssh. When I manually connected with just:
>> 'ssh -p [port] -i ~/.vagrant.d/insecure_private_key vagrant@localhost`
>> it was
>> working. Looks like in your case port is 2200 so try it.
>>
>> Once connected all was working but as I'm not using vagrant any more
>> I'm not
>> sure if the above still apply.
>
> Hello Marcin!
> Thank you for your help. I've checked the command and had no success.
>
> I used VirtualBox UI to connect to "local" desktop of VM and logged with
> vagrant/vagrant credentials and saw that machine is left without address
> on eth0.
>
> Now, changelog of debian/jessie64 box says*:
> "do not add vagrant insecure key for root user (closes: #831302)"
>
> So I'm assuming that Vagrant does some administrative tasks on root@
> account to provision the VM and last change broke things for Vagrant.
>
> Normal vagrant up log looks like following (box version 8.5.2):
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default:
> default: Vagrant insecure key detected. Vagrant will automatically
> replace
> default: this with a newly generated keypair for better security.
> default:
> default: Inserting generated public key within guest...
> default: Removing insecure key from the guest if it's present...
> default: Key inserted! Disconnecting and reconnecting using new SSH
> key...
> ==> default: Machine booted and ready!
>
> Here we have (box version 8.6.0):
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> 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.
>
> and machine is left without IP address on eth0.
>
> * Source: https://atlas.hashicorp.com/debian/boxes/jessie64
can you login in the box via VirtualGui as vagrant user ( pw vagrant )
then do as root
echo "pre-up sleep 2" >> /etc/network/interfaces
shutdown the machine
and see if "vagrant up" this time works
Reply to: