VirtualBox

Ticket #12182 (reopened defect)

Opened 6 months ago

Last modified 3 days ago

Failed to create the host network interface => Fixed in SVN

Reported by: wwirthtorres Owned by:
Priority: major Component: network
Version: VirtualBox 4.3.0 Keywords: host only adapter
Cc: Guest type: Windows
Host type: Windows

Description

I have two VMs that worked properly on v4.2.6. I upgraded vbox to 4.3 today and now can only start-up the VMs if I have a Bridged Adapter. The Host-Only adapter has defaults of IP: 0.0.0.0, Subnet 0.0.0.0 and will not save any changes (I tried updating to 192.168.56.1 and 255.255.255.0). When that didn't work I tried deleting and recreating the Host-Only adapter and received this error:

Failed to create the host network interface.

Assertion 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,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0034).

Please contact the product vendor!.

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

Although the adapter deleted here, as soon as I restarted Vbox, the default Host-only adapter was back. These VMs are a lab build that must be separated completely from both the internal network and the internet.

Change History

comment:1 Changed 6 months ago by wwirthtorres

Resolved by uninstalling VBox, rebooting, reinstalling VBox, rebooting.

When I upgraded to 4.3, I did not uninstall 4.2 first. Additionally, the 4.3 install did not require a restart after upgrading; however, I rebooted the system as part of troubleshooting with no results. The only fix that worked was to start from scratch.

comment:2 Changed 6 months ago by Jailout2000

I was also having this issue when I upgraded from 4.2.18 to 4.3. Host operating system is Windows 7 Home Premium x64. I will try the steps mentioned in comment 1.

comment:3 Changed 6 months ago by akshah123

I have the same problem. However, uninstalling Vbox, rebooting, reinstalling Vbox and rebooting doesn't work.

comment:4 Changed 6 months ago by dlech

Same error here. Was able to fix by uninstalling, rebooting, and reinstalling. Did not have to reboot again after the reinstall. The issue appears to be with the installation of the host-only network interface in Windows. When I first installed 4.3, I noticed that I no longer had the "VirtualBox Host-Only Ethernet Adapter" in "Control Panel\Network and Internet\Network Connections".

comment:5 Changed 6 months ago by pauloelr

An issue on the Vagrant repository om GitHub seens to be related with this one too:  https://github.com/mitchellh/vagrant/issues/2392#issuecomment-26885297

comment:6 Changed 5 months ago by dopry

This seems to still be an issue with virtual box. running into tonight on windows 8.1 w/ virtual box 4.3.2.

comment:7 Changed 5 months ago by AlexSell

Problem persists since v.4.3.0 and is a BIG issue on Windows. It has been reported on Win7 up to Win8.1 (all 64bit) versions.

Symptoms: after clean-install (with uninstall, reboot, install, reboot) of any VBox version >= 4.3.0, the host-only network interface can only be deleted, but when created, the application throws the error mentioned in the ticket. It doesn't matter if the interface is created via GUI or directly via VBoxManage (thus making it even more annoying for Vagrant users).

