From 82ba818ff456bcd6d56a06226e3f27e98fbb55c3 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Thu, 14 Aug 2025 22:58:58 -0500 Subject: removing all downloaded devdocs files --- devdocs/vagrant/hyperv%2Flimitations.html | 6 ------ 1 file changed, 6 deletions(-) delete mode 100644 devdocs/vagrant/hyperv%2Flimitations.html (limited to 'devdocs/vagrant/hyperv%2Flimitations.html') diff --git a/devdocs/vagrant/hyperv%2Flimitations.html b/devdocs/vagrant/hyperv%2Flimitations.html deleted file mode 100644 index c001f596..00000000 --- a/devdocs/vagrant/hyperv%2Flimitations.html +++ /dev/null @@ -1,6 +0,0 @@ -

Limitations

The Vagrant Hyper-V provider works in almost every way like the VirtualBox or VMware provider would, but has some limitations that are inherent to Hyper-V itself.

Limited Networking

Vagrant does not yet know how to create and configure new networks for Hyper-V. When launching a machine with Hyper-V, Vagrant will prompt you asking what virtual switch you want to connect the virtual machine to.

A result of this is that networking configurations in the Vagrantfile are completely ignored with Hyper-V. Vagrant cannot enforce a static IP or automatically configure a NAT.

However, the IP address of the machine will be reported as part of the vagrant up, and you can use that IP address as if it were a host only network.

Snapshots

Restoring snapshot VMs using vagrant snapshot pop or vagrant snapshot restore will sometimes raise errors when mounting SMB shared folders, however these mounts will still work inside the guest.

-

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

-
-- cgit v1.2.3