Guest loses networking on high traffic load => Fixed in SVN/3.0.8

I can confirm this as well on OpenSuse? 11.1 64 Bit host. I am using bridge mode.

Hmm, evil, why are you using the same intnet for both network cards of the VM?

What do you mean? The configuration is:

src eth1 (192.168.1.10) <-> netem eth1 (192.168.1.1) netem eth2 (192.168.2.1) <-> dest eth1 (192.168.2.20)

so there are 2 internal networks (src_side and dest_side)

each of them has a NATted eth0 down and disconnected

Sorry, my fault. Misread the VBox.log file. Actually the names of the two internal networks are send and receive.

How long does it take until the VM looses the connection?

What I am doing is transfer videos. From destination I do: ssh user@192.168.1.10 "mp4trace -f -s 192.168.2.20 12346 video.mp4"

mp4trace is included in evalvid software. it packetize a video and sends it to the destination.

I do it in a cycle with 5 short videos. Sometimes it loses network on the first, sometimes on another, sometimes it gets to the end, no precise spot. The only thing that I suspect, is that it happens more likely if I am doing something stressful on the host, using CPU. But it's just a feeling

Situation update: I found out an error on netem2 which affected sometimes netem eth2 (192.168.2.1). Cleaning netem rules there restored the network without reboot. Anyway such problem should have been fixed.

So I am back to virtualbox "blame" :) I kept testing and now the network was lost between src eth1 (192.168.1.10) <-> netem eth1 (192.168.1.1), both virtual devices without a netem rule set, ever. And I restored the network turning off/on src machine, which never had any netem rule set.

Cannot figure out any reasonable explanation.

Just fixed a potential hang of the PCNet emulation in rare cases. E1000 is not affected AFAICS.

Apparently it should be solved cause I didn't experience any hang so far with the new package.

I'd like to add as a further information that the same problem was happening also on vmware, but there it was detected as too many I/O requests and it turned the file system into read-only, which was extrmely annoying, way more than the disappearing network.

Thanks for the feedback.

I experience this issue as well, and it hasn't changed in v3.0.8. E1000 is also affected.

Sorry, I forgot a couple of details. This is a Mac OSX 10.6 host with a Debian testing guest (kernel 2.6.30-1). I use two network interfaces: one NAT and one Host-only adapter. The NAT interface works great all the time. The host-only interface, however, usually works as it should for a while after boot, then it becomes extremely slow and/or unresponsive.

The problem is discussed here as well: http://forum.virtualbox.org/viewtopic.php?f=6&t=19457&start=30&sid=d2fa7b3d50bc97a49f596a0df94743ce

Replying to henrik242:

The problem is discussed here as well: http://forum.virtualbox.org/viewtopic.php?f=6&t=19457&start=30&sid=d2fa7b3d50bc97a49f596a0df94743ce

This bug was initially filled against NAT, so could you please open new one against host-only + log files?

Hachiman: Sure, it's submitted as ticket #5254