Picture of Michael Horn
Vagrant Up Fail
by Michael Horn - Monday, 3 April 2017, 4:32 AM
 

OS: Widows 7 x64

Trying to install/run Adapt Learning Authoring tool, but I am encountering errors in the 'vagrant up' command.

I have tested this on 2 seperate computers, each displaying that same problem. I have followed the instructions from here and have had 0 luck. I am currently just wanting to see what the framework is like.

I have installed vagrant, virtual box, put the adapt files in a place that doesnt require perms. Anything that I have missed?

Any help would be great to have.

Here is my console output:

C:\Users\mpire\adapt_a>vagrant up

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty32'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/trusty32' is up to date...
==> default: Setting the name of the VM: adapt_a_default_1491193752215_12733
==> default: Clearing any previously set forwarded ports...
==> default: Destroying VM and associated drives...
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_o
pen.rb:21:in 'initialize': The requested address is not valid in its context. -
connect(2) for "0.0.0.0" port 5000 (Errno::EADDRNOTAVAIL)
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/u
til/is_port_open.rb:21:in 'new'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/u
til/is_port_open.rb:21:in 'block in is_port_open?'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in 'bloc
k in timeout'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in 'bloc
k in catch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in 'catc
h'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in 'catc
h'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in 'tim
eout'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/u
til/is_port_open.rb:19:in 'is_port_open?'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/handle_forwarded_port_collisions.rb:248:in 'port_check'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/handle_forwarded_port_collisions.rb:121:in '[]'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/handle_forwarded_port_collisions.rb:121:in 'block in handle'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/handle_forwarded_port_collisions.rb:257:in 'block in with_forwarde
d_ports'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/handle_forwarded_port_collisions.rb:253:in 'each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/handle_forwarded_port_collisions.rb:253:in 'with_forwarded_ports'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/handle_forwarded_port_collisions.rb:98:in 'handle'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/handle_forwarded_port_collisions.rb:42:in 'block in call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/e
nvironment.rb:567:in 'lock'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/handle_forwarded_port_collisions.rb:41:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/env_set.rb:19:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/provision.rb:80:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/clear_forwarded_ports.rb:15:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/set_name.rb:50:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/clean_machine_folder.rb:17:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/check_accessible.rb:18:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:95:in 'block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builder.rb:116:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/u
til/busy.rb:19:in 'busy'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/call.rb:53:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:95:in 'block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builder.rb:116:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/u
til/busy.rb:19:in 'busy'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/call.rb:53:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:95:in 'block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builder.rb:116:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/u
til/busy.rb:19:in 'busy'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/call.rb:53:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/box_check_outdated.rb:78:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/config_validate.rb:25:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/check_virtualbox.rb:17:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:95:in 'block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/match_mac_address.rb:19:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/discard_state.rb:15:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/import.rb:74:in 'import'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/import.rb:13:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/prepare_clone_snapshot.rb:17:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/prepare_clone.rb:15:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/customize.rb:40:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/check_accessible.rb:18:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:95:in 'block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builder.rb:116:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/u
til/busy.rb:19:in 'busy'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/call.rb:53:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/config_validate.rb:25:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:95:in 'block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/handle_box.rb:56:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:95:in 'block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builder.rb:116:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/u
til/busy.rb:19:in 'busy'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builtin/call.rb:53:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/provi
ders/virtualbox/action/check_virtualbox.rb:17:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/warden.rb:34:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/builder.rb:116:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/u
til/busy.rb:19:in 'busy'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/a
ction/runner.rb:66:in 'run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/m
achine.rb:225:in 'action_raw'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/m
achine.rb:200:in 'block in action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/e
nvironment.rb:567:in 'lock'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/m
achine.rb:186:in 'call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/m
achine.rb:186:in 'action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/b
atch_action.rb:82:in 'block (2 levels) in run'

Picture of Khari Kambon
Re: Vagrant Up Fail
by Khari Kambon - Monday, 3 April 2017, 11:23 PM
 

