After installing the Vm i get a time out error

[AymanIslam]

After installing the Vm and typing vagrant up i get a time out error
afterwards when i type Vagrant up again i get a msg indicating that the machine in already running
when i try to go to the notebook using the browser i get nothing

[AymanIslam]

By the way the Vm is installed inside a linux ubuntu 13.10 32 bit VM ware virtual machine
and i have modified the vagrant file as ststed in the getting started video

[AymanIslam]

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. This can
mean a number of things.

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.

[AymanIslam]

when trying to connect to the vagrant vm using ssh i get
ssh_exchange_identification: read: Connection reset by peer

[ptwobrussell]

Glad to try and help you.

Can you clarify if you have already successfully gotten a Vagrant box powered by Virtualbox to work and now you are trying with VMWare? Or are you starting with VMWare as your provider?

When you initially say "i get a time out error", can you paste in the console log with the particulars?

Also, can you describe your host machine's operating system?

Someone submitted a pull request with specific changes to the Vagrantfile that might really help: #113

TBH, I haven't used VMWare myself yet (though I do intent to test the pull request and merge it), but in theory, it should work since it is fully supported by Vagrant. (In the event we get stuck though, it might be wise to use Virtualbox since I'm confident I can best help you there.)

[AymanIslam]

Thanks a lot for ur response
1- I installed vmware on windows 8 64 bit
2- I created an Ubuntu linux 13.10 vm
3- i used the ubuntu linux vm as my host for your Vagrant vm

[AymanIslam]

I followed the getting started video from inside ubuntu vm

[AymanIslam]

I installed virtualbox and vagrant INSIDE the ubuntu linux vm

[ptwobrussell]

@AymanIslam - Ok, this is helpful. TBH, it's going to be a challenge to help you given that you are working pretty far outside of the standard parameters. Would you consider just following the instructions exactly as they're written to get everything up and running, and then once you have a good baseline understanding in place with a configuration that I can support, you could deviate and try other configurations?

The big deviations as I understand them from your description are that 1) you are using VMWare versus Virtualbox (which version of VMWare?), 2) you are using a different base image (not precise64) for your VM (which one?), and 3) you are trying to configure a 32 bit VM even though your host is a 64 bit machine (why?)

I am more than happy to try and help you push through this, though I can't make any guarantees about how much back and forth or time will be involved. (With the supported configuration, I can be a lot more certain about things, though.)

Regardless of which path you'd like to choose, I'll need to see your console output to better diagnose some of the issues. There's really no way to move forward without a clean start without that. (You can do a "vagrant destroy" and then another "vagrant up" to start clean and get good console output.)

[AymanIslam]

[AymanIslam]

The screen shot i posted is from my ubuntu linux vmware

[AymanIslam]

i am using vmware 10

[AymanIslam]

The terminal is stuck on "waiting for your machine to boot " and the virtualbox shows that the machine is running

[ptwobrussell]

I just noticed something that you said previously but initially slipped past me: "I installed virtualbox and vagrant INSIDE the ubuntu linux vm"

TBH, I have no idea what happens if you are trying to run VMs inside of VMs, and I'd advise against it if at all possible. There is almost certainly something hokey going on here as evidenced by the fact that your VM doesn't ever seem to boot, which (I think) is symptomatic of a deeper problem than anything with Mining the Social Web's VM. You're the first person to ever try to do this that I've attempted to support.

Could you consider just following the instructions exactly as written in the Quick Start guide at http://miningthesocialweb.com/quick-start/ which would entail installing Virtualbox and Vagrant on your Windows 8 host? I am certain this will work for you, and you'll have an operational environment. From there, you can always revisit using other providers or running VMs inside of VMs if that's what you really want to do.

You might also consider the Vagrant IRC channel or Google Group, because if you insist of running VMs inside of VMs, there would be some people in there who could speak to the issues and configurations involved a lot better than I could.

[ptwobrussell]

Just wanted to check back with you on this?