try a different box. hashicorp/precise64
do yo have that private key? On Mon, Dec 11, 2017 at 5:52 AM, CodeLyfe <[email protected]> wrote: > My host is Windows 10 Home. (Fall Creators Update) > > When I run the `vagrant up` command I either can't get vagrant to boot > into the machine or if it does eventually succeed and boot it takes 15 > minutes or more to do so. > > What can I do to fix this and have Vagrant & Virtualbox working together > properly. > > Virtualbox version: 5.2.2 > Vagrant version: 2.0.1 > > My box is just an Ubuntu 14.04 box for Ruby on Rails development. It works > fine on other systems, (Mac, Linux). > > So far I've tried disabling the Firewall as well as disabling & enabling > the Virtualbox Host-Only adapter. > > I have set vgui = true so I can see what is going on inside the VM. > > In the VM it tries to find the network device, then retries again after 10 > seconds, then again after 120 seconds. Then it "gave up" looking for the > network device and runs an init. The network device appears immediately > after the init. Then it spends about 5 minutes configuring the network > interfaces. When it completed it booted into Ubuntu with a login prompt. > > Once the login prompt is shown, Vagrant stops retrying and shows Machine > booted and ready. It then took another 10 minutes configuring and enabling > network interfaces, then finally mounts the shared folder and gives me a > command prompt. > > When it fails I get what you see below. > > Any help will be greatly appreciated! > > This is what I get when I run `vagrant up`: > > λ vagrant up > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'dev_box'... > ==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: Dev_default_1512943736797_96012 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: bridged > ==> default: Forwarding ports... > default: 3000 (guest) => 3000 (host) (adapter 1) > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> 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 aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Remote connection disconnect. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > The guest machine entered an invalid state while waiting for it > to boot. Valid states are 'starting, running'. The machine is in the > 'unknown' state. Please verify everything is configured > properly and try again. > > If the provider you're using has a GUI that comes with it, > it is often helpful to open that and watch the machine, since the > GUI often has more helpful error messages than Vagrant can retrieve. > For example, if you're using VirtualBox, run `vagrant up` while the > VirtualBox GUI is open. > > The primary issue for this error is that the provider you're using > is not properly configured. This is very rarely a Vagrant issue. > > -- > 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/eea05fbb-4678-46c8-adc8-b7a83bb24b21%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/eea05fbb-4678-46c8-adc8-b7a83bb24b21%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Alvaro -- 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/CAHqq0ey%2Bj58ZYE6e5WqNjwDN3RiG-HLdvk%2B9TAvae9vEk5MK8Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
