I am having a (possibly related?) problem with Xen 2.0.6 + 2.6.11.10.
The machine is a dual athlon MP on a Tyan Tiger S2466-4M, Intel e1000.
I am running Debian 3.1.
A have been running the same configuration for months, and for a few
minutes each day, Nagios would notice that my domU's lost networking
connectivity completely. It would never last more than a few minutes, so
I did not pay much attention to it. During this time, the domU's don't
even respond to arp requests. It does not matter what CPU they are on.
dom0 was never affected.
Last Friday the problem got very bad to the point where every few minutes,
domU networking would go down, and stay down for longer periods of time.
Rebooting did not fix anything. I switched from the e1000 to the onboard
3com 10/100 NIC, and this seemed to cure the problem for 5 days, but
last night the domU networking started to bounce up and down again.
There is no interesting dmesg output in dom0 or domU or Xen.
I have not tried to ping from one domU to another. Usually these events
are infrequent and happen while I am asleep.
Now I am wondering if there is some SMP issue with Xen that only surfaces
on the K7 architecture.
Any insight would be appreciated.
Regards,
Jeff
On Tue, Aug 30, 2005 at 06:31:16PM +0200, Christoph Schmitz wrote:
> Hi,
>
> we're running Xen 2.0.5 (Kernel 2.6.11.4-21.8-xen) as installed by default
> on SuSE 9.3. The machine is a dual Athlon MP on a Tyan Thunder board with
> an Intel Pro/1000 NIC. The network between dom0 and the domUs uses the
> default bridged setup.
>
> Unfortunately, when transferring large amounts of data (e.g. large file
> transfers via NFS, or just pumping zeroes across the network with netcat),
> after 1 GB of data or so (a 3 GB file transfer definitely fails), the
> network suddenly stalls with only a few 100k/s of bandwidth remaining.
>
> This happens between dom0 and other machines, between domU and other
> machines, and between several domUs when running on different CPUs.
> Interestingly, things seem to be ok between domUs if they're on the same
> CPU.
>
> Are there any ideas what one could do to fix this?
>
> Thanks in advance,
>
> Christoph
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home