v5.0.0 RC3 Unable to install/use Bridged Adapter Network

[pcf]

Hello,

Background:
+ Host machine is running Windows 8.1 Pro 64-bit with all the latest Windows Updates (Critical, Important and Optional).
+ Host machine utilizes an Intel I217-V NIC with Intel's latest v20.1 drivers (https://downloadcenter.intel.com/produc ... ion-I217-V).
+ I've installed VirtualBox v5.0.0 RC3 (VirtualBox-5.0.0_RC3-101436-Win.exe).
+ Installer + Driver installation logs are attached to this post (followed the instruction guide here: https://www.virtualbox.org/wiki/MSI_Logging).
- setupapi.log is not included as I don't see one present in C:\Windows nor C:\Windows\Inf.

The issues:
1. VirtualBox's Bridged Network Adapter does not appear to be installed on my host machine, even though it clearly selected during the installation process.
Here's the end result in the host machine's Network Connections window:


2. After VirtualBox's installation, my host machine's NIC appears to be in a disabled state (as seen in the image above).
However, when I open my host machine's Device Manager, my host machine's NIC doesn't appear to be disabled (I can actually select 'Disable' from the context menu):

Furthermore, I still have have access to both physical machines on my physical network and the Internet.

3. When I select Bridged Adapter, (like so: http://i.imgur.com/50Qa381.png) and then proceed to turn on a VM, even an empty one that hasn't got an OS installed on it yet, I'm presented with the following error:

Or in text form:

Code: Select all

Failed to open a session for the virtual machine Windows 2012 R2 #3.

Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Ethernet Connection I217-V' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Additional, possible references:
https://www.virtualbox.org/ticket/13481

Help is appreciated. Regards,

[mpack]

Did this work with previous Windows versions? I.e. is this a regression?

[pcf]

Hello and thank you for the prompt reply.

I have no idea as the last time I've used VirtualBox it was on a whole other Host machine that's no longer at my disposal.


Regards,

[pcf]

Apologies for double-bump.

I've added another piece of information to Issue #2 in the original post:
2. After VirtualBox's installation, my host machine's NIC appears to be in a disabled state.
However, when I open my host machine's Device Manager, my host machine's NIC doesn't appear to be disabled (I can actually select 'Disable' from the context menu):

Furthermore, I still have have access to both physical machines on my physical network and the Internet.

[vvp]

all looks normal from the attached logs at first glance. You put all lines related to Virtualbox from setupapi.api.log and setupapi.dev.log, didn't you?
And after reboot nothing was changed, wasn't it?

Can you show a networking window "Ethernet properties->Networking" where should be displayed vbox bridge network adapter?
is adapter there?

Also, it is useful to run "sc query vboxnetlwf" and look on the status of driver (running/stopped).

p.s. I see that your oem files for netadp and neetlwf have the big values 80 and 81. How many other oem files exist in Windows\inf directory?

[pcf]

Before I reply to vvp's post above me, I'd like to note that I've also just tried the following on the host machine:
1. Uninstalled VirtualBox.
2. Uninstalled the drivers for my Intel NIC (Windows reverted to it's built-in drivers).
3. Rebooted.
4. Via an elevated Command Prompt, ran the following commands:

Code: Select all

ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int ipv4 reset
netsh int ipv6 reset
netsh winsock reset

5. Rebooted.
6. Installed the latest drivers for my Intel NIC.
7. Rebooted.
8. Installed VirtualBox.
9. Rebooted.
Same results.

BTW: I might try this tool as well, just haven't gotten around to it yet: https://support.microsoft.com/en-us/kb/299357

all looks normal from the attached logs at first glance.
..
..

Hello,

1. Yes. I haven't stripped out anything out of the log files.

2. After multiple reboots nothing has changed.

3. What do you mean by "Ethernet Properties->Networking Window"?
I've posted in my OP the follow screenshot, did you refer to that?


4. 'sc query vboxnetlwf' results:

Or in text form:

Code: Select all

SERVICE_NAME: vboxnetlwf
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

5. My host machine's 'oemxx.inf' enumeration goes up to 'oem86.inf'.

Regards,

[vvp]

3. What do you mean by "Ethernet Properties->Networking Window"?
I've posted in my OP the follow screenshot, did you refer to that?

No, i didn't. I mean clicking on Ethernet in those window, it's opened "Ethernet status" window, then click "Property" button and it'll be opened "Ethernet properties" window.
Is the vbox bridge driver there in the list?

4. 'sc query vboxnetlwf' results:

Or in text form:

Code: Select all

SERVICE_NAME: vboxnetlwf
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

This picture demonstrates that bridge driver (vboxnetlwf) works.
Would you upload here a starting log of your VM? click on VM and click on "show log", copy and save the latest log.

5. My host machine's 'oemxx.inf' enumeration goes up to 'oem86.inf'.

It was question about some leftovers (how many those files are really used, oem79, oem78...oem1) existing in your system, which can interfere some way with actual(latest) bridge driver.

[pcf]

Hello vvp. Thank you for following-up with me.

1. I now understand what you were asking for, thank you.
Yes, the VBox Bridged Networking driver does appear in the list and is enabled, in both instances:
VirtualBox Host-Only Ethernet Adapter: http://i.imgur.com/cgBB06x.png
Intel Ethernet Connection I217-V: http://i.imgur.com/4L5VWaK.png

2. Certainly. I've zipped VBoxSVC.log + selectorwindow.log to this post.


Regards,

[vvp]

you posted the wrong log, i asked about VM log not about VirtualBox COM Server log. Click on your VM in GUI select item "show log" from pop up menu.

I have just created an empty VM with type Win8.1. set bridged network. and run it. Of course, without bootable disk VM can't start, but some steps were done before anyway.
from my VM log:

VirtualBox VM 5.0.0_RC3 r101436 win.amd64 (Jul 3 2015 15:19:20) release log
00:00:11.764450 Log opened 2015-07-06T13:45:57.428268500Z
00:00:11.764451 Build Type: release
00:00:11.764454 OS Product: Windows 8.1
00:00:11.764456 OS Release: 6.3.9600
00:00:11.764456 OS Service Pack:
00:00:11.796699 DMI Product Name: Ultra 24
00:00:11.799682 DMI Product Version: 0.00.01
00:00:11.799686 Host RAM: 8126MB total, 4557MB available
00:00:11.799688 Executable: F:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:11.799689 Process ID: 6824
00:00:11.799689 Package type: WINDOWS_64BITS_GENERIC
00:00:11.804682 Installed Extension Packs:
00:00:11.804738 Oracle VM VirtualBox Extension Pack (Version: 5.0.0_BETA2 r99648; VRDE Module: VBoxVRDP unusable because of 'Failed to load the main module ('F:\Program Files\Oracle\VirtualBox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/win.amd64/VBoxPuelMain.DLL'): VERR_SYMBOL_NOT_FOUND - GetLastError=127')
00:00:11.807711 Console: Machine state changed to 'Starting'
00:00:11.910198 SUP: Loaded VMMR0.r0 (F:\Program Files\Oracle\VirtualBox\VMMR0.r0) at 0xfffff801cd07d000 - ModuleInit at fffff801cd09e390 and ModuleTerm at fffff801cd09e680 using the native ring-0 loader
00:00:11.910224 SUP: VMMR0EntryEx located at fffff801cd09fb80, VMMR0EntryFast at fffff801cd09ead0 and VMMR0EntryInt at fffff801cd09eac0
00:00:11.910231 SUP: windbg> .reload /f F:\Program Files\Oracle\VirtualBox\VMMR0.r0=0xfffff801cd07d000
00:00:11.914288 Guest OS type: 'Windows81_64'
00:00:11.916500 Installed Drivers:
00:00:11.921051 F:\Windows\system32\DRIVERS\VBoxUSBMon.sys (Version: 5.0.0.1436)
00:00:11.927985 F:\Windows\system32\DRIVERS\VBoxDrv.sys (Version: 5.0.0.1436)
00:00:11.930049 F:\Windows\system32\DRIVERS\VBoxNetAdp6.sys (Version: 5.0.0.1436)
00:00:11.932344 F:\Windows\system32\DRIVERS\VBoxNetLwf.sys (Version: 5.0.0.1436)
00:00:11.932881 Enabling CMPXCHG16B for Windows 8.1 / 2k12 or newer guests
00:00:11.933008 fHMForced=true - 64-bit guest
00:00:11.950536 File system of 'F:\Users\valery\VirtualBox VMs\empty machine win8.1\Snapshots' (snapshots) is unknown
00:00:11.950550 File system of 'F:\Users\valery\VirtualBox VMs\empty machine win8.1\empty machine win8.1.vdi' is ntfs
00:00:12.414690 Shared clipboard service loaded
00:00:12.414709 Shared clipboard mode: Off
00:00:12.420862 Drag and drop service loaded
00:00:12.420872 Drag and drop mode: Off
00:00:12.431836 Guest Control service loaded

[pcf]

Oh I see now.

Cool, I've zipped and attached it to this post: Windows 2012 R2 #3-2015-07-06-17-22-32.zip.


Regards,

[vvp]

there is next line in your log at least:

00:00:01.362423 AssertLogRel F:\tinderbox\win-rel\src\VBox\Main\src-client\ConsoleImpl2.cpp(5147) int __cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool): <NULL>
00:00:01.362431 Console::configNetwork: CreateFile failed, err (0x2), ignoring

and other errors that occurred later. Will see why this happened.

[pcf]

Yup. I see.

Again, thank you very much for following-up with me.

Awaiting further instructions from you as to how to proceed.


Regards,
//subscribed to thread.

[vvp]

it should be something simple because it happened only with you at moment.
Did you install Virtualbox as admin, but run as guest?
Does Virtualbox work without your Intel I217-V driver? is it possible to check? i mean you won't install the driver and try to run with some default driver.
Have you installed and run Virtualbox with any VM on this machine before or it was a first installation?

[pcf]

1. A. Yes, I've also tried installing VirtualBox as Administrator (Right click > Run as Administrator).
2. B. My account is the only account on this machine and it's a member of the Administrators group.
I'm not sure if that counts as "Running VirtualBox as Guest". Or does it?
In any case I've also just tried actually running VirtualBox as Administrator. Same results.

2. A. The Intel I217-V NIC is the only physical NIC I have on this machine.
2. B. I have also tried installing VirtualBox while Windows' default driver was present (instead of Intel's latest driver). The results were the same.

3. This is the first time I've tried VirtualBox on this machine as far as I can recall.


Regards,

[loukingjr]

FWIW, I have a ZenBook running Windows 8.1 Professional and have had no problem using Bridged.