new repository

1 files changed, 6 insertions, 0 deletions

diff --git a/devdocs/vagrant/virtualbox%2Fcommon-issues.html b/devdocs/vagrant/virtualbox%2Fcommon-issues.html
new file mode 100644
index 00000000..83185b6b
--- /dev/null
+++ b/devdocs/vagrant/virtualbox%2Fcommon-issues.html
@@ -0,0 +1,6 @@
+<h1 id="common-issues">  Common Issues </h1> <p>This page lists some common issues people run into with Vagrant and VirtualBox as well as solutions for those issues.</p> <h2 id="hanging-on-windows">  Hanging on Windows </h2> <p>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. Starting 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.</p> <p>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.</p> <h2 id="dns-not-working">  DNS Not Working </h2> <p>If DNS is not working within your VM, then you may need to enable a DNS proxy (built-in to VirtualBox). Please <a href="https://serverfault.com/questions/453185/vagrant-virtualbox-dns-10-0-2-3-not-working">see the StackOverflow answers here</a> for a guide on how to do that.</p><div class="_attribution">
+  <p class="_attribution-p">
+    &copy; 2010&ndash;2018 Mitchell Hashimoto<br>Licensed under the MPL 2.0 License.<br>
+    <a href="https://www.vagrantup.com/docs/virtualbox/common-issues.html" class="_attribution-link">https://www.vagrantup.com/docs/virtualbox/common-issues.html</a>
+  </p>
+</div>