2014-03-13 01:33:36 +00:00
|
|
|
---
|
2016-01-19 18:08:53 +00:00
|
|
|
layout: "docs"
|
2014-03-13 01:33:36 +00:00
|
|
|
page_title: "Common Issues - VirtualBox Provider"
|
2016-01-19 18:08:53 +00:00
|
|
|
sidebar_current: "providers-virtualbox-issues"
|
|
|
|
|
description: |-
|
|
|
|
|
This page lists some common issues people run into with Vagrant and VirtualBox
|
|
|
|
|
as well as solutions for those issues.
|
2014-03-13 01:33:36 +00:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Common Issues
|
|
|
|
|
|
2016-01-19 18:08:53 +00:00
|
|
|
This page lists some common issues people run into with Vagrant and VirtualBox
|
|
|
|
|
as well as solutions for those issues.
|
2014-03-13 01:33:36 +00:00
|
|
|
|
|
|
|
|
## 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.
|
2015-07-07 05:22:22 +00:00
|
|
|
|
|
|
|
|
## 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
|
2016-01-19 18:08:53 +00:00
|
|
|
here](https://serverfault.com/questions/453185/vagrant-virtualbox-dns-10-0-2-3-not-working)
|
2015-07-07 05:22:22 +00:00
|
|
|
for a guide on how to do that.
|
