I tried turning off checksumming, first just in domU, then in both dom0
and domU, but the network still stopped.
However I have figured out what the problem is. The domU's network is
becoming unresponsive immediately after 4GB of data has been transmitted
by the eth0 device, as reported by ifconf
I am experiencing the same problem as Wolfgang two posts above. Unsure
if it is related to bug 218126.
Running stock feisty dom0, upgraded domU to hardy and now having this
problem. Tried Hirano Takahito's kernel on the domU yet the problem
subsists.
The server is quite heavily loaded as a web
Public bug reported:
The package sets up a startup link in /etc/rc2.d as S20jabberd2.
Unfortunately MySQL starts up in S20mysql, and therefore after jabberd2.
Renaming S20jabberd2 to S21jabberd2 fixes this problem.
** Affects: jabberd2 (Ubuntu)
Importance: Undecided
Status: Unconfi