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


[Xen-users] 3.4.x networking

To: <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] 3.4.x networking
From: "Mark Chaney" <macscr@xxxxxxxxxx>
Date: Sun, 13 Sep 2009 00:57:18 -0500
Delivery-date: Sat, 12 Sep 2009 22:58:05 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=macscr.com; h=Received:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:x-cr-hashedpuzzle:x-cr-puzzleid:X-soundwave-MailScanner-Information:X-soundwave-MailScanner-ID:X-soundwave-MailScanner:X-soundwave-MailScanner-SpamCheck:X-soundwave-MailScanner-From; b=H/UiJDUgi69g3dVCAbyUZJo7ugPEO7Z7HEKqnk/SgHg0nvZAiUlg5qV6WKL1D9Bam3fjM/p7n6r/fD0wTBXcDvR+t2VJAPbFHUi1kwQ8FfECxuNG2LiNAXCQQxYVQqE9;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aco0NwvlFVfNoaz6RnuAYl7ah7DT1Q==

My Centos 5.3 cluster has major network stability issues (these are the dom0's) when running xen 3.4 and 3.4.1. Things were rock solid when running 3.3.1 and they were again when we downgraded back to it. Are there any known network issues with the 3.4.x group? Did something change with 3.4 with how networking is done that we might have needed to change? The guest networking worked fine afaik, but every hour or so, the dom0 would get fenced by another cluster member and its more than likely because of some type of networking change (maybe like the network service getting restarted or whatever). I couldn’t get any useful info out of the logs, but only happened on nodes that were running 3.4.x and it only happened if guests were running on it. Everything was fine if no guests were running. BTW, we tried changing kernels and that didn’t make a difference either. Current with centos is 2.6.18-128.7.1.el5xen, but our cluster was the most stable with 2.6.18-92.1.22.el5xen #1 SMP Tue Dec 16 12:26:32 EST 2008 x86_64 x86_64 x86_64 GNU/Linux and xen 3.3.1. Obviously for security and performance reasons we want to stay current


Any help is sincerelly appreciated!




Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>