the host VM is still reporting that SSH is unavailable

[scalingexcellence]

the host VM is still reporting that SSH is unavailable

[lookfwd]

Yeah - for the case of limited computers there's a 32-bit VM that supports all but the last chapter: #5 (comment)

Unfortunately the solution doesn't seem to apply. I have been trying to use the Vagrantfile.32 since you've posted. The symptoms have changed, but it is still behaving in a way that seems to reflect an SSH or some other network problem.

I first tried the Vagrantfile.32 straight out of the box, and without modification (withholding the change made to the file extension, of course.) This generated the same VT-x error as previously mentioned.

I then added "vb.customize ["modifyvm", :id, "--hwvirtex", "off"]" to the Vagrantfile.32 file, again still getting the VT-x error.

The full solution had to be applied to Vagrantfile.32 to suppress the VT-x error.

After modifying Vagrantfile.32 and running "vagrant up --no-parallel", I got this message again:
"docker-provider: 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."

Running "vagrant up --no-parallel" a second time, with no manual change in state, I get this message:
"Bringing machine 'scrapy-vm-32' up with 'virtualbox' provider...
==> scrapy-vm-32: Checking if box 'lookfwd/scrapybook32' is up to date...
~/$
"
and running the command a third time, just to be sure:

"Bringing machine 'scrapy-vm-32' up with 'virtualbox' provider...
==> scrapy-vm-32: Checking if box 'lookfwd/scrapybook32' is up to date...
==> scrapy-vm-32: Machine already provisioned. Run vagrant provision or use the --provision
==> scrapy-vm-32: flag to force provisioning. Provisioners marked to run always will still run.
"

So all is good right?

Unfortunately when I type any of the following URL's into the browser address bar:
"web:9312/properties/property_000000.html"
"localhost:web:9312/properties/property_000000.html"
"web:9312"
"localhost:web:9312"

The browser just hangs forever, waiting for the response.

If the browser is trying to access web:9312, and I run "vagrant destroy " from the terminal, then the browser resolves; saying the typical "page cannot be found" error.

I also have tried various combinations of the 3 Vagrantfiles ('Vagrantfile.32', 'Vagrantfile', 'Vagrantfile.host'). For example, I've tried changing the name of 'Vagrantfile.32' to 'Vagrantfile.host', and as I am sure that you expect, it say 'docker-provider' can't be found (or something like that.)

When vagrant is active and stable, by running ~/$ virtualbox ; the virtualbox GUI pops up, but no VM is listed. Although vagrant global-status does list a VM.

I don't know if it makes a difference, but I am pretty sure that my machine is 64 bit. I run Ubuntu 64 bit, I have ran FL Studio 64 bit. The CPU definitely does not support virtualization technology though. I first checked BIOS, and the option was not present. I ran the command from the terminal with grep to search for svm, and (I don't remember the other name,) to which neither requirement was present. I then found an online technical resource specifically for my CPU. Alas, VT is not supported. That issue, of non-supporting architecture, was solved by adding the three lines to the Vagrantfile. When I went through this process of modifying the Vagrantfile, I did so incrementally in both cases (for Vagrantfile, and for Vagrantfile.32,) from the bottom up. The system simply would not run until I had added every line.

Am I over looking something in all of this?

Also, perhaps unrelated, but as soon as I sent the last post: all of my machines went off the network, but my brothers did not. My tablet recovered first, after I shut my laptop down (where I was running vagrant.) My laptop took several minutes to recover connectivity after reboot. Vagrant was active at the time.

update: various machines keep going on and off the network. lol

Reseting the router fixed the connectivity issues.

[lookfwd]

A few summarizing points:

a) The easy solution for me is to say that your machine isn't supported and I'm fine. I don't need to fix it for a machine that doesn't have Virtualization extensions... everything beyond this is a bonus
b) I don't need to comment on Vagrant hacks and I highly discourage anyone from hacking Vagrantfiles. If it doesn't work, send a post here or on the e-mail as you did and I will find a solution. It takes months and lots of pain to get on an intermediate level with Vagrant and all those VM stuff and if you spend just a few hours all you will be able to contribute is part of your feelings of pain... which are irrelevant to Scrapy and the book. If Vagrant doesn't work, don't fix it.

Overall, I will try to contact you on the e-mail and fix your system. If there's something I believe might be of interest to other people I will come back and report. Otherwise, we're good for now.

P.S. "localhost:web:9312/properties/property_000000.html", "localhost:web:9312" aren't valid URLs. "localhost:9312/properties/property_000000.html", "localhost:9312" might work.

[lookfwd]

There was also an issue with unsupported, by default, network card. See 5a6600a

I will definitely check that out. thanks a million, I would have never figured out how to get it to run properly.

[lookfwd]

Cheers! Yes, VM's are very tricky. Unless you get them "exactly right" they will bite you sooner or later. Enjoy!