Last modified: 2013-10-19 14:16:05 UTC
I upgraded to the vagrant 1.3.5 and had the following problem at the initial boot with windows 7 and ubuntu 12.04.lts both 64 bit: Error message: hostname -f command not found Solution: comment the line starting with config.vm.hostname and uncomment after first boot I'm wondering that nobody else has ran into that problem.
The error message: [default] The guest additions on this VM do not match the installed version of VirtualBox! In most cases this is fine, but in rare cases it can cause things such as shared folders to not work properly. If you see shared folder errors, please update the guest additions within the virtual machine and reload your VM. Guest Additions Version: 4.1.12 VirtualBox Version: 4.2 [default] Setting hostname... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! hostname -f Stdout from the command: Stderr from the command: sudo: unable to resolve host mediawiki-vagrant hostname: Name or service not known
I think this is a corner case. I just had to remove the old box via vagrant box remove precise-cloud