Add hyperv docs for disk management

This commit is contained in:
Brian Cain 2020-04-21 14:53:57 -07:00
parent cf063c6e38
commit 7012328672
No known key found for this signature in database
GPG Key ID: 9FC4639B2E4510A0
3 changed files with 92 additions and 0 deletions

View File

@ -0,0 +1,26 @@
---
layout: "docs"
page_title: "Common Issues - Disks Hyper-V Provider"
sidebar_current: "disks-providers-virtualbox-issues"
description: |-
This page lists some common issues people run into with Vagrant and Hyper-V
as well as solutions for those issues.
---
# Common Issues and Troubleshooting
This page lists some common issues people run into with Vagrant and Hyper-V
as well as solutions for those issues.
## Are my disks attached?
A handy way to figure out what disks are attached (or not attached) to your guest
is to open up the Hyper-V GUI and select the guest. When selecting a guest on the GUI,
it should open more information about the guest, including storage information. Here
you should see a list of disks attached to your guest.
## Applying Vagrant disk configuration changes to guests
Due to how Hyper-V works, you must reload your guest for any disk config changes
to be applied. So if you update your Vagrantfile to update or even remove disks, make
sure to `vagrant reload` your guests for these changes to be applied.

View File

@ -0,0 +1,35 @@
---
layout: "docs"
page_title: "Disks for Hyper-V Provider"
sidebar_current: "disks-providers-virtualbox"
description: |-
Vagrant comes with support out of the box for Hyper-V, a free,
cross-platform consumer virtualization product.
---
# Hyper-V
<div class="alert alert-warning">
<strong>Warning!</strong> This feature is experimental and may break or
change in between releases. Use at your own risk. It currently is not officially
supported or functional.
This feature currently reqiures the experimental flag to be used. To explicitly enable this feature, you can set the experimental flag to:
```
VAGRANT_EXPERIMENTAL="disks"
```
Please note that `VAGRANT_EXPERIMENTAL` is an environment variable. For more
information about this flag visit the [Experimental docs page](/docs/experimental/)
for more info. Without this flag enabled, any disks defined will not be configured.
</div>
Because of how Hyper-V handles disk management, a Vagrant guest _must_ be powered
off for any changes to be applied to a guest. If you make a configuration change
with a guests disk, you will need to `vagrant reload` the guest for any changes
to be applied.
For more information on how to use VirtualBox to configure disks for a guest, refer
to the [general usage](/docs/disks/usage.html) and [configuration](/docs/disks/configuration.html)
guide for more information.

View File

@ -0,0 +1,31 @@
---
layout: "docs"
page_title: "Usage - Disks VirtualBox Provider"
sidebar_current: "disks-providers-virtualbox-usage"
description: |-
The Vagrant VirtualBox provider is used just like any other provider. Please
read the general basic usage page for providers.
---
# Usage
<div class="alert alert-warning">
<strong>Warning!</strong> This feature is experimental and may break or
change in between releases. Use at your own risk. It currently is not officially
supported or functional.
This feature currently reqiures the experimental flag to be used. To explicitly enable this feature, you can set the experimental flag to:
```
VAGRANT_EXPERIMENTAL="disks"
```
Please note that `VAGRANT_EXPERIMENTAL` is an environment variable. For more
information about this flag visit the [Experimental docs page](/docs/experimental/)
for more info. Without this flag enabled, any disks defined will not be configured.
</div>
For examples of how to use the disk feature with VirtualBox, please refer to the
[general disk usage guide](/docs/disks/usage.html) for more examples.
## provider_config options