Re: Vagrant debian/jessie64 8.6.0 not bootable any more
Closing this thread with reference to bug that Emmanuel fixed: On 29/09/16 23:33, Emmanuel Kasper wrote: > I've pushed a new box with version 8.6.1 who should fix the bug ( I > tested it in a Virtualbox 5.0.* env and the network works properly) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838999
Re: Vagrant debian/jessie64 8.6.0 not bootable any more
On 09/22/2016 11:42 AM, Łukasz Zaremba wrote: > On 22/09/16 06:55, Emmanuel Kasper wrote: >> I retested the box and it's working here >> so it looks like the embedded Virtualbox DHCP server it not found >> >> can you try an alternative Box ( Centos, Ubuntu ) to see if they get >> network ? > > centos/7 worked after applying config.ssh.insert_key = false > https://github.com/mitchellh/vagrant/issues/7610 > > ubuntu/trusty64 worked out of the box. OK as I cannot reproduce the issue it's going to be difficult to debug can you try to manually request an ip adress on the VM is started ? service networking stop dhclient -r eth0 dhclient eth0
Re: Vagrant debian/jessie64 8.6.0 not bootable any more
On 22/09/16 06:55, Emmanuel Kasper wrote: I retested the box and it's working here so it looks like the embedded Virtualbox DHCP server it not found can you try an alternative Box ( Centos, Ubuntu ) to see if they get network ? centos/7 worked after applying config.ssh.insert_key = false https://github.com/mitchellh/vagrant/issues/7610 ubuntu/trusty64 worked out of the box.
Re: Vagrant debian/jessie64 8.6.0 not bootable any more
Le 21/09/2016 à 21:35, Łukasz Zaremba a écrit :
> On 21/09/16 20:54, Emmanuel Kasper wrote:
>> 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
>
> Hello Emmanuel!
> Unfortunately I have the same result:
>
> $ vagrant up
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Checking if box 'debian/jessie64' is up to date...
> ==> default: Clearing any previously set forwarded ports...
> ==> default: Fixed port collision for 22 => . Now on port 2200.
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> ==> default: Forwarding ports...
> default: 22 (guest) => 2200 (host) (adapter 1)
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2200
> 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.
>
>
> Here is the /etc/network/interfaces file after last command*:
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> source /etc/network/interfaces.d/*
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> allow-hotplug eth0
> iface eth0 inet dhcp
> pre-up sleep 2
>
>
> I also checked the same scenario with auto eth0 instead of allow-hotplug
> eth0 and it didn't change anything.
>
>
> Following this reasoning I also launched /etc/init.d/networking status
> to see:
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
> ..
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
I retested the box and it's working here
so it looks like the embedded Virtualbox DHCP server it not found
can you try an alternative Box ( Centos, Ubuntu ) to see if they get
network ?
Re: Vagrant debian/jessie64 8.6.0 not bootable any more
On 21/09/16 20:54, Emmanuel Kasper wrote:
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
Hello Emmanuel!
Unfortunately I have the same result:
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'debian/jessie64' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => . Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2200
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.
Here is the /etc/network/interfaces file after last command*:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
pre-up sleep 2
I also checked the same scenario with auto eth0 instead of allow-hotplug
eth0 and it didn't change anything.
Following this reasoning I also launched /etc/init.d/networking status
to see:
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
..
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
To be sure that the problem is with this particular 8.6.0 box version I
also tested the same commands as in original thread on another computer
with little older software - OS X El Capitan 10.11.6, VirtualBox 4.3.10
r101610 and Vagrant 1.8.4 - the same result.
* I had to retype the text by hand so hopefully I did that without errors.
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:
> 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:
> 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
Re: Vagrant debian/jessie64 8.6.0 not bootable any more
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:
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:
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
Re: Vagrant debian/jessie64 8.6.0 not bootable any more
On 2016-09-21 14:14:16, Łukasz Zaremba wrote: > Hello! Hi > It seems that starting from 8.6.0 (Vagrant 1.8.5) it is not possible to > start the box: 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. snip -- |_|0|_| | |_|_|0| "Panta rei" | |0|0|0| kuLa | gpg --keyserver pgp.mit.edu --recv-keys 0x686930DD58C338B3 3DF1 A4DF C732 4688 38BC F121 6869 30DD 58C3 38B3 signature.asc Description: PGP signature