Michael, I can help with this as I experienced the same problem and took a good while to figure out, but don't give up just yet. As it turns out the problem is not with Adapt AT itself, but the Vagrant version 1.9.3 which I see you are attempting to use. Vagrant devs apparently know about this problem, but as of now haven't yet released the 1.9.4 version with the fix. The fix was made less than 2 weeks ago. Some Windows 10 users may also have this same problem. The specific error here is referring to the host IP add not being set and 0.0.0.0 not being available,so you need to configure the Vagrant file to use the host IP 127.0.0.1 (localhost). You'll need to change/add the host_ip parameter set to 127.0.0.1

So here's what you need to do to get past this point:

1. Navigate to the adapt_authoring-master dir you created and at that root (not in the Vagrant folder) you will see a file called "Vagrantfile" This is the config file for your project's (Adapt AT's) Vagrant

2. You need to edit the file so open this file in a text editor like Notepad++ and you should see a line that starts with config.vm.network "forwarded_port"

The full line will look something like this:

config.vm.network "forwarded_port", guest: 5000, host: 5000

Also note that there may be a set of two or three consecutive lines like this. You must update ALL of these present.

If your lines include host_ip: "0.0.0.0" then you'll have to replace the "0.0.0.0" with "127.0.0.1"

If your lines do not include host_ip: "0.0.0.0" then you should add the following:

At the end of each line add: , host_ip: "127.0.0.1"

so after the append you'd have:

config.vm.network "forwarded_port", guest: 50, host: 5000, host_ip: "127.0.0.1"

3. Save the file and close
4. Open Command Prompt as admin and navigate to adapt_authoring-master dir and enter the command vagrant reload
5. The installation process should restart and continue without the EADDRNOTAVAIL error. Note that at some points it will appear that nothing is happening, but the full installation does take some time - at least 20 mins. So just wait patiently for it. It may also show some errors, but these are not fatal. As a precaution, I copy/pasted the entire output into a text file to save and possibly help troubleshoot any problems later.
6. Once it's complete open browser and go to http://localhost:5000 and you should see Adapt.

good luck and let me know how it goes!

Picture of Arun Kumar Pokharna
Re: Vagrant Up Fail
by Arun Kumar Pokharna - Tuesday, 11 April 2017, 8:15 PM
 

Hi Khari,

I am also facing the exact same problem in my windows machine. I followed your steps and tried to debug but I could not find anything as you mentioned in your response. Before describing the error, I should mention the version of software and platform I am using.
Virtual Box: Version 5.1.18 r114002 (Qt5.6.2)

Vagrant: version 1.9.3

My OS: Windows 10.

Steps I took so far:

1). Installed Virtual box with default options.

2). Installed vagrant with default options.

3). Ran command vagrant up and getting the same error as below:

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in `initialize': The requested address is not valid in its context. - connect(2) for "0.0.0.0" port 5000 (Errno::EADDRNOTAVAIL)

 

Issues I could not resolve from your response above:

1). I could not find any dir named "adapt_authoring-master" or any similar name also.

2). My vagrantfile is found on "C:\Users\arunp\.vagrant.d\boxes\udacity-VAGRANTSLASH-ud381\0.0.5\virtualbox". However, it does not contain what you wrote above. It contains as follows (content between <--- --->):

<----
# The contents below were provided by the Packer Vagrant post-processor

Vagrant.configure("2") do |config|
config.vm.base_mac = "08002729222B"
end


# The contents below (if any) are custom contents provided by the
# Packer template during image build.

 --->

 

Please suggest me the solution as I am stuck for a few days on it now.

Picture of Arun Kumar Pokharna
Re: Vagrant Up Fail
by Arun Kumar Pokharna - Tuesday, 11 April 2017, 8:34 PM
 

I got the previous issue and found the mistake I was making. I fixed that problem and got into another issue.

Error message I am getting now is:

 

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'udacity/ud381'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'udacity/ud381' is up to date...
==> default: Setting the name of the VM: ud381_default_1491942726306_11989
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 5000 (guest) => 5000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "d95cf3a9-00ce-4106-bdac-2a6ba774a5e7", "--type", "headless"]

Stderr: VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Picture of Arun Kumar Pokharna
Re: Vagrant Up Fail
by Arun Kumar Pokharna - Tuesday, 11 April 2017, 9:59 PM
 

I could resolve the issues. Thanks for above information. It was really helpful. :-)