Re-establishing reference from Vagrant to VirtualBox VM

0 0

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

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

Now I can create the file

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

using the UUID learned from VBoxManage.

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

About Post Author

Lucas Jellema

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, Kubernetes & Docker, Machine Learning, Java, SOA and microservices, events in various shapes and forms and many other things. Author of the Oracle Press book Oracle SOA Suite 12c Handbook. Frequent presenter on user groups and community events and conferences such as JavaOne, Oracle Code, CodeOne, NLJUG JFall and Oracle OpenWorld.

lucas.jellema@amis.nl

https://www.amis.nl/

Happy

0 0 %

Sad

0 0 %

Excited

0 0 %

Sleepy

0 0 %

Angry

0 0 %

Surprise

0 0 %

Related posts:

Fastest way to a Virtual Machine with JDeveloper 12.1.3 and Oracle Database XE 11gR2 – on Ubuntu Linux 64 bit Quick generation of a VirtualBox VM with Oracle Database 12.1.0.2 EE on CentOS 5.6 Resources for JavaOne 2015 session: Java Developer Intro to Environment Management with Vagrant, Puppet, and Docker (BOF2817) Rapid creation of Virtual Machine(s) for SOA Suite 12.1.3 server run time environment – leveraging Vagrant, Puppet and Biemond Vagrant and Docker followed by Puppet to provision complex environments