Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Document how to handle Hyper-V provisioning errors. 

Specifically, the problem here is that Vagrant is mis-detecting what
provider to use.
This commit is contained in:
Priyanshu Singh 2019-03-02 18:22:58 +05:30 committed by Tim Abbott
parent 6a540d5773
commit 61c0796025
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/development/setup-vagrant.md
View File

@ -767,6 +767,19 @@ vboxmanage setextradata YOURVMNAME VBoxInternal2/SharedFoldersEnableSymlinksCrea
The virtual machine needs to be shut down when you run this command. The virtual machine needs to be shut down when you run this command.
#### Hyper-V error messages
If you get an error message on Windows about lack of Windows Home
support for Hyper-V when running `vagrant up`, the problem is that
Windows is incorrectly attempting to use Hyper-V rather than
Virtualbox as the virtualization provider. You can fix this by
explicitly passing the virtualbox provider to `vagrant up`:
```
christie@win10 ~/zulip
$ vagrant up --provide=virtualbox
```
#### Connection timeout on `vagrant up` #### Connection timeout on `vagrant up`
If you see the following error after running `vagrant up`: If you see the following error after running `vagrant up`: