You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to share a folder from the OSX host to an Android(-x86) guest in Virtualbox. However I have hit a wall with trying to make it a bit more robust with regards to guest IPs. I have VM set up to obtain an IP address from the VirtualBox DHCP server, so I would like to specify the following rules:
With this, I can't access the share even from 172.28.128.3 machine. If I remove the IP address, I can mount a share just fine. Note that if I reload, I then get an exports check error
exports:2: can't specify both network and hosts on same line
I am not above writing an Android guest definition, but this would need to be deployed to all vagrant installations we have. It would be great if we could just drop the IP address for BSD NFS shares if network is specified. Although this is less secure, it is all on a host-only network, and context is a single-user machine, so this does not present a security issue for us.
The text was updated successfully, but these errors were encountered:
Removing the IP from the exports isn't a wide enough needed a feature to warrant doing it right now given how invasive it would be to every guest. I don't understand the problem here... what makes Android different from any other guest with this? Every other guest works fine with an IP there, why not Android?
I am trying to share a folder from the OSX host to an Android(-x86) guest in Virtualbox. However I have hit a wall with trying to make it a bit more robust with regards to guest IPs. I have VM set up to obtain an IP address from the VirtualBox DHCP server, so I would like to specify the following rules:
However, when I up, I hit the following error:
I tried setting an IP address to private nework:
However, then this IP address gets passed to the nfs exports template, and in the /etc/exports I get
With this, I can't access the share even from 172.28.128.3 machine. If I remove the IP address, I can mount a share just fine. Note that if I reload, I then get an exports check error
I am not above writing an Android guest definition, but this would need to be deployed to all vagrant installations we have. It would be great if we could just drop the IP address for BSD NFS shares if network is specified. Although this is less secure, it is all on a host-only network, and context is a single-user machine, so this does not present a security issue for us.
The text was updated successfully, but these errors were encountered: