Mining-the-Social-Web-2nd-Edition icon indicating copy to clipboard operation
Mining-the-Social-Web-2nd-Edition copied to clipboard

Vagrant Up: Virtual Machine doesn't boot

Open RavDanny opened this issue 8 years ago • 1 comments

Hi, After having some confusion with setting up the Virtual Machine correctly, I followed someone's troubleshooting instructions:

$ git clone https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition Mi ningSocialWeb

which gave me this:

Cloning into 'MiningSocialWeb'... remote: Counting objects: 1725, done. remote: Total 1725 (delta 0), reused 0 (delta 0), pack-reused 1725 Receiving objects: 100% (1725/1725), 29.72 MiB | 1.78 MiB/s, done. Resolving deltas: 100% (850/850), done. Checking connectivity... done.

Then, I did the following:

Danny@Danny-PC MINGW64 /c/Users/danny/MiningSocialWeb (master) $ vagrant up

to which I got the following:

Bringing machine 'default' up with 'virtualbox' provider... ==> default: Box 'precise64' could not be found. Attempting to find and install. .. default: Box Provider: virtualbox default: Box Version: >= 0 ==> default: Box file was not detected as metadata. Adding it directly... ==> default: Adding box 'precise64' (v0) for provider: virtualbox default: Downloading: http://files.vagrantup.com/precise64.box default: ==> default: Successfully added box 'precise64' (v0) for 'virtualbox'! ==> default: Importing base box 'precise64'... ==> default: Matching MAC address for NAT networking... ==> default: Setting the name of the VM: MiningSocialWeb_default_1444284474920_9 1775 ==> default: Fixed port collision for 22 => 2222. Now on port 2200. ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 8888 => 8888 (adapter 1) default: 5000 => 5000 (adapter 1) default: 27017 => 27017 (adapter 1) default: 27018 => 27018 (adapter 1) default: 27019 => 27019 (adapter 1) default: 28017 => 28017 (adapter 1) default: 22 => 2200 (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'poweroff' 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.

[End of quote.]

Any suggestions?

RavDanny avatar Oct 08 '15 06:10 RavDanny

I'm no expert but had several issues so will try. If this doesn't work, keep your file open and just "Ctrl Z" to get back to the original state.

Have you tried adding the gui option to your Vagrantfile as suggested.

  • Navigate to the folder with your "Mining the Social web" clone
  • Open the Vagrantfile in a text editor, just add this:
 config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine

    vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
    vb.memory = "1024"
 end

Make sure the spacing is similar to what's already in the file.

Then try vagrant up

For username and pass, the default is usually "vagrant" and "vagrant". See if you can launch the notebook from the command line. It may require you downloading the Extension Pack for the version of VirtualBox you have; https://www.virtualbox.org/wiki/Downloads

linwoodc3 avatar Feb 29 '16 01:02 linwoodc3