Or even simpler, specifically, if you open Git Bash (if you still haven’t installed Git tools on Windows, please do so, it’ll make your life infinitely easier) and run the following commands in order:
git clone https://github.com/swader/homestead-improved hi_sample
cd hi_sample
sed -i '' "s@map\: \.@map\: $PWD@g" Homestead.yaml
vagrant up
@Webmachine did you solve your virtualization problem? If not, if you would want to shoot me some pictures or something I could try and help you out. Typically you’re looking under some sort of “CPU Options” menu although it’s pretty much been different on most BIOS I’ve looked at, so kind of hard to give you a generic answer. You’re right, it’s ludicrously hard to find settings information for particular computers and mobos and such. It’s annoying.
@swader, @jeffreylees - thank you for your suggestions. I will try these out when I get some time this afternoon.
I had given up and gone back to using my setup in xampp, figuring that if my machine had virtualization disabled and didn’t show the option to enable it, then I was out of luck until I got a different laptop.
I tried finding the users manual for my laptop (an MSI gaming laptop), but they want you to create an account and sign your life away first so I bailed.
Yeah, what I’m saying is that I’m not sure if she’d need to, hence why trying @swader’s suggestion would be a good quick way to know one way or another.
Also, why I was asking for pictures of BIOS screens above - just to be sure the setting is not being missed. I know mine on my work machine was buried in some submenu ambiguously worded.
Here are the images of my BIOS. As I mentionnd in a previous post, I used Speccy to take a look at my system, and apparently I have virtualization support, but virtualization is disabled.
I seem to be progressing slowly (I haven’t had much time to work on this lately) - I got as far as typing the ‘vagrant up’ command and have run into a conflict with my ports. How can I fix this without wrecking my Xampp setup that uses port 80?
The error message was as follows:
I would like to know if I added the line “config.vm.network :forwarded_port, guest: 80 host: 1234” , would that do the job, or would I really mess up everything?
BUT - before you do editing, try running vagrant up; a few times, I’ve found that sometimes when I get a FAIL the first time, the second time Vagrant is able to auto-correct.
Suggestion, if you do edit the file, comment out the existing line with a hash and leave comments eg.
# config.vm.network :forwarded_port, guest: 3000, host: 4000 # Aarrgghh doesn't work !
config.vm.network :forwarded_port, guest: 3000, host: 8080 # maybe this will work ?