virtualbox.org

I have the latest VirtualBox (4.3.2 r90405) running on Windows 7 / SP1 (Intel i5 proc / 8GB ram, etc).
I have several CentOS virtual machines, and I need to set up a host-only network so that:

* the VMs can talk to each other
* the windows host can talk directly to each VM
* the VMs can reach the internet through the host via NAT

I have this exact same set up working beautifully on an OS X host at home, but this is for work so it has to be Windows.

Here's my problem, VirtualBox cannot seem to set up a host-only network interface. I go into the networking preferences and click the button to create a new host-only network, I get the "creating host only network interface" progress bar for a minute or two then I get this message:

Code: Select all

Failed to create teh host network interface.
Asserion failed: [!aGuid.isValid()] at 'D:\tinderbox\win-4.3\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (74) in long_cdecl HostNetworkInterface::init(class com::Bstr,classcom::Bstr,class com::Guid,enum __MIDL____MIDL_itf_VirtualBox_0000_0000_0034)

Please contact the product vendor!.

Details:


Result Code: 
E_FAIL (0x80004005)
Component: 
HostNetworkInterface
Interface: 
IHostNetworkInterface {f6e556f9-d598-409b-898c-8ba99d9b05ae}

note: I do not have a drive D on my system!

I've been googling and poking at this for more than a week and can't seem to find a way around this. Crazy thing is it works perfectly on Mac OS X (even the same VMs!).

So I put it to you, forum gurus ... what is up? How can I fix this?

^^ bump ^^

Make sure the host only ethernet adapter exists (check Device Manager). If it exists then there shouldn't be any need to create any new networks, surely the default one will do. If the adapter doesn't exist then at least one of the following is true :-

You told the VirtualBox installer not to install host-only adapter support .
Your user don't have admin rights.
You installed for the wrong user (e.g. "Admin").
You have Win64's Driver Signature Enforcement feature configured to silently discard non-MS drivers. Note that this feature is separate from the issue of admin rights.

Fix these problems then re-install.

mpack wrote:Make sure the host only ethernet adapter exists (check Device Manager). If it exists then there shouldn't be any need to create any new networks, surely the default one will do. If the adapter doesn't exist then at least one of the following is true :-

You told the VirtualBox installer not to install host-only adapter support .

Your user don't have admin rights.

You installed for the wrong user (e.g. "Admin").

You have Win64's Driver Signature Enforcement feature configured to silently discard non-MS drivers. Note that this feature is separate from the issue of admin rights.
Fix these problems then re-install.

Well ... I'm not sure what the deal was.
I definitely did not turn off host-only in the installer or install as wrong user or without admin rights.
I was not prompted about an unsigned driver on install.

However ... completely uninstalling it, and re-installing seemed to do the trick. As you say, this time after install, the host-only network adapted appeared (it had been missing before -- possibly because I upgraded from a previous version? not sure).

Anyhow, thank you for your help.

virtualbox.org

Host-only Network / can't set up interface on Windows 7

Host-only Network / can't set up interface on Windows 7

Re: Host-only Network / can't set up interface on Windows 7

Re: Host-only Network / can't set up interface on Windows 7

Re: Host-only Network / can't set up interface on Windows 7