Cleaned and reindented Vagrantfile with 3 spaces, remove tabs
Weird provisioning bug, counteract with explicit --provision flag

vagrant destroy + vagrant up, should surely provision the new fresh
machine, but under certain circumstances Vagrant seems to claim that the
machine is already provisioned.  It appears this weird bug can be
circumvented by simply forcing provisioning.  Still have no idea
why this happens though - it didn't do it before...
Merge also upstream so we can push properly
HDD sizes added to README.md