7/18/2018 - 6:40 AM

virtualbox_and_vagrant_on_windows.md

virtualbox and vangrant on windows 7 SP1

cd /c/Users/Josh/virtualmachines
mkdir ubuntu
cd ubuntu
vagrant init ubuntu/trusty64

Had to enable virtualization in bios cpu settings (see notes below)

If no prompt, must tell Vagrant to prefer your system tools with the VAGRANT_PREFER_SYSTEM_BIN environment variable (https://github.com/hashicorp/vagrant/issues/9143)

VAGRANT_PREFER_SYSTEM_BIN=1 vagrant ssh

or put this into your .bash_profile:

export VAGRANT_PREFER_SYSTEM_BIN=1

Vagrant Docs Vagrant CLI IRC: #vagrant on Freenode

vagrant up hangs, updating powershell as a fix (see https://github.com/hashicorp/vagrant/issues/8777) Now hangs at ssh auth method: private key. Try following fixes:

config.vm.network "forwarded_port", guest: 22, host: 2222, host_ip: "127.0.0.1", id: 'ssh'

Didn't work. Tried adding following block to Vagrantfile (https://github.com/hashicorp/vagrant/issues/8157)

config.vm.provider "virtualbox" do |vb|
    vb.customize ["modifyvm", :id, "--cableconnected1", "on"]
  end

Uninstall "Web Companion". On Windows, go to Control Panel->Programs and Features and find it in the list. Select and click Uninstall
Open a command prompt as Administrator and run: netsh winsock reset
Reboot your PC
Remove the DLL's it was trying to load. They should be located in located in two locations

C:\Windows\System32\LavasoftTcpService.dll C:\Windows\SysWOW64\LavasoftTcpService.dll

Note: There were also two similarly named .ini files. I removed them as well but that isn't strictly necessary

vagrant up --provision
With any luck, this was your issue and the vagrant guest will now be able to ssh into the box during provisioning to setup your environment

Didn't work, No Web companion installed. Try running windows update. Didn't work.

Finally fixed by enabling virtualization in bios cpu setting!!!