Despite the error, VBox seems to create the network interface correctly (a restart of the GUI shows the new interface in place.

Re-installing didn't help on my system. Also it seems like the installation works as expected, all default network interfaces are there after.

Relevant system information below (all device drivers are recent):

System Information report written at: 11/06/13 08:23:45
System Name: -
[System Summary]

Item	Value	
OS Name	Microsoft Windows 8.1 Pro	
Version	6.3.9600 Build 9600	
Other OS Description 	Not Available	
OS Manufacturer	Microsoft Corporation	
System Name	-	
System Manufacturer	SAMSUNG ELECTRONICS CO., LTD.	
System Model	900X3C/900X3D/900X3E/900X4C/900X4D	
System Type	x64-based PC	
System SKU	System SKUNumber	
Processor	Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz, 1701 Mhz, 2 Core(s), 4 Logical Processor(s)	
BIOS Version/Date	Phoenix Technologies Ltd. P09ABK, 07.10.2013	
SMBIOS Version	2.7	
Embedded Controller Version	255.255	
BIOS Mode	UEFI	
BaseBoard Manufacturer	SAMSUNG ELECTRONICS CO., LTD.	
BaseBoard Model	Not Available	
BaseBoard Name	Base Board	
Platform Role	Mobile	
Secure Boot State	On	
PCR7 Configuration	Binding Not Possible	
Windows Directory	C:\WINDOWS	
System Directory	C:\WINDOWS\system32	
Boot Device	\Device\HarddiskVolume1	
Locale	Germany	
Hardware Abstraction Layer	Version = "6.3.9600.16408"	
User Name	-\-	
Time Zone	W. Europe Standard Time	
Installed Physical Memory (RAM)	4,00 GB	
Total Physical Memory	3,63 GB	
Available Physical Memory	1,80 GB	
Total Virtual Memory	4,07 GB	
Available Virtual Memory	1,91 GB	
Page File Space	448 MB	
Page File	C:\pagefile.sys	
Hyper-V - VM Monitor Mode Extensions	Yes	
Hyper-V - Second Level Address Translation Extensions	Yes	
Hyper-V - Virtualization Enabled in Firmware	Yes	
Hyper-V - Data Execution Protection	Yes	

[Hardware Resources]



[Conflicts/Sharing]

Resource	Device	
Memory Address 0xF0600000-0xF0601FFF	Intel(R) Centrino(R) Advanced-N 6235	
Memory Address 0xF0600000-0xF0601FFF	Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 1 - 1E10	
		
I/O Port 0x00000000-0x0000001F	Direct memory access controller	
I/O Port 0x00000000-0x0000001F	PCI Express Root Complex	
		
I/O Port 0x00002000-0x000020FF	Realtek PCIe GBE Family Controller	
I/O Port 0x00002000-0x000020FF	Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 4 - 1E16	
		
I/O Port 0x00000070-0x00000070	Motherboard resources	
I/O Port 0x00000070-0x00000070	System CMOS/real time clock	
		
Memory Address 0xF0400000-0xF0403FFF	Realtek PCIe GBE Family Controller	
Memory Address 0xF0400000-0xF0403FFF	Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 4 - 1E16	
		
Memory Address 0xFF000000-0xFFFFFFFF	Motherboard resources	
Memory Address 0xFF000000-0xFFFFFFFF	Intel(R) 82802 Firmware Hub Device	
		
IRQ 16	Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 1 - 1E10	
IRQ 16	Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 5 - 1E18	
		
I/O Port 0x00005000-0x00005003	Motherboard resources	
I/O Port 0x00005000-0x00005003	Motherboard resources	
		

[DMA]

Resource	Device	Status	
Channel 4	Direct memory access controller	OK	

[Forced Hardware]

Device	PNP Device ID	

[I/O]

Resource	Device	Status	
0x0000002E-0x0000002F	Motherboard resources	OK	
0x0000004E-0x0000004F	Motherboard resources	OK	
0x00000061-0x00000061	Motherboard resources	OK	
0x00000063-0x00000063	Motherboard resources	OK	
0x00000065-0x00000065	Motherboard resources	OK	
0x00000067-0x00000067	Motherboard resources	OK	
0x00000070-0x00000070	Motherboard resources	OK	
0x00000070-0x00000070	System CMOS/real time clock	OK	
0x00000080-0x00000080	Motherboard resources	OK	
0x00000092-0x00000092	Motherboard resources	OK	
0x000000B2-0x000000B3	Motherboard resources	OK	
0x00000680-0x0000069F	Motherboard resources	OK	
0x00001000-0x0000100F	Motherboard resources	OK	
0x00005000-0x00005003	Motherboard resources	OK	
0x00005000-0x00005003	Motherboard resources	OK	
0x0000FFFF-0x0000FFFF	Motherboard resources	OK	
0x00000400-0x00000453	Motherboard resources	OK	
0x00000458-0x0000047F	Motherboard resources	OK	
0x00000500-0x0000057F	Motherboard resources	OK	
0x00000A00-0x00000A0F	Motherboard resources	OK	
0x0000164E-0x0000164F	Motherboard resources	OK	
0x00000062-0x00000062	Microsoft ACPI-Compliant Embedded Controller	OK	
0x00000066-0x00000066	Microsoft ACPI-Compliant Embedded Controller	OK	
0x00000020-0x00000021	Programmable interrupt controller	OK	
0x00000024-0x00000025	Programmable interrupt controller	OK	
0x00000028-0x00000029	Programmable interrupt controller	OK	
0x0000002C-0x0000002D	Programmable interrupt controller	OK	
0x00000030-0x00000031	Programmable interrupt controller	OK	
0x00000034-0x00000035	Programmable interrupt controller	OK	
0x00000038-0x00000039	Programmable interrupt controller	OK	
0x0000003C-0x0000003D	Programmable interrupt controller	OK	
0x000000A0-0x000000A1	Programmable interrupt controller	OK	
0x000000A4-0x000000A5	Programmable interrupt controller	OK	
0x000000A8-0x000000A9	Programmable interrupt controller	OK	
0x000000AC-0x000000AD	Programmable interrupt controller	OK	
0x000000B0-0x000000B1	Programmable interrupt controller	OK	
0x000000B4-0x000000B5	Programmable interrupt controller	OK	
0x000000B8-0x000000B9	Programmable interrupt controller	OK	
0x000000BC-0x000000BD	Programmable interrupt controller	OK	
0x000004D0-0x000004D1	Programmable interrupt controller	OK	
0x00000454-0x00000457	Motherboard resources	OK	
0x00000000-0x0000001F	Direct memory access controller	OK	
0x00000000-0x0000001F	PCI Express Root Complex	OK	
0x00000081-0x00000091	Direct memory access controller	OK	
0x00000093-0x0000009F	Direct memory access controller	OK	
0x000000C0-0x000000DF	Direct memory access controller	OK	
0x00000060-0x00000060	Standard PS/2 Keyboard	OK	
0x00000064-0x00000064	Standard PS/2 Keyboard	OK	
0x000000F0-0x000000F0	Numeric data processor	OK	
0x00002000-0x000020FF	Realtek PCIe GBE Family Controller	OK	
0x00002000-0x000020FF	Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 4 - 1E16	OK	
0x00000D00-0x0000FFFF	PCI Express Root Complex	OK	
0x00000040-0x00000043	System timer	OK	
0x00000050-0x00000053	System timer	OK	
0x00003000-0x0000303F	Intel(R) HD Graphics 4000	OK	
0x00003088-0x0000308F	Intel(R) 7 Series Chipset Family SATA AHCI Controller	OK	
0x00003094-0x00003097	Intel(R) 7 Series Chipset Family SATA AHCI Controller	OK	
0x00003080-0x00003087	Intel(R) 7 Series Chipset Family SATA AHCI Controller	OK	
0x00003090-0x00003093	Intel(R) 7 Series Chipset Family SATA AHCI Controller	OK	
0x00003060-0x0000307F	Intel(R) 7 Series Chipset Family SATA AHCI Controller	OK	
0x0000EFA0-0x0000EFBF	SAMSUNG SMBus Driver	OK	

comment:8 Changed 5 months ago by frank

We think we found and fixed the issue. Please could you check if  this test build fixes the problem with creating the host-only network interfaces? Thank you!

comment:9 Changed 5 months ago by AlexSell

I can confirm following things working now in VBox version 4.3.3 build 90468 on Win8.1 64bit:

  • Adding and deleting host-only interfaces in VBox GUI (user and elevated mode): no errors
  • Adding and deleting host-only interfaces via VBoxManage (user and elevated mode): no errors

Nice one, thank you for your quick response! :-)

Last edited 5 months ago by AlexSell (previous) (diff)

comment:10 Changed 5 months ago by frank

  • Summary changed from Failed to create the host network interface to Failed to create the host network interface => Fixed in SVN

Thank you for the feedback! Of course this fix will be included in the next maintenance release. No release date yet but it will not take months.

comment:11 Changed 5 months ago by shallal

didn't work for me on windows 7 64bit

comment:12 Changed 5 months ago by frank

shallal, in that case I guess you have a different problem. Please describe what you experience and attach log files. You cannot experience the problem as described in the subject because this was definitely fixed in the test build (see comment 8).

comment:13 follow-up: ↓ 15 Changed 5 months ago by shallal

D:\Oracle\Vbox>VBoxManage.exe hostonlyif create bla --ip 192.168.1.1 --netmask 2 55.255.255.0 0%... Progress state: E_FAIL VBoxManage.exe: error: Failed to create the host-only adapter VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended in fo not available) VBoxManage.exe: error: Context: "int cdecl handleCreate(struct HandlerArg *,in t,int *)" at line 66 of file VBoxManageHostonly.cpp

comment:14 Changed 5 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in 4.3.4.

comment:15 in reply to: ↑ 13 Changed 4 months ago by FirewallEngineer

Replying to shallal:

