Host networking dies when VBoxSvc reconfigures n/w adapters
Posted: 21. Sep 2015, 14:53
I have some experience of using VirtualBox and have usually managed to find solutions or workarounds to issues I have encountered, but this one has me stumped. I am using VB to bring up Vagrant boxes, but am convinced this is an issue with VB itself, or its network drivers. I am currently using version 5.0.4, but had the same issue with v4.3.30.
I am trying to reproduce a Vagrant cluster on a Windows 8 (not 8.1) host, guest OS is CentOS 6.5. I can't post URLs yet, but Google 'dnafrance vagrant-hadoop-spark-cluster' (without quotes) to find details on GitHub.
When 'vagrant up' is invoked, all is well until the script tries to reconfigure a VM's networking. It tries to set up Adapter 1 as NAT and Adapter 2 as host only, apparently using VBoxSvc. This appears to be successful, but has two side effects:
1) Every time the script is run, a new instance of the "VirtualBox Host-Only Network" adapter is brought into being. These are named "VirtualBox Host-Only Network #2", "... #3" etc.
2) When the new adapter instance comes into being, the host loses its external network connections, whether wired or wireless. At the very least, DNS Lookup is lost, as I found that a ping connection to an external server will continue to be connected while the new adapter pops into being, but if the ping is then stopped and restarted, it fails to connect to the server. nslookup also fails to produce a result. The only way I have found to bring the networking back is to reboot the host.
I have tried running the script both as a normal user and as Administrator to no avail. The issue appears to be similar to others found on the web, but I am at a loss. Any help you can offer would be gratefully received.
I am trying to reproduce a Vagrant cluster on a Windows 8 (not 8.1) host, guest OS is CentOS 6.5. I can't post URLs yet, but Google 'dnafrance vagrant-hadoop-spark-cluster' (without quotes) to find details on GitHub.
When 'vagrant up' is invoked, all is well until the script tries to reconfigure a VM's networking. It tries to set up Adapter 1 as NAT and Adapter 2 as host only, apparently using VBoxSvc. This appears to be successful, but has two side effects:
1) Every time the script is run, a new instance of the "VirtualBox Host-Only Network" adapter is brought into being. These are named "VirtualBox Host-Only Network #2", "... #3" etc.
2) When the new adapter instance comes into being, the host loses its external network connections, whether wired or wireless. At the very least, DNS Lookup is lost, as I found that a ping connection to an external server will continue to be connected while the new adapter pops into being, but if the ping is then stopped and restarted, it fails to connect to the server. nslookup also fails to produce a result. The only way I have found to bring the networking back is to reboot the host.
I have tried running the script both as a normal user and as Administrator to no avail. The issue appears to be similar to others found on the web, but I am at a loss. Any help you can offer would be gratefully received.