virtualbox.org

Hi all,

I've been playing with virtualbox for some time on my windows server to test out things before putting them into production. Recently I began running the VM's on my linux server as it had a stack more ram to use and have run into a networking issue.

Randomly either after an hour or a few hours or so the network drops entirely on the VM. I am using host networking with my vbox1 interface bridged onto my internal network interface. It works great but all of a sudden just drops entirely. Nothing in my syslog or log files indicates what is going on.

For reference my server is an AMD X2 (no VT) with 4gb of ram running 64bit Debian Lenny. The latest copy of VirtualBox 1.6.4 (same issue happens on 1.6.2 and 1.6.0).

The guest system is a 2003 Standard edition (x86) SP2 and has been fine before. The system was installed fresh on the linux server. Running the latest guest tools but still seeing the issue. I've tried assigning an ip to the vbox1 interface on the server side and pinging and I get nothing. From within the windows guest however I get "No Resources" which is odd because the network interface still shows as up.

Any suggestions would be greatly appreciated.

Hello all,
I have the same problem as "clayman".

VBox 1.6.4 working on XUBUNTU 7.10 and every guest "WindowsXP" drop after an undefined time the complete network connection. In guest I can see an aktiv network card, but no connection (no IP-ping or something else). Also no connection to an shared folder is possible (share folder are stored in the home folder from linux). Nothing to find in an log from the guest!

Only an new start from the guest rebuild this connection.

I work with HIF (Host-Mode) and installed the latest guest-additions.

This problem was not before. With the old version VBox 1.5.6 I didn't see this.

STRAGIC-IT
Hardy

I seem to have resolved the issue on my setup. Instead of the PCNet3 network interface I reconfigured it to be an Intel Desktop adapter and installed the latest Intel drivers. It's now been rock solid since then (about 24 hours).

Not sure if it was something weird with maybe the windows driver but either way its working now.

claymen wrote:I seem to have resolved the issue on my setup. Instead of the PCNet3 network interface I reconfigured it to be an Intel Desktop adapter and installed the latest Intel drivers. It's now been rock solid since then (about 24 hours).

Not sure if it was something weird with maybe the windows driver but either way its working now.

WOW - it worked now... great job clayman...
I tested it in WindowsXP Prof. and in WindowsXP Home.
I think it comes since servicepack #3 for WindowsXP. Before servicepack #3 both guests work 2 days without that error an the latest VBox V1.6.4. Is it possible there was an problem with the AMD card support in WindowsXP with SP3?

Great job clayman - this saved my day.

STRAGIC-IT
Hardy

No worries, glad its working.

It could be a broken driver for the AMD PCNet card but I am not really sure. I mean it worked perfectly for so long without issue and only recently broke.

Doesn't really matter too much then so long as its working with the Intel driver.