Kitchen-vagrant 1.3.0 released!

Ohai kitchen users,

We’re pleased to announce the latest release of kitchen-vagrant which is all about Hyper-V. If you’re a Windows user and interested in leveraging vagrant + hyperv, we’ve made it much easier to do so in test-kitchen.


As Hyper-V is an exclusive hypervisor, it is recomended that the environment variable VAGRANT_DEFAULT_PROVIDER be set to hyperv. Vagrant currently requires user input to choose a virtual switch so we try to detect this automatically and use a workaround. If no network configuration is provided, we check:

  1. environment variable KITCHEN_HYPERV_SWITCH
  2. use the built-in ‘Default Switch’ if available (Windows 10 Fall Creators Update)
  3. the first switch returned

If VAGRANT_DEFAULT_PROVIDER is set and the above logic has a valid virtual switch, no additional configuration is needed. This will effectively generate a configuration similar to:

  name: vagrant
  provider: hyperv
  - ["public_network", bridge: "Default Switch"]

In conjunction with the latest Bento Release Hyper-V users can now leverage kitchen-vagrant without any extra configuration.