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.

Vmware vs virtualbox on slackware