Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to configure an existing VM for use with Vagrant? #262

Open
chrigrahcisco opened this issue Jun 19, 2018 · 1 comment
Open

How to configure an existing VM for use with Vagrant? #262

chrigrahcisco opened this issue Jun 19, 2018 · 1 comment

Comments

@chrigrahcisco
Copy link

chrigrahcisco commented Jun 19, 2018

Vagrant 1.9.2
vagrant-vsphere (1.13.2)

I am successfully using Vagrant to manage a variety of systems and environments simultaneously as long as I create multiple, unique directories for each environment so they can all maintain their own unique .vagrant

However, I have a couple existing environments that someone else created using Vagrant so I don't have an available .vagrant for these boxes. Vagrant simply sees the currently running boxes as. vagrant_vsphere.states.short_not_created (vsphere)

Is there some manual process I can use to associate these existing boxes with Vagrant vSphere as opposed to having to destroy and recreate them?

@brozow
Copy link

brozow commented Sep 21, 2018

I would love to see this to due to the following bug:

https://kb.vmware.com/s/article/2064681

This way I could create the VM manaually and then do the rest via vagrant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants