More Bridge mode woes

[mwyckoff]

I'm trying to get rid of MS Virtual Server on a client's machine. I've been using VBOX since 1.4 and I've never encountered anything like this. But from looking at other posts, I'm not alone, and I've seen no definitive answer. Scenario: HOST: Server 2003 x64 8 Gb mem, bunches of disk space, 2 NICs. Goal: (achieved using MS Virtual Server)-2 VMs 1) SBS2003 Premium; 2) SBS2003 Member Server. Nothing fancy, just a small office that needs two servers. When I set up VBOX in bridged mode (a must for SBS, no other DHCP allowed, plus running Exchange server so it needs a static IP) the guest won't even start. It gets an error that says "Failed to open/create the internal network....." then "VERR_SUPDRV_COMPONENT_NOT_FOUND" The result code is "E_FAIL 0x80004005".

As an interesting note, I tried several different adapters, and the logs showed that none of them were able to be loaded.

• 00:00:03.473 IntNet#0: szNetwork={HostInterfaceNetworking-LAN Realtek Gigabit} enmTrunkType=3 szTrunk={\DEVICE\{5A845944-0CBE-4AAD-B4EB-AAD721067730}} fFlags=0x0 cbRecv=223232 cbSend=36864
  00:00:03.473 PDM: Failed to construct 'e1000'/0! VERR_SUPDRV_COMPONENT_NOT_FOUND (-3700) - The component factory was not found.
  00:00:03.681 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={0a51994b-cbc6-4686-94eb-d4e4023280e2} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-LAN Realtek Gigabit' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
  00:00:03.681 Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).
  00:00:03.681 Unknown error creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND)} aWarning=false, preserve=false
  00:00:03.685 Power up failed (vrc=VERR_SUPDRV_COMPONENT_NOT_FOUND, rc=E_FAIL (0X80004005))
  
  
  00:00:02.241 IntNet#0: szNetwork={HostInterfaceNetworking-LAN Realtek Gigabit} enmTrunkType=3 szTrunk={\DEVICE\{5A845944-0CBE-4AAD-B4EB-AAD721067730}} fFlags=0x0 cbRecv=223232 cbSend=36864
  00:00:02.241 PDM: Failed to construct 'pcnet'/0! VERR_SUPDRV_COMPONENT_NOT_FOUND (-3700) - The component factory was not found.
  00:00:02.449 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={0a51994b-cbc6-4686-94eb-d4e4023280e2} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-LAN Realtek Gigabit' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
  00:00:02.449 Unknown error creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND)} aWarning=false, preserve=false
  00:00:02.454 Power up failed (vrc=VERR_SUPDRV_COMPONENT_NOT_FOUND, rc=E_FAIL (0X80004005))

Note that the part about "failed to construct" is the only difference. Not sure why, but it doesn't seem to matter which NIC I select. And what does "The component factory was not found." mean????

This happens in 3.0.4, 3.0.8 and 3.0.10.
Running as administrator, so there are no restrictions. It just doesn't work.

I did a complete uninstall and reinstall of various versions, including deleting the .Virtualbox directory, cleaned the registry of all VBOX entries and created a new machine and reinstalled the VB additions. This machine works fine with NAT, even gets an address (when I set it to use DHCP) from the ISP (Comcast) even though the client has 2 static IPs. I know the drivers on the guest are OK, it's something in VBOX. I thought it might be a problem with the NIC, but since NAT works, the bridging itself that seems to be broken. Yes, the VBOX bridging driver is checked on each NIC.

Additional dreck. On different occasions VBOX killed the network on the host. I fixed that by uninstalling VBOX, deleting the NICs and reloading the drivers for the host. I also upgraded the drivers on the host NICs just in case that was the problem. So far, nothing has helped. I've had VBOX running on a number of machines running various versions of Ubuntu Server 64, a laptop running XP and other systems running SBS 2003, XP various service packs, etc. Except when I'm using a cellular modem, I use bridging. With the cellular modem, since it only gets one IP address, I have to use NAT.

It's discouraging to think that I will have to go back to MS Virtual Server, but if it works and VBOX doesn't, there's not much choice.

Any constructive ideas??? Is there a reason to think that going back before 3.0.4 will produce any different results??

[Perryg]

Host Interface has not been used since version 2.?
This is more than likely the problem. It is now Bridged.
You will need to remove the HIF from your host and let VBox handle the bridge and then everything should settle down and work properly.

[mwyckoff]

That's not it. If by HIF you mean the VBOX entry in Device Manager under Network Cards, it was already disabled. Uninstalling it made no difference. Anyway, any time I run a repair on VBOX that adapter gets put back in.

Edit:  Look before leaping. Repair doesn't put the host adapter back. Apparently it's just a new install that puts it there. I've done so many of each I never noticed that repair really didn't repair everything. I wonder what else is leaves out from an original/clean install. [End Edit]

[Perryg]

Well I was reading your post where it was still stating that you where trying to use the HIF and since it is there it has not been removed, or at least it appears to me that it has not been removed.

Usually when this happens I suggest that you install the older version and select repair. then without rebooting you run the installation again and tell it to remove it. Then without rebooting you install the new version and once this is complete you do reboot the host. Fixes this kind of thing about 98% of the time.

All of your guests should remain intact but I always tell everyone to back up their systems.

[kabalah]

this is the same problem i was having. and it still isn't resolved. no matter what i do, i can't get vbox to run anymore...at least i'm not the only one now.
jim

[Perryg]

@kabalah,
What was the last version that you had that worked?

[kabalah]

i actually had 3.0.8 working, but since installing 3.0.10 i have not been able to use bridged networking on 3.0.0, 3.0.2, 3.0.4, 3.0.8 and 3.0.10. nat works fine, just bridged networking seems broken.
jim

[Perryg]

@kabalah,
For some reason it appears that you have something that was not updated or installed properly. You can try the suggestion below and let me know if this helps.

Reinstall version 3.0.8. (DO NOT reboot)
Install version 3.0.8 install again and tell it to uninstall (DO NOT reboot)
Install Version 3.0.10 install and see if it works (This time reboot)

[kabalah]

ok, i downloaded 3.0.12 and installed it. then did a repair of 3.0.12, and then rebooted as administrator. everything is working again...so i'm not sure if it was 3.0.12 or the install as administrator with the repair...but, since it's working i'll quit experimenting. thanks for all your help!
jim

[sconklin]

On my Windows XP host I went to Network Connections-> VirtualBox Host-Only Ethernet Adapter->Properties and found that the VirtualBox Bridged Networking Driver was unchecked. I checked it, clicked OK-a Driver Install dialog box popped up, chose install, and now my bridged networking is working with my Ubuntu 9.04 guest