haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

website/docs: doc windows gotcha [GH-3170]

This commit is contained in:
Mitchell Hashimoto 2014-03-12 18:33:36 -07:00
parent dac6ae9310
commit 9b5d262e29
2 changed files with 23 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
website/docs/source/layouts/layout.erb
View File

@ -216,6 +216,7 @@
<li<%= sidebar_current("virtualbox-usage") %>><a href="/v2/virtualbox/usage.html">Usage</a></li>
<li<%= sidebar_current("virtualbox-boxes") %>><a href="/v2/virtualbox/boxes.html">Creating a Base Box</a></li>
<li<%= sidebar_current("virtualbox-configuration") %>><a href="/v2/virtualbox/configuration.html">Configuration</a></li>
<li<%= sidebar_current("virtualbox-issues") %>><a href="/v2/virtualbox/common-issues.html">Common Issues</a></li>
</ul>
<% end %>

22
website/docs/source/v2/virtualbox/common-issues.html.md Normal file
View File

@ -0,0 +1,22 @@
---
page_title: "Common Issues - VirtualBox Provider"
sidebar_current: "virtualbox-issues"
---
# Common Issues
This page lists some common issues people run into with VirtualBox as well
as solutions for those issues.
## Hanging on Windows
If Vagrant commands are hanging on Windows because they're communicating
to VirtualBox, this may be caused by a permissions issue with VirtualBox.
This is easy to fix. Start VirtualBox as a normal user or as an
administrator will prevent you from using it in the opposite way. Please keep
in mind that when Vagrant interacts with VirtualBox, it will interact with
it with the same access level as the console running Vagrant.
To fix this issue, completely shut down all VirtualBox machines and GUIs.
Wait a few seconds. Then, launch VirtualBox only with the access level you
wish to use.