Skip to content

Commit

Permalink
Update README
Browse files Browse the repository at this point in the history 
A lot of documentation is incorrect and extremely confusing for fresh installers/new users of VM. 
If fresh install downloads VB 6.1.x [Windows], VVV sets default provider to Hyper-V instead of VB, even if the Windows OS is compatible with Hyper-V.

The only way of being aware that VB 6.1.x is incompatible is by adding --provider=virtualbox at the end of vagrant up, to which we will receive the error explaining that it only is compatible with 6.0 and below. There is no documentation of this.
  • Loading branch information
@achaacha @tomjn
achaacha authored and tomjn committed Jan 20, 2020
1 parent 985cb6b commit 56dfff7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
View file
Expand Up @@ -22,8 +22,8 @@ The online documentation contains more detailed [installation instructions](http

## Minimum System requirements

* [Vagrant](https://www.vagrantup.com) 2.2.4+
* [Virtualbox](https://www.virtualbox.org) 5.2+
* [Vagrant](https://www.vagrantup.com) 2.2.6 or below.
* [Virtualbox](https://www.virtualbox.org) 6.0.x or below.

This comment has been minimized.

Sign in to view

Copy link
@MaxLaumeister

MaxLaumeister Jan 30, 2020 •
edited

Spent this afternoon figuring out that Virtualbox 6.1 was causing my issues. Thank you for adding it to the readme, or it could have taken me longer!

This comment has been minimized.

Sign in to view

Copy link
@tomjn

tomjn Jan 30, 2020

Member

@MaxLaumeister it's Vagrant 2.2.6 that's incompatible, not VVV

This comment has been minimized.

Sign in to view

Copy link
@MaxLaumeister

MaxLaumeister Jan 30, 2020

@tomjn Thanks. Updated to reflect that.
* 8GB+ of RAM
* Virtualisation ( VT-X ) enabled in the BIOS ( Windows/Linux )
* Hyper-V turned off ( Windows )
Expand Down

0 comments on commit 56dfff7

Please sign in to comment.