Closed einsty closed 2 years ago
In my testing this issue NFS will timeout only if you have created the VM before. If this is a completely fresh then the error is:
==> www-mlc.local.ciservers.net: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "ipconfig", "vboxnet3", "--ip", "192.168.0.1", "--netmask", "255.255.255.0"]
Stderr: VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp
The only solution I found is to add a file /etc/vbox/networks.conf
with the contents:
* 10.0.0.0/8 192.168.0.0/16
* 2001::/64
This is the relevant docs page from VirtualBox. https://www.virtualbox.org/manual/ch06.html#network_hostonly
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.
Issue Type
Your Environment
Your OS
Full console output
...
and eventually the infamous
Summary
The range of supported "host only" IP Addresses in VirtualBox 6.1.28 has been reduced. The Drupal VM address of 192.168.88.88 is not in the supported range. It will be a problem when trying to create the NFS share.
https://www.virtualbox.org/manual/ch06.html#network_hostonly
For Discussion / Options
Either modify the default IP address used by Drupal VM to be in the 192.168.56.0/21 range, and/or add a lot of heads up about this issue.
I did find that by using an IP address of say 192.168.57.57 (as an example) I no longer had any trouble with the NFS shares being mounted.