Re-establishing reference from Vagrant to VirtualBox VM

Lucas Jellema 1

Stress in the middle to demo preparation: Vagrant refused to bring up my suspended VMs. The message is wrote:

D:\GitHub\biemond-orawls-vagrant-12.1.3-infra-soa>vagrant resume soa2admin2
==> soa2admin2: VM not created. Moving on…

After some Googling I discovered that the link between Vagrant and my VM consists of a the file called “id” in the subfolder

image

This file contains nothing but UUID used by VirtualBox to identify the VM.

Unfortunately, this file was missing (not sure why).

It is fairly easy to restore.

First, find out the required UUID, using the management tools for Virtual Box; in the home directory for Virtual Box, I sued this command to list all VMs and their UUID values:

VBoxManage list vms

SNAGHTML102d9cf

Now I can create the file

D:\GitHub\biemond-orawls-vagrant-12.1.3-infra-soa\.vagrant\machines\soa2admin2\virtualbox\id

SNAGHTML1047bd8

using the UUID learned from VBoxManage.

After restoring this file, I can start the VM as wanted and expected:

image

One thought on “Re-establishing reference from Vagrant to VirtualBox VM

Comments are closed.

Next Post

Very first experience with oracle Cloud Service

Facebook0TwitterLinkedinRecently I found myself in the unique position of having access to the beta version of the Oracle Cloud to get a glimpse at the future as Oracle sees it. This blog describes my personal experience and does not necessarily reflect Oracle’s point of view.  That said, the cooperation with […]