1

I need to be able to spin up VMs every now and again so that I can have a space to build the latest iteration from my project's 'dev' branch (using chef), run the configuration scripts, and make sure that the scripts are not broken due to the latest build changing something.

I've been looking at Vagrant and I like what I see so far, but it seems from the website to favor Type 2 Hypervisors. After some googling and poking around the mailing list, I found that there is a vSphere plugin on github aside from the baked-in VirtualBox support.

My question is, does Vagrant have support for a T1 Hypervisor?

Devon Finninger
  • 113
  • 2

1 Answers1

0

A Vagrant KVM provider exists which uses libvirt for controlling the hypervisor. Thus it (in theory; I don't know if the provider implements it yet) can be used to deploy either to the local workstation or a remote hypervisor.

A Vagrant libvirt provider exists which provides more general provisioning via libvirt, and thus could (again, in theory) be used to provision VMs on any libvirt-supported hypervisor, such as KVM, Hyper-V, ESXi, etc.

Michael Hampton
  • 237,123
  • 42
  • 477
  • 940
  • vagrant-kvm and vagrant-libvirt both use libvirt and both only support KVM. vagrant-libvirt can be used to control VMs both locally or remotely, whereas vagrant-kvm only works locally. – sciurus Oct 03 '13 at 14:54
  • @sciurus Time for somebody to add the features then :) – Michael Hampton Oct 03 '13 at 14:55
  • 1
    [From vagrant-kvm README](https://github.com/adrahon/vagrant-kvm): "This project is dead, please use [vagrant-libvirt](https://github.com/pradels/vagrant-libvirt/) instead!" – Timofey Stolbov May 16 '15 at 13:32