D:\Oracle\Vbox>VBoxManage.exe hostonlyif create bla --ip 192.168.1.1 --netmask 2 55.255.255.0 0%... Progress state: E_FAIL VBoxManage.exe: error: Failed to create the host-only adapter VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended in fo not available) VBoxManage.exe: error: Context: "int cdecl handleCreate(struct HandlerArg *,in t,int *)" at line 66 of file VBoxManageHostonly.cpp

I’m experiencing the same issue even though I’ve downloaded and installed the latest one.  http://download.virtualbox.org/virtualbox/4.3.6/VirtualBox-4.3.6-91406-Win.exe

 http://firewallengineer.wordpress.com/2013/12/26/problem-virtualbox-failed-to-create-the-host-network-interface/

comment:16 follow-up: ↓ 20 Changed 4 weeks ago by David.Requena

  • Status changed from closed to reopened
  • Resolution fixed deleted

Sorry to bother but this is not fixed as of 4.3.8.r92456 on Windows 7 Pro x64

VBoxManage hostonlyif create "vbho" --ip 10.0.200.1
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "int __cdecl handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHostonly.cpp

comment:17 Changed 4 weeks ago by frank

  • Priority changed from blocker to major

This must be a different problem. Are you sure that you installed the host-only driver when you installed VirtualBox?

comment:18 Changed 4 weeks ago by David.Requena

I definitely did install it. In fact going back to 4.2.24 and creating some h/o adapter allows its use after upgrading to any 4.3.x release. Said adapter can be removed in 4.3.x but not modified. Under no circunstance can it be re-created.

Please let me know if I should open a new issue. It's definitely the same one reported by @FirewallEngineer above however.

comment:19 Changed 2 weeks ago by chriscupas

Resolved it by going to virtualbox manager and

File -> Preferences -> Network -> Host-only Networks -> Add host-only network (icon)

comment:20 in reply to: ↑ 16 Changed 4 days ago by Markl8

Replying to David.Requena:

Sorry to bother but this is not fixed as of 4.3.8.r92456 on Windows 7 Pro x64

VBoxManage hostonlyif create "vbho" --ip 10.0.200.1
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "int __cdecl handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHostonly.cpp

Exactly the same problem and message with windows 8.1 pro 64-bits and virtual box 4.3.10 R39012.

Did you found any solution?

comment:21 Changed 4 days ago by mrlindsey

Same problem in Windows 7 64-bit on 4.3.10 R39012. Thanks.

comment:22 Changed 3 days ago by Duck Asteroid

VBox 4.3.10r93012 On Windows 8.1 64 bit:

VBoxManage hostonlyif create -vbho- --ip 10.0.200
.10%...
Progress state- E_FAIL
VBoxManage.exe- error- Failed to create the host-only adapter
VBoxManage.exe- error- Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe- error- Context- -int __cdecl handleCreate(struct HandlerArg -,int,int -)- at line 66 of file VBoxManageHostonly.cpp
Last edited 3 days ago by Duck Asteroid (previous) (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use