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

Vagrantfile to manage existing VMs #291

Open
Hi-Angel opened this issue Aug 6, 2020 · 1 comment
Open

Vagrantfile to manage existing VMs #291

Hi-Angel opened this issue Aug 6, 2020 · 1 comment

Comments

@Hi-Angel
Copy link

Hi-Angel commented Aug 6, 2020

I have a vSphere with pre-existing VMs that I want to manage with Vagrant.

However when I use a Vagrantfile from README, vagrant tries to create a new VM instead. The reason is that README requires to put in the file either this:

# this means clone a VM
vsphere.clone_from_vm = true

…or this:

# this means create a VM from a template
vsphere.compute_resource_name = 'YOUR COMPUTE RESOURCE'
vsphere.resource_pool_name = 'YOUR RESOURCE POOL'

…but I don't want a new VM, I want to run existing ones. In fact, I can't even clone some VMs, because I get a complaint

$ vagrant up --provider=vsphere
Bringing machine 'default' up with 'vsphere' provider...
==> default: Calling vSphere CloneVM with the following settings:
==> default:  -- Source VM: Datacenter/vm/my_node1
==> default:  -- Target VM: Datacenter/vm/my_node1
SnapshotIncompatibleDeviceInVm: Virtual machine is configured to use a device that prevents the snapshot operation: Device '' is a SCSI controller engaged in bus-sharing.

So, what options do I need to NOT clone/create a VM, but rather to run an existing one?

@edmcman
Copy link

edmcman commented Aug 6, 2020

I think you'd have to modify the source to do this.

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