Required This determines which Vagrant box will be used. This will effectively generate a configuration similar to: If VAGRANT_DEFAULT_PROVIDER is set and the above logic has a valid virtual switch, no additional configuration is needed.

‘Default Switch’ when running on Windows 10 Fall Creator edition and later.

The environment variable KITCHEN_HYPERV_SWITCH.

Kitchen-vagrant will select the switch to use with new VMs in the following order: It is also important to consider how network switches are defined and selected when using Hyper-V.

This environment variable is particularly useful is you are using Hyper-V in a project where other users rely on VirtualBox. The VAGRANT_DEFAULT_PROVIDER environment variable allows controlling the default provider when one is not defined in the kitchen.yml. Due to this restriction it is recommended that you either set the provider to hyperv in your kitchen.yml config or set the environment variable VAGRANT_DEFAULT_PROVIDER to hyperv.

Microsoft Hyper-V is an exclusive hypervisor, meaning it cannot be used when another hypervisor is active on a system. To learn more about the installation, upgrade, and usage of these plugins see Vagrant VMware Desktop Plugin Documentation and Parallels + Vagrant Documentation.

Specify the provider within your kitchen.yml config to use a different hypervisor. Kitchen-vagrant defaults to the virtualbox provider, which provides a high-performance virtualization experience on macOS, Windows, and Linux hosts. Our recommended hypervisors for use with kitchen-vagrant are: Provider Vagrant supports a large number of hypervisors, including both commercial and free/open-source products. The Vagrant driver is the preferred driver for local cookbooks testing due to the extensive platform and hypervisor support in Vagrant before running Test Kitchen. Kitchen-vagrant is a Test Kitchen driver for HashiCorp Vagrant 1.6 and later.

Vagrant base box