The problem is easy to reproduce.
I've managed to reproduce it using 3 separate Ubuntu 10.04 hosts.To reproduce
1. Setup a 64-bit Ubuntu 10.04 host.
2. Create a 64-bit Windows 7 guest.
3. Configure the guest to use "bridged" networking, with the "Intel(R) PRO/1000 MT Desktop Adapter" (this is your only real choice, no drivers available for the others).
4. Run the guest and use it to perform tasks that require networking.
Within an hour (usually within 10 minutes) the network will stop working on your guest.
At the moment when it happens, the guest CPU will spike and the system will become unresponsive for about 30 seconds. After that, you'll be able to use the guest system again, but you will not be able to access the network.To temporarily restore the network
Reset the network interface.
The least painful way to do is is:
1. Start a command prompt session, with administrator privileges.
2. Use netsh to disable and then re-enable the network enterface:
- Code: Select all Expand viewCollapse view
netsh interface set interface "Local Area Connection" DISABLED
netsh interface set interface "Local Area Connection" ENABLED
This will restore your network temporarily, until the problem repeats itself.