VirtualBox

Ticket #7551 (new defect)

Opened 4 years ago

Last modified 20 months ago

VERR_SUPDRV_COMPONENT_NOT_FOUND when using bridged mode and host-only adapter has no list of names

Reported by: kenyee Owned by:
Priority: major Component: network
Version: VirtualBox 3.2.8 Keywords:
Cc: Guest type: Windows
Host type: Windows

Description (last modified by frank) (diff)

Two probably related problems:

I can't see any Names listed in the pulldown when I choose Host-Only for my network.

If I use Bridged mode, I get the above error when running the VM. There seems to be a lot of cases of this error, and I've followed all the suggestions that I've found (uninstall, reboot, reinstall, reboot, then try it...check device manager, etc.).

Host is Windows XP w/ all current patches. Guest is Win2003x64 w/ all patches, though the guest probably doesn't matter because it seems the host is messed up :-P

I'm attaching the vbox.log, the setupapi.log and the MSI*.log. I didn't see anything obvious in them...there seem to be a few USB driver errors but nothing w/ the network...

Attachments

Win2003x64-2010-10-08-13-46-15.log Download (34.0 KB) - added by kenyee 4 years ago.
vbox.log
virtualboxlogs.zip Download (182.3 KB) - added by kenyee 4 years ago.
MSI, setupapi, and vbox logs

Change History

Changed 4 years ago by kenyee

vbox.log

Changed 4 years ago by kenyee

MSI, setupapi, and vbox logs

comment:1 Changed 4 years ago by kenyee

Bridged networking used to work in 3.2.6, so I uninstalled 3.2.8 and put on 3.2.6 but it doesn't work any more. Whatever changes 3.2.8 made, it looks like I can't roll back to a previous version of VirtualBox :-P

comment:2 Changed 4 years ago by frank

Try to uninstall VirtualBox completely, then reboot the host. Make sure that no VBox network interface is installed (check the Windows network settings). After that try to install VBox again.

comment:3 Changed 4 years ago by kenyee

I uninstalled, verified that there were no virtual box interfaces (looked at all the network connections, and also at system\devicemanager). In device manager, the vboxnetadp.sys version is listed as 3.2.8r64453 from Oracle, but on the General page, it says the manufacturer is still Sun, so you guys missed a string when doing the search replace thing ;-)

I did notice that VMWare had two network interfaces installed and I don't use VMWare any more so I also uninstalled VMWare Server before I installed VirtualBox. Same issue. My VM still isn't usable...can't do bridge mode or even host-only mode. I'd rather get bridge mode working because it's more flexible but would settle for host-only mode at this point :-P

It'd be nice if there were some sort of "cleanup virtualbox drivers/files from my drives and registry" utility...

If you want me to run any beta code w/ debug statements, let me know...

comment:4 Changed 4 years ago by kenyee

I think these are also related:  http://www.virtualbox.org/ticket/3654

 http://forums.virtualbox.org/viewtopic.php?f=5&t=16828

I have the same symptoms as mentioned in the forums...I can't add a host-only adapter. The dialog box about approving an unsigned driver comes up and then it gives the error described. Bridged mode probably uses the same driver and both seem to be unable to enumerate network cards on my system which is probably why that Name dropdown doesn't get filled and why doing File/Preferences/Network and trying to add a Host network doesn't work...

comment:5 Changed 4 years ago by kenyee

ok...this is just weird. I installed VMWare Server 2.0.2 (the free one) and now I can install a VirtualBox host only adapter and bridged mode sees it too. Only odd thing now is I can't ping the VM from the host or vice-versa and I used to be able to do it.

Someone really needs to write a utility that breaks down the host adapter enumeration or install process more to figure out why this weirdness happens...there are too many bug reports w/ this symptom :-P

comment:6 Changed 4 years ago by kenyee

FYI, fixed the problem w/ not seeing the VM from host. For Bridged mode, I chose to bridge w/ the network adapter. I had to bridge with the "MAC Bridge" adapter instead and now both can ping each other. Guess I'm stuck w/ having VMWare on my system so VirtualBox works...the irony :-P

comment:7 Changed 3 years ago by Ethreal

I had not seen this post and have just added post #7706 with the same problem. Only difference is that I upgraded from 3.2.8 to 3.2.10. It is clear that the installation has damaged/removed an essential Windows component. I also now get a windows message on boot to install new 'unidentified driver'. Windows cannot find this as it is unidentified. This message only began to appear after upgrade to 3.2.10. Host Win Vista home premium.

comment:8 Changed 3 years ago by jupsoleil

I found the solution to this problem elsewhere:  http://forums.virtualbox.org/viewtopic.php?f=6&t=36730&p=164725#p166352[[BR]]

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network
Postby jonnybravo » 15. Dec 2010, 05:53
Hey Bryan,

Your post helped me find where to look; however, deleting the config key did not work (at least it didn't in my Win7Pro x64 host). Although, what did work is in the same area, there is a key called MaxNumFilters. On my end, that was set to 8. I changed that value to 20 (which is 14 hex). Reboot and bingo. Problem solved... bridged adapter now installed properly when running vb installer.

comment:9 Changed 20 months ago by frank

  • Priority changed from blocker to major
  • Description modified (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use