This repository has been archived on 2025-01-19. You can view files and clone it, but cannot push or open issues or pull requests.
oliverdavies.uk-old-sculpin/source/_posts/2014-10-06-fix-vagrant-loading-wrong-virtual-machine.md
2015-03-17 04:04:02 +00:00

1,021 B

title nav slug tags
How to fix Vagrant Loading the Wrong Virtual Machine blog fix-vagrant-loading-wrong-virtual-machine
Vagrant
VirtualBox

A few times recently, I've had instances where Vagrant seems to have forgotten which virtual machine it's supposed to load, probably due to renaming a project directory or the .vagrant directory being moved accidentally. Here are the steps that I took to fix this and point Vagrant back at the correct VM.

  • Stop the machine from running using the $ vagrant halt command.
  • Use the $ VBoxManage list vms command to view a list of the virtual machines on your system. Note the ID of the correct VM that should be loading. For example, "foo_default_1405481857614_74478" {e492bfc3-cac2-4cde-a396-e81e37e421e2}. The number within the curly brackets is the ID of the virtual machine.
  • Within the .vagrant directory in your project (it is hidden by default), update the ID within the machines/default/virtualbox/id file.
  • Start the new VM with $ vagrant up.