I am using macOS Mojave. After I installed VirtualBox and Vagrant, I tried "vagrant up". However, I got following strange error:
Dir: VA $vagrant up
sh: netsh: command not found
sh: cscript: command not found
It seems that you don't have the privileges to change
the firewall rules. NFS will not work without that
firewall changes. Execute the following commands via
cmd as administrator:
netsh advfirewall firewall add rule
name="VagrantWinNFSd-1.4.0" dir="in" action=allow
protocol=any
program="\Users\Ten\.vagrant.d\gems\2.4.4\gems\vagrant
...
It seems netsh and cscript command belong to Windows. However, I am using macOS and I am sure my VirtualBox and Vagrant are for macOS.
Can any one help me with this question? Thanks!
===================== Updated ===================
At last I solved this problem. However I am sorry I forgot I raised the question here and even worse I forgot how I solved it.
The only thing I remembered is, installing VirtualBox first and then Vagrant is important. And reinstallation may help.
Hope this can help a bit.
I faced this issue on macOS Sierra (10.12.6). I resolved it after finding that I had the plugin vagrant-winnfsd installed.
To uninstall, I ran the command:
vagrant plugin uninstall vagrant-winnfsd
Related
Help solve the problem with powershell.
I use as a console git bash. VT-x enabled. Hyper-v disabled.
Problem in
The version of powershell currently installed on this host is less than
the required minimum version. Please upgrade the installed version of
powershell to the minimum required version and run the command again.
Installed version: N/A
Minimum required version: 3
Installed powershell 6.
The error usually occurs when entering
vagrant ssh
or
vagrant up
It's funny that the problem is solved by re-entering vagrant up or vagrant ssh.
What is the problem ?
p.s. Sorry for bad English :)
The comment by Theo solved the issue for us.
powershell -Command 'vagrant up'
Executing vagrant ssh next works as expected AND is also a little faster.
I just recently installed Vagrant and Virtualbox but am unable to run Vagrant. I'm getting the following error when I run 'vagrant up':
roosterlegs#roosterlegs-Lenovo-Y50-70:~/vagrant_proj$ vagrant up
VirtualBox is complaining that the installation is incomplete. Please
run `VBoxManage --version` to see the error message which should contain
instructions on how to fix this error.
Then when I run 'VBoxManage --version', I get:
roosterlegs#roosterlegs-Lenovo-Y50-70:~/vagrant_proj$ VBoxManage --version
WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.
You will not be able to start VMs until this problem is fixed.
5.0.18_Ubuntur106667
I have tried a number of solutions such as the instructions here:
How to correct virtualbox installation, but nothing has seemed to work.
Please help.
For others who are also having the issue, disable the secure boot. Worked to me.
Reinstalling virtualbox-dkms (via aptitude reinstall virtualbox-dkms) did the trick for me. It forced the rebuild of the modules and whatnot, now my VMs boot again =)
Hope this helps
I am trying to add the laravel/homestead box to my vagrant installation and keep getting the error "The program 'vagrant' is currently not installed. You can install it by typing: sudo apt-get install vagrant"
I have virtual box installed and working (I use it regularly) and I just downloaded vagrant and it DID say it downloaded successfully. Some forums suggest my installation is not up to date but I installed it about 15 minutes ago so I don't think that could be the case.
Also, I have already created a new directory using mkdir, then used "vagrant init hashicorp/precise32" and then "vagrant ssh" which have all been successful. The next thing I try to do is add the box and it won't work. I have never used vagrant before so I am unfamiliar with this. Any help is appreciated!
PS I'm on OSX El Capitan
Not sure if this is useful after so many months, but I ran into this same problem yesterday. There appears to be a lot of information about this in the vagrant git forums.
As a workaround (not fix) I downgraded to virtualBox 5.0, and vagrant 1.7.4
I have cloned a repository from Github following a course on Udacity. It contains a vagrant file and according to the tutorial I shoulld use vagrant up command to get the virtual machine started. But it says that vagrant is not a recognized internal/external command. How can I fix this?
Install Vagrant for Windows, if your machine OS is windows.
https://www.vagrantup.com/downloads.html
Restart computer.
Install Virtualbox from Virtualbox SDK
https://www.virtualbox.org/wiki/Downloads
VirtualBox 5.2.6 platform packages. The binaries are released under the terms of the GPL version 2.
Windows hosts
Once Virtual box is installed, run the command on the cmd prompt.
vagrant up --provision
I'm in the same course on Udacity and I think the issue you are having can be resolved by adding C:\Hashicorp\Vagrant\bin to your system variables path.
Instructions for editing your path can be found here: Where can I set path to make.exe on Windows?
This fixed the error for me.
I am on Windows 8.1
When i attempt to install vagrant and run it with virtual box i always get the following error.
"The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:
Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the VBoxManage binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
VBoxManage binary and add it to the PATH environmental variable."
I have tried different things such as uninstalling both virtual box and vagrant and re-installing them.
I have tried installing vagrant first then vbox and the other way around also but no change.
I am new to vagrant so if anyone can assist please.
I bet that you're using the latest VirtualBox version (4.3.12). If so, there's a known issue which will be addressed in Vagrant 1.6.3:
https://github.com/mitchellh/vagrant/issues/3852
As a workaround you can install VirtualBox 4.3.10 and it will work flawlessly.
As Emyl said, you can either downgrade your VirtualBox or upgrade your Vagrant to 1.6.3(as the issue has been fixed in this version).
But if you want to have a quick fix on this issue you can simply change the environmental variable name for the Virtual Box installation path from VBOX_MSI_INSTALL_PATH to VBOX_INSTALL_PATH
(This PC -> Advanced System Settings -> Environmental Variables -> Search for VBOX_MSI_INSTALL_PATH and change it to VBOX_INSTALL_PATH)
Make sure to restart your terminal before doing vagrant up again.
You are done!
changing VBOX_MSI_INSTALL_PATH and change it to VBOX_INSTALL_PATH in environment variables and then restarting terminal resolved my issue :)
I also had this problem on Windows 8.1 and solved it by restarting my computer. If you have just installed VirtualBox, you may need to restart your command prompt or Windows for the environment variables to get read correctly when you run "vagrant up".
i had to run the cmd.exe as administrator to make this work after using Sri Harsha Kappala solution