With VBox 3.2.0 my network crashes under Server 2003 Std. x86 when i boot up any guest. So i can't reach my server over remotedesktop. The only way to fix that, is a reset. I disabled the host-only adapter but it doesn't solve the problem.
With VBox 3.1.8 everything works fine. Is there anyone with the same problem?
I'm using a fritzbox 5140 router with the nvidia nForce430 onboard networking controller.
------------------------------------------------
Sounds like there is a problem with the network drivers.
You can try to uninstall VirtualBox reboot and then install it again (yes reboot again it's Windows). This should pickup your setting and you should still have all of your VMs intact.
But I always tell everyone to backup first.
Same problem. After 15-20 min. my server isn't reachable, even when i'm connected by RDP that time.
With VBox 3.1.8 everything is fine. I don't have a clou whats the problem. has something changed in the bridged network driver with 3.2.0?
These kinds of problems that are reproducible should be reported to bugtracker. You will need to setup an account there as it is on a different system.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.
Same problem. Running Linux 2.6 with Asterisk phone switch software as a system service. The server crashes once a day because svchost (network service) generates high cpu traffic (60-80%). Sometimes generation of a bluescreen and reboot. Hopefully this problem is solved soon. Otherwise I have to roll back to version 3.1.8
@xstream2005
Did you find some hints in the systems log? I have changed the PoolUsageMaximum to the value 60 (from default 80) because I've found some hints regarding the windows memory management. Let's see until tomorrow, if it works now...
@www_keng_de
No sorry. The problem is that my server is reacheable via remotedesktop only. So i have to do a hard reset to get access again.
But someone answers my ticket. He says that he has the same problem, but he can reactivate the network by closing VBox.
Yes, that's right - because the system get some resources/memory back. But restart your server before you start the VM again. It seems, that the VirtualBox's bridged network driver has a memory leak.
Yes, seems to be a memory problem. I have to reboot the server now once a day. In the taskmanager I see the Kernel-memory is growing and growing and the the CPU utilization as well.
Same problem. After 15-20 min. my server isn't reachable, even when i'm connected by RDP that time.
With VBox 3.1.8 everything is fine. I don't have a clou whats the problem. has something changed in the bridged network driver with 3.2.0?
I had the same problem. I used VBox 3.1.6 in bridged network, then at May 27 upgraded for 3.2.0, my system crash during all day May 28, after 15-20 min. my server isn't reachable, as happened to you. According to your experience with VBox 3.1.8 everything is fine, then I roll back to version 3.1.8 and my system is fine too.
Went from 3.1.8 to 3.2.0, immediately it started to consume resources to the point where server '03 kept indicating memory and disk errors. Reloaded '03, reinstalled vbox, same issue. Tested hardware, all tested good. Went back, reloaded windows, installed vbox 3.1.8 and she's now working just fine.
Problem would always start about 5-10 minutes into using the bridged nic setup.
**ADDED**
4gb ram installed on a SC1425 dual Xeon 3.6ghz server setup
3.2.0 should be renamed to 3.2 BETA 4 !!!
This is not a stable release for a productive environment. We switched back to 3.1.8 and everything is fine now.
www_keng_de wrote:This is not a stable release for a productive environment.
guesswork, from what i can see in the release dates the stable release is the 3.0.x Series (3.0.14) - and 2.0.x (2.0.12) is oldstable => http://download.virtualbox.org/virtualbox/
anyway, the version numbers last digit is the bugfix level
@fixedwheel
Oracle mentioned it at the virualbox.org download page "...at the time of the stable 3.2.0 release". Could also be an error .
I'll wait for the next 3.2.1 version.