From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/vagrant/hyperv%2Fconfiguration.html | 34 +++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 devdocs/vagrant/hyperv%2Fconfiguration.html (limited to 'devdocs/vagrant/hyperv%2Fconfiguration.html') diff --git a/devdocs/vagrant/hyperv%2Fconfiguration.html b/devdocs/vagrant/hyperv%2Fconfiguration.html new file mode 100644 index 00000000..af18e540 --- /dev/null +++ b/devdocs/vagrant/hyperv%2Fconfiguration.html @@ -0,0 +1,34 @@ +

Configuration

The Vagrant Hyper-V provider has some provider-specific configuration options you may set. A complete reference is shown below:

VM Integration Services

The vm_integration_services configuration option consists of a simple Hash. The key values are the names of VM integration services to enable or disable for the VM. Vagrant includes an internal mapping of known services which allows them to be provided in a "snake case" format. When a provided key is unknown, the key value is used "as-is" without any modifications.

For example, if a new CustomVMSRV VM integration service was added and Vagrant is not aware of this new service name, it can be provided as the key value explicitly:

config.vm.provider "hyperv" do |h|
+  h.vm_integration_services = {
+    guest_service_interface: true,
+    CustomVMSRV: true
+  }
+end
+
+

This example would enable the GuestServiceInterface (which Vagrant is aware) and CustomVMSRV (which Vagrant is not aware) VM integration services.

+

+ © 2010–2018 Mitchell Hashimoto
Licensed under the MPL 2.0 License.
+ https://www.vagrantup.com/docs/hyperv/configuration.html +

+
-- cgit v1.2.3