VirtualBox 5.0.4 r102546 inaccessible from Windows 8.1 host

[jamieburchell]

Hi

Since upgrading to VirtualBox 5.0.4 my host is unable to access the guest at 192.168.33.10 (ping, h ttp etc) after the guest has been started and shutdown once. The guest can ping my host machine and access the internet at all times.

I tried downgrading to 5.0.2 and this seems to resolve the issue, before that, the last release of 4.3.30 also worked fine.

The host OS is Windows 8.1, I am using Vagrant 1.7.4 (running as Administrator) and the guest OS is CentOS 6.6 with the latest Guest Additions.

In 5.0.4 the network configuration for the box is: Adapter 1 (NAT), Adapter 2 (Host-only Adapter - VirtualBox Host-Only Ethernet Adapter #6).
In 5.0.2 the network configuration for the box is: Adapter 1 (NAT), Adapter 2 (Host-only Adapter - VirtualBox Host-Only Ethernet Adapter #2).

I don't know if that means the issue is that the wrong adapter is being used?

I can SSH in to the guest on 127.0.0.1:2222 because of the port forwarding rule that is set on Adapter #1.

Things I've tried:

• Disabled Windows firewall
  Disabled iptables firewall
  Uncheck/check IP V6 on all adapters
  Don't install the "Brige" adapter during installation
  Uninstalling/reinstalling (curiously it works the first time, then not)
  Reboots of host.
  Don't upgrade Guest Additions

Pretty much wasted a day on this. Any help appreciated.

EDIT: I may have semi-answered my own question. Manually changing Adapter #2 to Host-only Adapter - VirtualBox Host-Only Ethernet Adapter #2 from Host-only Adapter - VirtualBox Host-Only Ethernet Adapter #6 when the guest has booted seems to resolve the issue. I guess my question now is why does 5.0.4 select adapter #6 and how can I change the default behaviour (this might be outside the remit of this forum as I am using Vagrant shell provisioning to bring the box up).

EDIT 2: It seems that each time Vagrant reboots the machine a new VirtualBox Host-only Ethernet Adapter is created and set as the default. I have to keep changing it back to #2 :/

Thanks

[noteirak]

Try installing the NDIS5 driver during VirtualBox install:

The user is able to choose between NDIS5 and NDIS6 host network filters drivers during the installation. This is realized via a command line parameter NETWORKTYPE. The NDIS6 driver is default for Windows Vista and later. For older Windows versions, the installer will automatically select the NDIS5 driver and this cannot be changed. For Windows Vista and later the user can force to install the (legacy) NDIS5 host network filter driver using NETWORKTYPE=NDIS5. For example, to install the NDIS5 driver on Windows 7, do

VirtualBox.exe -msiparams NETWORKTYPE=NDIS5

[jamieburchell]

Excellent, thank you! This seems to have resolved the issue where a new "VirtualBox Host-Only Ethernet Adapter" is created and selected on each boot.

I'm curious if this is just a bug in 5.0.4 that needs fixing?

Thanks again.

[jamieburchell]

Looks like I spoke too soon. It hasn't made a lasting difference, I'm currently up to VirtualHost Adapter #16 and counting.

[loukingjr]

Try installing VB 5.0.6 if you haven't already.

[jamieburchell]

Tried 5.0.6 this morning, all seemed OK. After several vagrant up and vagrant halt the expected two network adapters were in use. Excellent I thought. Then I rebooted the host and tried again and the network adapter list is growing again on each vagrant up, selecting the wrong one each time.

Here's the log file http://pastebin.com/w7GY9J7t

On this bootup, yet another Host Only Ethernet Adapter was created and selected (#4).

[loukingjr]

Two things worth noting, Vagrant isn't supported here and you can attach log files to your posts. If they are too large you can zip them.

[jamieburchell]

OK, point taken. I wasn't sure if using Vagrant was relevant to the issue (especially since a previous version of VirtualBox and the same Vagrant version does not do this), but I have since found that I can cure this problem by adding the following in to my vagrant configuration file. I appreciate it's not supported, but I'll post this here incase someone else has the same issue:

Force the adapter to use:

Code: Select all

config.vm.network "private_network", ip: "192.168.33.10", name: "VirtualBox Host-Only Ethernet Adapter #2"

Now, why this is suddenly necessary with VirtualBox 5, I'm not sure.

Cheers
Jamie