This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Xen 3.1 + CentOS 5 + HP ProLiant G5 = DomU packet drops

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen 3.1 + CentOS 5 + HP ProLiant G5 = DomU packet drops
From: Ivan Porro <pivan@xxxxxxxxxxxxx>
Date: Tue, 13 Nov 2007 12:26:39 +0100
Cc: Pezza <mario.beccia@xxxxxxxxxx>
Delivery-date: Tue, 13 Nov 2007 03:27:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <13687654.post@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <13687654.post@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20071022)
Dear all,

I've the same problem on xen 3.1, PE 1950 server (on dom0 I've broadcom nextreme driver updated to 1.5) I'm experiencing a strange behaviour.

On windows HVM (2003 and XP) I don' have problem via the built-in VNC server but, if I connect via RDP (terminal server), after few minutes of connection, the terminal server client freeze (on windows and on linux) and the HVM does not respond. After about half minute of panic, it go back working just to freeze again after few minutes. It freeze even if from a VNC session on Win2k3 server machine I open a terminal server to the very same server... the RDP session crashes, while the VNC is perfect. I need to virtualize a server for terminal server access so I cannot rely on VNC only...

During the freeze, if I click a button (i.e. sw installation on windows) it "remember" the event and as soon as the system unlock it execute the requested commands.

during the worst freeze I've experienced my laptop (Ubuntu 7.10) became totally locked too... to complete this e-mail I had to CTR+ALT+F1 switch to text console and kill tsclient.

The only useful info I found is:

Net0 RX:   0bytes        0pkts        0err    23759drop
TX:        0bytes        0pkts        0err        0drop

Net0 RX:   0bytes        0pkts        0err    23757drop
TX:        0bytes        0pkts        0err        0drop

but I don't know how to further investigate in and relate it to other system hw/sw components. Network inside the VM seems working good.

I'll google around until new advice :)


Pezza wrote:
Hi all,

I've a Xen server (Xen 3.1 compiled from sources [stable downloaded last
wed...], CentOS 5 as the host OS, HP Proliant G5 6Gb ram with Broadcom
NetXtreme 2) with 4 guests, each running Windows 2003 just installed, with
nothing else.
Network is configured with the default bridging script, no changes. I'm
using 1 network card only for the moment.
All guests run apparently fine, but if I try to download from a server on
the same subnet and/or from a share on the same subnet, I get strange
corruption errors.

Poking around, I found out that all the guests are experiencing packet drops
on their network cards: even just after booting the guest, with the guest os
completely idle, I can see from xm top that the guest network card is
dropping packets.

Googling around, I've found some similar situations and thus I tried:
 * updating the network card drivers: I'm now using version 1.5.xxx
downloaded from the broadcom website and installed following instructions
found on this mailing list
 * enabling IP forwarding in the host kernel (instead of using the
automatically generated rules in the forward chain in iptables)
 * disabling the management mode on the card firmware, following
instructions found on this mailing list
 * using the ne2k_pci driver in the guest instead of the default
 * trying different vm schemes (1, 2 or 3 VM at a time instead of 4)
 * pinning Dom0 to one CPU and the guest on another (as suggested somewhere
on this mailing list)

None of the above fixed the problem.

I don't know what else could I do to fix this.

Is this situation normal? Is using a PV enabled host/guest system the only

Thanks in advance,


voice: +39 010 353 2789
fax:   +39 010 353 2948

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>