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/virtualbox%2Fcommon-issues.html | 6 ------ 1 file changed, 6 deletions(-) delete mode 100644 devdocs/vagrant/virtualbox%2Fcommon-issues.html (limited to 'devdocs/vagrant/virtualbox%2Fcommon-issues.html') diff --git a/devdocs/vagrant/virtualbox%2Fcommon-issues.html b/devdocs/vagrant/virtualbox%2Fcommon-issues.html deleted file mode 100644 index 83185b6b..00000000 --- a/devdocs/vagrant/virtualbox%2Fcommon-issues.html +++ /dev/null @@ -1,6 +0,0 @@ -

Common Issues

This page lists some common issues people run into with Vagrant and 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. 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.

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.

DNS Not Working

If DNS is not working within your VM, then you may need to enable a DNS proxy (built-in to VirtualBox). Please see the StackOverflow answers here for a guide on how to do that.

-

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

-
-- cgit v1.2.3