VirtualBox

Ticket #4677 (new defect)

Opened 5 years ago

Last modified 15 months ago

Host-only interface causing problems on Windows 7 host

Reported by: shubbard Owned by:
Priority: major Component: network/hostif
Version: VirtualBox 3.0.4 Keywords:
Cc: Guest type: other
Host type: Windows

Description

I am not sure how to substantiate my claims; however, installing the VirtualBox Networking Components causes my machine (the host) to experience pretty severe issues. I am using version 3.0.2 of VirtualBox on a Windows 7 64-bit host. Immediately after installing VirtualBox, coming out of sleep I would have to disable/re-enable the interface to get it to work. I checked, downloaded, and installed the latest nVidia drivers for my chipset and that fixed the sleep issue. After resuming from Hibernate my interface stopped working all together. No amount of disabling and re-enabling the interface had any impact. At first I thought my NIC had just died and was about to write off the whole experience; however, booting into SystemRescueCD proved that my NIC was in fact functioning. I returned to Windows 7, where my interface still wasn't working, and removed VirtualBox and voila my network was functioning again.

My system specs are as follows: AMD Phenom II X4 Asus M3N-HD/HDMI (nForce 750a chipset) 4GB RAM Windows 7 (x64)

Change History

comment:1 Changed 5 years ago by shubbard

Sorry, I forgot to mention that I installed VirtualBox without the Networking Components and it works just fine.

comment:2 follow-up: ↓ 3 Changed 5 years ago by shubbard

No longer an issue in 3.0.4.

comment:3 in reply to: ↑ 2 ; follow-up: ↓ 5 Changed 5 years ago by shubbard

Replying to shubbard:

No longer an issue in 3.0.4.

Scratch that, just had the same problem in 3.0.4.

comment:4 Changed 5 years ago by frank

  • Version changed from VirtualBox 3.0.2 to VirtualBox 3.0.4

comment:5 in reply to: ↑ 3 ; follow-up: ↓ 6 Changed 5 years ago by misha

Replying to shubbard: Am I correct that the issue happens only after resuming from hibernate?
Did you see this with VBox versions other than 3.0.2 & 3.0.4?

comment:6 in reply to: ↑ 5 Changed 5 years ago by shubbard

Replying to misha:

Replying to shubbard: Am I correct that the issue happens only after resuming from hibernate?
Did you see this with VBox versions other than 3.0.2 & 3.0.4?

You are correct. It only happens after resuming from hibernate. I have not tried other versions, but I will try them and let you know.

comment:7 follow-up: ↓ 8 Changed 5 years ago by ZPrime

I have had similar network issues in Windows 7 RC. I did NOT have any problems with 3.0.2, but 3.0.4, when I installed it and updated the network filter driver, completely broke the host's network connection. If I uncheck the filter driver so it isn't in use on my physical NIC, networking is fine.

I just recently reloaded the host OS with Windows 7 final/RTM, and I have just reinstalled VBox 3.0.4 and the behavior is gone at the moment. I haven't yet tried sleeping and resuming to see if that is the trigger.

comment:8 in reply to: ↑ 7 Changed 5 years ago by shubbard

Replying to ZPrime:

I have had similar network issues in Windows 7 RC. I did NOT have any problems with 3.0.2, but 3.0.4, when I installed it and updated the network filter driver, completely broke the host's network connection. If I uncheck the filter driver so it isn't in use on my physical NIC, networking is fine.

I just recently reloaded the host OS with Windows 7 final/RTM, and I have just reinstalled VBox 3.0.4 and the behavior is gone at the moment. I haven't yet tried sleeping and resuming to see if that is the trigger.

Out of curiosity, what are your system specs?

comment:9 Changed 5 years ago by ZPrime

HP dc7800 "convertable tower" Windows 7 x64 (now final/Enterprise, was RC/Ultimate when having problems) Core2Duo E6750 4 GB RAM Intel 82566DM-2 Gigabit onboard NIC

Can't think of much else that is relevant to the discussion.

I'm wondering if perhaps a complete uninstall and then re-install of VBox and all components would solve your problem? That's essentially what I did when I formatted the host and put on Win7 Final... but as I said I've yet to try sleeping and restoring to see if that causes the bug to reappear.

When I had the problem with 3.0.4 previously, it happened instantly after upgrading to 3.0.4 from .2, and I could toggle the behavior by en/disabling the "VirtualBox Bridged Networking Driver" (henceforth "BND") on my host NIC. Rebooting the host didn't help, but if I disabled the BND then my host networking was OK.

