Re-establishing reference from Vagrant to VirtualBox VM

1
Share this on .. Tweet about this on TwitterShare on LinkedIn0Share on Facebook0Share on Google+0Email this to someoneShare on Tumblr0Buffer this page

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

Share this on .. Tweet about this on TwitterShare on LinkedIn0Share on Facebook0Share on Google+0Email this to someoneShare on Tumblr0Buffer this page

About Author

Lucas Jellema, active in IT (and with Oracle) since 1994. Oracle ACE Director and Oracle Developer Champion. Solution architect and developer on diverse areas including SQL, JavaScript, Docker, Machine Learning, Java, SOA and microservices, events in various shapes and forms and many other things. Author of the Oracle Press books: Oracle SOA Suite 11g Handbook and Oracle SOA Suite 12c Handbook. Frequent presenter on community events and conferences such as JavaOne, Oracle Code and Oracle OpenWorld.

1 Comment

Leave a Reply