Bridged networking on guest dies after 1st use
Posted: 21. Nov 2010, 18:55
Greetings everyone,
I'm running Virtualbox 3.2.10 on OSX 10.6.5 and am running a Windows 7 (x64) guest as my virtual machine. The VM has the Intel Pro 1000/MT as the virtual network interface and it is configured in bridged mode.
The problem that I'm having is that after I boot and log into the VM, I open a command prompt and check my IP address and I am getting an IP from my DHCP server and everything "looks" good. At that point, I can also ping any host (google, etc.) that I want and name resolution and traffic flow appear to look fine, as the pings are successful.
As soon as I open a browser, the VM freezes for about 10-20 seconds and after the VM "comes back"/unfreezes, the virtualized NIC appears to die. I can then no longer ping hosts, resolve names, etc. I can successfully release my DHCP address, but I can not successfully renew and get it back, as it appears that I lose all ability to pass network traffic at that point. VirtualBox shows the virtual NIC as being connected, and during this entire time, network access on the Host is not affected.
This behavior is exhibited regardless of whether the VirtualBox VM Additions are installed, and this is a newly-installed VM that I'm working with.
Any ideas?
I've uninstalled and reinstalled VirtualBox a few times - mainly to make sure the kernel extensions are deleted, rebooted after uninstall/reinstall, etc. but nothing seems to make a difference.
I'm crying "uncle" at this point because I don't know enough about the innards of OSX networking to troubleshoot this much further. Any help would be GREATLY appreciated.
Thank you!
I'm running Virtualbox 3.2.10 on OSX 10.6.5 and am running a Windows 7 (x64) guest as my virtual machine. The VM has the Intel Pro 1000/MT as the virtual network interface and it is configured in bridged mode.
The problem that I'm having is that after I boot and log into the VM, I open a command prompt and check my IP address and I am getting an IP from my DHCP server and everything "looks" good. At that point, I can also ping any host (google, etc.) that I want and name resolution and traffic flow appear to look fine, as the pings are successful.
As soon as I open a browser, the VM freezes for about 10-20 seconds and after the VM "comes back"/unfreezes, the virtualized NIC appears to die. I can then no longer ping hosts, resolve names, etc. I can successfully release my DHCP address, but I can not successfully renew and get it back, as it appears that I lose all ability to pass network traffic at that point. VirtualBox shows the virtual NIC as being connected, and during this entire time, network access on the Host is not affected.
This behavior is exhibited regardless of whether the VirtualBox VM Additions are installed, and this is a newly-installed VM that I'm working with.
Any ideas?
I've uninstalled and reinstalled VirtualBox a few times - mainly to make sure the kernel extensions are deleted, rebooted after uninstall/reinstall, etc. but nothing seems to make a difference.
I'm crying "uncle" at this point because I don't know enough about the innards of OSX networking to troubleshoot this much further. Any help would be GREATLY appreciated.
Thank you!