VirtualBox

Ticket #7706 (closed defect: obsolete)

Opened 3 years ago

Last modified 3 months ago

3.2.10 Win XP guest boot error with bridged network on Win Vista host

Reported by: Ethreal Owned by:
Priority: major Component: network
Version: VirtualBox 3.2.10 Keywords: bridged
Cc: Guest type: Windows
Host type: Windows

Description (last modified by frank) (diff)

There has been no effective reply to my post "3.2.10 bridged network problems on Win Vista host". I have uninstalled and reinstalled 3.2.10 on Vista machine and get same network error for Bridged network. Guest (Win XP SP3) will boot with either NAT or Internal network but not bridged. I need to be able to transfer files between host & guest so need bridged. Log files attached.

Attachments

Vbox error 2.odt Download (17.7 KB) - added by Ethreal 3 years ago.
Screen shot of error message & outdated msi information
Vbox error 2 revised.doc Download (16.0 KB) - added by Ethreal 3 years ago.
2nd file updates 1st and is in Word
#7706 additional info.odt Download (194.8 KB) - added by Ethreal 3 years ago.
#7706 additional detailed information

Change History

Changed 3 years ago by Ethreal

Screen shot of error message & outdated msi information

comment:1 Changed 3 years ago by Ethreal

Ticket #7706

Booting guest operating system (Win XP pro) from Virtualbox, mounted on Windows Vista home premium host, fails.

On trying to open the guest machine (Win XP) with network bridged adapter the following error message appears and the boot fails.

Virtualbox – error (message box) Failed to open a session of the virtual machine Windows WX Pro Failed to open/create the internal network 'HostinterfaceNetworking- Atheros ….Wifi adaptor' (VERR_SUPDRV_COMPONENT_NOT_FOUND)

Unknown error in creating virtual drive (VERR_SUPDRV_COMPONENT_NOT_FOUND)

Details Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}

Subsequent actions

I have uninstalled VB 3.2.10, reinstalled 3.2.10, uninstalled again and reinstalled 3.2.8 (as recommended by a contributor on the forum. Each time the same message. It appears that the original 3.2.10 installation has damaged/removed a driver in Windows somewhere, or a registry entry for a driver.

Associated problems/messages

On booting Windows I get the following message box; “Found new hardware” “Windows needs to install driver software for your unknown device” Option 1 “Locate and install driver software”

Previously this found nothing, the most recent attempt resulted in the following message box; “Found new hardware – unknown device” “Windows found driver software for your hardware device but encountered an error while attempting to install it.” “Virtualbox Bridged Network Driver Miniport” “Insufficient system resources exist to complete the requested service”

Existing Virtualbox advice that did not work

I tried to obtain the required log files to attach by following the instructions on your page 'How to enable logging for the .MSI host installer of VirtualBox' .

'There are two logs which are needed for an in-depth analysis: The installer log and the driver installation log of Windows itself. Please provide both logs when asked for them. ' .

Can't find either file anywhere on the computer.

Please also note that the microsoft installer cleanup mentioned in the article has been discontinued.

I can't upload screenshots of the error messages – files too big.

Win XP will boot from Virtual box if the bridged adapter (all adaptors) are de-activated and either NAT or Internal network are activated. I have not found a way to transfer files between guest and host in either mode, although internet connection works. My master database is on this copy of virtualbox. I cannot therefore make backups otr transfers to my Mac mounted Virtualbox, version 3.2.10 on which installed without problem.

Changed 3 years ago by Ethreal

2nd file updates 1st and is in Word

comment:2 Changed 3 years ago by Ethreal

I am not a programmer so can make no sense of the contents of the 'inf' files but, could the problem lie in the VBoxNetFlt_m.inf or one of the other VBoxNetFlt.xxx files ? Could it also be related to recent Microsoft updates? Certainly VBoxNetFlt_m.inf is entitled "Virtualbox Bridged Networking Driver" the same reference as the Microsoft driver install failure memobox.

comment:3 Changed 3 years ago by Ethreal

Since installing a 2nd virtual machine for a 2nd user on the one PC I now get 4 'Found new hardware' messages on start-up and each time that I change users. On checking these drivers they are all related to “Virtualbox Bridged Network Driver Miniport” followed by “Insufficient system resources exist to complete the requested service”

comment:4 Changed 3 years ago by chuguanyu

I have the exact same problem with Ubuntu guest on a Vista host.

comment:5 Changed 3 years ago by Ethreal

Update; I have just installed VB 3.2.12. This problem remains unresolved

comment:6 in reply to: ↑ description Changed 3 years ago by Ethreal

Replying to Ethreal:

There has been no effective reply to my post "3.2.10 bridged network problems on Win Vista host". I have uninstalled and reinstalled 3.2.10 on Vista machine and get same network error for Bridged network. Guest (Win XP SP3) will boot with either NAT or Internal network but not bridged. I need to be able to transfer files between host & guest so need bridged. Log files attached.

I have just installed VB 4.0 complete with Guest Additions 4.0; the problem remains

comment:7 follow-up: ↓ 8 Changed 3 years ago by Ethreal

Have just installed vBox 4.0.4; bridged network driver problem on Vista host remains unresolved. Since installing 4.0.0 the number of times the Windows driver dialog box has to be cancelled on login has increase to 6. This bug appears to be the same as reported in #7551 & #7745.

Changed 3 years ago by Ethreal

#7706 additional detailed information

comment:8 in reply to: ↑ 7 Changed 3 years ago by Ethreal

Replying to Ethreal:

Have just installed vBox 4.0.4; bridged network driver problem on Vista host remains unresolved. Since installing 4.0.0 the number of times the Windows driver dialog box has to be cancelled on login has increase to 6. This bug appears to be the same as reported in #7551 & #7745.

Additional details including Windows Vista registry data (see attached OoO file.

comment:9 Changed 3 months ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use