opdavies/oliverdavies.uk-old-sculpin
Archived
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Updated post

Browse source
This commit is contained in:
Oliver Davies 2015-04-11 20:28:43 +01:00
parent 78ed619613
commit 787265c628
1 changed files with 11 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
source/_posts/2014-10-06-fix-vagrant-loading-wrong-virtual-machine.md
View file

@ -5,12 +5,16 @@ use:
- posts
slug: fix-vagrant-loading-wrong-virtual-machine
tags:
- Vagrant
- VirtualBox
- vagrant
- virtualbox
meta:
description: How to fix it when Vagrant loads the wrong virtual machine.
---
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.
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.
* 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`.
Here are the steps that I took to fix this and point Vagrant back at the correct VM.
1. Stop the machine from running using the `$ vagrant halt` command.
2. 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.
3. Within the .vagrant directory in your project (it is hidden by default), update the ID within the machines/default/virtualbox/id file.
4. Start the new VM with `$ vagrant up`.