WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] 3.4.x networking

To: Mark Chaney <macscr@xxxxxxxxxx>
Subject: Re: [Xen-users] 3.4.x networking
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sun, 13 Sep 2009 16:46:26 +0300
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 13 Sep 2009 06:47:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <00fe01ca3476$6ca490b0$45edb210$@com>
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>
References: <00de01ca3437$0eaf5e20$2c0e1a60$@com> <713d03b70909130225k2761319bwb490679e3458bb4@xxxxxxxxxxxxxx> <00fe01ca3476$6ca490b0$45edb210$@com>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Sun, Sep 13, 2009 at 08:30:53AM -0500, Mark Chaney wrote:
> Snippet from /var/log/messages:
> 
> Sep 13 01:28:32 wheeljack kernel: device vif1.0 entered promiscuous mode
> 
> Sep 13 01:28:32 wheeljack kernel: physdev match: using --physdev-out in the
> OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is deprecated
> and breaks other things, it will be removed in January 2007. See
> Documentation/feature-removal-schedule.txt for details. This doesn't affect
> you in case you're using it for purely bridged traffic.
> 
> Sep 13 01:28:32 wheeljack logger: /etc/xen/scripts/vif-bridge: iptables
> setup failed. This may affect guest networking.
> 
> Sep 13 01:28:37 wheeljack kernel: blkback: ring-ref 8, event-channel 6,
> protocol 1 (x86_64-abi)
> 
> Sep 13 01:28:37 wheeljack kernel: eth1: topology change detected,
> propagating
> 
> Sep 13 01:28:37 wheeljack kernel: eth1: port 2(vif1.0) entering forwarding
> state
> 
>  
> 
> I know it says the error is with vif-bridge, but that's stock, so I don't
> know what could be wrong with it. I dont get these errors witht he Xen 3.3.1
> and Kernel i mentioned earlier. 

Did you diff vif-bridge script between xen 3.3.1 and xen 3.4.1 versions? 
What are the differences? 

What's the failing iptables command? Please paste the whole command here, 
including the parameters.

> Ive gone as far as disabling iptables and
> still have the same issues with stability. You did bring up an idea though,
> i havent tried disabling access to eth0 from the guests, but again, what
> changed in the xen versions that would cause such a problem if it was that.
> I swear there must have been a change that has been poorly documented.
> 

Please paste the errors (log messages) about fencing. Does the eth0
traffic work when the server gets fenced?

Do you have errors or log messages in "dmesg" or /var/log/messages when
that fencing happens? 

>  
> 
> Anyway, thanks for the help, I sincerelly appreciate it.
> 
>  
> 
> -Mark
>

-- Pasi

>  
> 
> From: Stephen Ross [mailto:stephen.ross1986@xxxxxxxxxxxxxx] 
> Sent: Sunday, September 13, 2009 4:25 AM
> To: Mark Chaney
> Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] 3.4.x networking
> 
>  
> 
> Hi Mark,
> 
>  
> 
> Are you using the xen network-bridge script or ifcfg scripts to setup your
> networking? Are guest VM's and CMAN node info passing on the same interface?
> 
>  
> 
> Cheers,
> 
> 
> Steve
> 
> On Sun, Sep 13, 2009 at 6:57 AM, Mark Chaney <macscr@xxxxxxxxxx> wrote:
> 
> 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!
> 
>  
> 
> -Mark
> 
>  
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
>  
> 

> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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