blob: 8db55e72ce9534b8f5a3cd42c45fd2a81c2d0e7f [file] [log] [blame]
Victor Moralesd4036482017-08-15 17:54:14 -05001============
2Known Issues
3============
4
5Virtualbox guest additions conflict with shared directories
6-----------------------------------------------------------
7
8If the **vagrant-vbguest** plugin is installed on the host, then an
9updated version of the Virtualbox guest additions will be installed
10on the guest in the /opt directory. Once this projects Vagrantfile
11mounts the ./opt directory on the host to the /opt directory on the
12guest during the provisioning process, the guest addtions on the
13guest are hidden and subsequent mounts of shared directories with the
14host will fail.
15
16The simplest workaround appears to be uninstalling the
17*vagrant-vbguest* plugin on the host system. This has been observed
18to work on a Windows 10 host using virtualbox 5.1.26.
19
20Check if vagrant-vbguest plugin is installed
21
22- Linux or Mac
23
24.. code-block:: console
25
26 $ vagrant plugin list
27.. end
28
29- Windows
30
31.. code-block:: console
32
33 C:\> vagrant plugin list
34.. end
35
36Remove vagrant-vbguest plugin
37
38- Linux or Mac
39
40.. code-block:: console
41
42 $ vagrant plugin uninstall vagrant-vbguest
43.. end
44
45- Windows
46
47.. code-block:: console
48
49 C:\> vagrant plugin uninstall vagrant-vbguest
50.. end
Victor Morales444f4ba2017-11-15 15:01:11 -080051
52
53Network configuration in Windows
54--------------------------------
55
56Some Virtual Machines present a problem in their network configuration so to
57make sure the install will work as it should install the virtualbox from the
58cmd window with the following command:
59
60.. code-block:: console
61
62 c:\downloads\VirtualBox-5.1.20-114628-Win.exe -msiparams NETWORKTYPE=NDIS5
63.. end