My current solution is to do vagrant reload, then watch the VM console and after it booted, but before vagrant gives up, do 'sudo ifdown eth0 & sudo ifup eth0' after that, vagrant picks the machine and finishes fine. this is of course a lengthy process.
I made sure again that there is no eth0 in /etc/network/interfaces and just one file in /etc/network/interfaces.d. The file is eth0 and its contents are: auto eth0 iface eth0 inet dhcp On Tuesday, October 20, 2015 at 8:40:34 AM UTC+3, Ittay Dror wrote: > > BTW, I have VirtualBox 5.0.6 > > On Tuesday, October 20, 2015 at 8:13:44 AM UTC+3, Ittay Dror wrote: >> >> After doing vagrant reload, the VM boots without networking (the icon is >> in the connected state). >> >> On Tuesday, October 20, 2015 at 8:10:43 AM UTC+3, Ittay Dror wrote: >>> >>> While rebooting the VM, I noticed that Devices->Network->Connect Network >>> Adapter was in an open state (at least I think it was, I clicked a few >>> times before realizing the caption 'connect network adapter' never changes, >>> but the icon does). >>> >>> So I rebooted again, making sure the icon is in the connected state and >>> the machine loaded with networking. >>> >>> On Tuesday, October 20, 2015 at 8:06:03 AM UTC+3, Ittay Dror wrote: >>>> >>>> I started using the VM again and have the same problem. Resetting the >>>> windows networking didn't help nor did adding a NAT adapter to VirtualBox. >>>> I'm using vagrant 1.7.4 now. >>>> >>>> Trying to reload did not solve the issue. >>>> >>>> Rebooting from the machines console doesn't solve the issue either.... >>>> >>>> I'm at home now, with only wifi, at work I have cable network. Maybe >>>> this has something to do with it? >>>> >>>> Regards, >>>> Ittay >>>> >>>> On Friday, August 7, 2015 at 7:04:05 PM UTC+3, dragon788 wrote: >>>>> >>>>> Reload is simply a reboot, it doesn't re-run provisioning or anything. >>>>> >>>>> On Thursday, August 6, 2015 at 7:35:59 AM UTC-5, Ittay Dror wrote: >>>>>> >>>>>> The machine is already in a healthy state, so I don't want to try >>>>>> reload for rear it may cause problems >>>>>> >>>>>> >>>>>> On Thu, Aug 6, 2015 at 2:19 PM Alvaro Miranda Aguilera < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> after you do a vagrant reload it should put the virtual machine back >>>>>>> into a healthy state >>>>>>> >>>>>>> Can you test that? >>>>>>> >>>>>>> Thanks >>>>>>> Alvaro >>>>>>> >>>>>>> On Thu, Aug 6, 2015 at 8:57 PM, Ittay Dror <[email protected]> >>>>>>> wrote: >>>>>>> > So due to another problem I reset my TCP stack >>>>>>> > (https://iihelp.iinet.net.au/Resetting_TCP/IP_to_Default). Now >>>>>>> when I boot >>>>>>> > the VM it has networking from the first boot. Not sure if this >>>>>>> actually >>>>>>> > solved the problem or not (I didn't boot, saw no networking, reset >>>>>>> and then >>>>>>> > saw there was, so something else might have solved it) >>>>>>> > >>>>>>> > >>>>>>> > -- >>>>>>> > This mailing list is governed under the HashiCorp Community >>>>>>> Guidelines - >>>>>>> > https://www.hashicorp.com/community-guidelines.html. Behavior in >>>>>>> violation >>>>>>> > of those guidelines may result in your removal from this mailing >>>>>>> list. >>>>>>> > >>>>>>> > GitHub Issues: https://github.com/mitchellh/vagrant/issues >>>>>>> > IRC: #vagrant on Freenode >>>>>>> > --- >>>>>>> > 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]. >>>>>>> > To view this discussion on the web visit >>>>>>> > >>>>>>> https://groups.google.com/d/msgid/vagrant-up/14f97cfc-a4db-4167-a27a-5390d5cad4df%40googlegroups.com >>>>>>> . >>>>>>> > For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>>> -- >>>>>>> This mailing list is governed under the HashiCorp Community >>>>>>> Guidelines - https://www.hashicorp.com/community-guidelines.html. >>>>>>> Behavior in violation of those guidelines may result in your removal >>>>>>> from >>>>>>> this mailing list. >>>>>>> >>>>>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues >>>>>>> IRC: #vagrant on Freenode >>>>>>> --- >>>>>>> You received this message because you are subscribed to a topic in >>>>>>> the Google Groups "Vagrant" group. >>>>>>> To unsubscribe from this topic, visit >>>>>>> https://groups.google.com/d/topic/vagrant-up/kjvUllcx34M/unsubscribe >>>>>>> . >>>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>>> [email protected]. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyQjXSkzRXG3Z%2BhkcCVnZhFUwa41kTYedVLPWbS9Udjdg%40mail.gmail.com >>>>>>> . >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> -- >>>>>> >>>>>> Sent from my Android >>>>>> >>>>> -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/d23ac4ab-a004-4981-9cdf-8cc6aff5499f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