Of note, with the BND disabled, I could still use NAT networking in guests without any problems. I don't often need bridged access, so I was able to tolerate the lack of it temporarily. I didn't try any host-only access.

comment:10 follow-up: ↓ 11 Changed 5 years ago by shubbard

I have tried completely removing and reinstalling Windows 7 on the Host. NAT does indeed work without any problems. I currently have VirtualBox installed without the VirtualBox Bridged Networking Driver.

comment:11 in reply to: ↑ 10 Changed 3 years ago by jg123

Replying to shubbard:

I have tried completely removing and reinstalling Windows 7 on the Host. NAT does indeed work without any problems. I currently have VirtualBox installed without the VirtualBox Bridged Networking Driver.

Installing without the Bridged Network adapter solved my no "network on resume from standby on Windows 7 64-bit" too! Ethernet card is an Intel 82567LF-2 Gigabit Network Card with latest Intel drivers.

comment:12 Changed 3 years ago by Phanto

Hi All,

I just wanted to confirm that I also have this issue. This is occurring with the latest version of VirtualBox (4.0.2 as of the time of this post).

Like the posters above, when hibernating or placing my system to sleep, I lose networking. I would have to disable/enable networking in order for it to resume working. Disabling the bridged networking module (or not installing it) resolves the issue. I am also running Windows 7, and I also have an Nvidia chipset (nForece4).

This bug has existed for many versions, and unfortunately, is still an issue in the latest release.

Please let me know if there is more information that I can contribute to this bug report.

Thank You.

comment:13 Changed 3 years ago by jamesm

I am having the same problem as described above. I am running VirtualBox 4.0.2 on a Windows 7 x64 host. I normally hibernate my system daily, but since installing VirtualBox my system always fails to reconnect to the network on restart.

Disabling my primary network interface then reenabling the interface restores network functionality to my Win7 host. However, this is a pain.

Hardware:

Biostar TF570SLI AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ NVIDIA nForce Networking Controller (dual NICs on mainboard, only 1 in use)

comment:14 follow-up: ↓ 15 Changed 3 years ago by vbguyny

I have the same issue on my Laptop, but it happens when resuming Windows from sleep. Please... PLEASE FIX THIS!!!

Windows 7 (32-bit) IBM Thinkpad R50 1.5GB RAM On board 802.11G

comment:15 in reply to: ↑ 14 ; follow-up: ↓ 16 Changed 3 years ago by vbguyny

Replying to vbguyny:

I have the same issue on my Laptop, but it happens when resuming Windows from sleep. Please... PLEASE FIX THIS!!!

Windows 7 (32-bit) IBM Thinkpad R50 1.5GB RAM On board 802.11G

Sorry, forgot to mention using VirtualBox 4.0.4

comment:16 in reply to: ↑ 15 Changed 3 years ago by jamesm

Replying to vbguyny:

I have upgraded to 4.0.4r70112 but still have the problem. There is no problem if I do a full shutdown of Windows 7 rather than hibernate. I have tried variations of bridging with my primary as well as secondary network interface, but my system always comes out of hibernation with the network unable to communicate. I have to disable then reenable the network interface before I can connect to my LAN. However, if I disable all network interfaces in all my VMs, resuming from hibernation is no longer a problem. However, it is troublesome to disable networking from my VMs every time I exit and to reenable VM networking before restarting a VM. It is troublesome to go through a full shutdown/startup in Windows every time. And it is troublesome to open my network adapter settings dialog after every resumption from hibernation to disable and reenable my network interface. Surely Oracle can figure this one out.

My host: Windows 7 Pro 64-bit SP1, Biostar TF570SLI, AMD Athlon(tm) 64 X2 Dual Core Processor 5600+, NVIDIA nForce Networking Controller

comment:17 Changed 3 years ago by galmok

I experience the same issue. When returning from standby on Vista64, I sometimes have no network. I always try to disable/enable the NIC, but that has so far never helped. When modifying the NIC settings to exclude VirtualBox Bridged Networking Driver, network function is restored right away. Excluding anything else doesn't help.

Using VB 4.04r70112 on Vista64 (UAC disabled). NIC is "Realtek PCIe GBE Family Controller", driver 6.242.824.2010 and date 24-08-2010.

NIC Driver had a switch in "Allow the computer to turn off this device to save power.". I'll remove that switch, keeping the NIC powered at all times (have to try something).

comment:18 Changed 15 months ago by ws liu

This issue still exist on latest release 4.2.6 r82870. Each time hibernate and wake up host-only network interface become malfunction. I need to disable and re-enable it to get it work. Please fix this issue.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use