search

mitthu / cmpsc473_spring18

Logistics for the course
0 stars 0 forks source link

'vagrant up' times out #2

Open Oponn-1 opened 6 years ago

Oponn-1 commented 6 years ago

C:\Users\Andres\Documents\datalab-handout>vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'ubuntu/xenial64'... ==> default: Matching MAC address for NAT networking... ==> default: Setting the name of the VM: datalab-handout_default_1516055384033_88941 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... 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 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.

If you look above, you should be able to see the error(s) that Vagrant had when attempting to connect to the machine. These errors are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly working and you're able to connect to the machine. It is a common problem that networking isn't setup properly in these boxes. Verify that authentication configurations are also setup properly, as well.

If the box appears to be booting properly, you may want to increase the timeout ("config.vm.boot_timeout") value.

The above is the output when I try to start my VM. I am doing this from the project folder extracted from the zip file from canvas.

timmyzhu commented 6 years ago

Sometimes this may be due to not having Intel VT-x or AMD-V virtualization hardware support enabled in the bios. One thing you can try is opening VirtualBox and launching the VM. If you get an error message about hardware virtualization support, then you'll need to enable that in the bios. Afterwards, vagrant up should hopefully work. You may need to run vagrant provision (once) after vagrant up is run to do an initial setup.