Alvaro, Thank you for looking into this. It is a Ubuntu VM, so option B is not possible.
Option A - There is a README file and a 60-vboxadd.rules file in /etc/udev/rules.d. Thank you. Aditya. On Sat, Feb 7, 2015 at 3:11 PM, Alvaro Miranda Aguilera <[email protected]> wrote: > Hello, on that new box try this: > > First . A. > > login from the gui > become root, sudo su - > > go to /etc/udev/rules.d > > do an ls > > if there is any 70-persistent-net.rule or similar delete it > > Then B. > > if the OS is centos or rpm based, try this > > cd /etc/sysconfig/network-scripts/ > edit ifcfg-eth0 or ifcfg-em0 > > if there is anything like MACADDR or UUID delete those lines > > If the directory doesn't exist, skip this part > > reboot and try again > > If that fix the issue, you need to do that manually before packing the box. > > Alvaro. > > > > On Sat, Feb 7, 2015 at 1:33 PM, <[email protected]> wrote: > > This is my first Vagrant box. I have Vagrant 1.7.2 and Virtualbox 4.3.20 > on > > a Windows 7 host. > > > > I used a bitnami box to build my vm without x windows. I followed > > instructions from this link - > > > https://github.com/hollodotme/Helpers/blob/master/Tutorials/vagrant/self-hosted-vagrant-boxes-with-versioning.md > > - to prepare for creating the vagrant box. > > > > I did a vagrant up and I keep getting 'Remote connection disconnect.' I > hit > > ctrl+c and did a 'vagrant halt'. I booted up the new vm from virtualbox > > directly. It gets me to the login prompt. I tried 'vagrant ssh' and I get > > this error: 'ssh_exchange_identification: read: The connection was > aborted'. > > > > I did a 'vagrant destroy and started over. I edited the Vagrantfile to > allow > > GUI to be visible. I am able to get to get to the login prompt in the > VBox > > UI and I still get the 'Remote connection disconnect' on the console. > > > > After this, I upgraded to Vagrant 1.7.2 and the issue is still there. > > > > I found other forum posts in this group about the same error message, but > > none of them seem to have the exact same problem. > > > > $ vagrant up > > Bringing machine 'default' up with 'virtualbox' provider... > > ==> default: Importing base box 'dashing_bitnami'... > > ==> default: Matching MAC address for NAT networking... > > ==> default: Setting the name of the VM: > > VagrantTest_default_1423268267150_49487 > > > > ==> default: Clearing any previously set network interfaces... > > ==> default: Preparing network interfaces based on configuration... > > default: Adapter 1: nat > > ==> default: Forwarding ports... > > default: 22 => 2222 (adapter 1) > > ==> default: Booting VM... > > ==> 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: Warning: Connection timeout. Retrying... > > default: Warning: Remote connection disconnect. Retrying... > > default: Warning: Remote connection disconnect. Retrying... > > default: Warning: Remote connection disconnect. Retrying... > > default: Warning: Remote connection disconnect. Retrying... > > default: Warning: Remote connection disconnect. Retrying... > > default: Warning: Remote connection disconnect. Retrying... > > > > -- > > 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/d/optout. > > -- > 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/bviqvAtHXbw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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/d/optout.
