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-bugs

Re: [Xen-bugs] Re: [Xen-users] Network problem after updates

To: Francisco Barrera <francisco.barrera@xxxxxxxxx>
Subject: Re: [Xen-bugs] Re: [Xen-users] Network problem after updates
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 15 Jun 2010 17:21:00 -0400
Cc: xen-tools@xxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, xen-bugs@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 16 Jun 2010 06:50:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1274799896.11522.5.camel@portatil-1>
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: <1274696442.6507.2.camel@portatil-1> <1274799896.11522.5.camel@portatil-1>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-12-10)
On Tue, May 25, 2010 at 05:04:56PM +0200, Francisco Barrera wrote:
> Can anybody help me with this problem?

Are you still having problems?

Granted you are using an ancient kernel so I fear I can't help you much.
If you updated to the latest pv-ops...

> 
> 
> El lun, 24-05-2010 a las 12:20 +0200, Francisco Barrera escribió:
> 
> > Hi all,
> > 
> > I've a serious problem with my dom0 xen installation, that's why I'm
> > blocked to daily work.
> > I come to describe my virtualization scenary and the arised problem.
> > 
> > Hardware is a Dell server with 3 physicall ethernet network cards and
> > 16 GB RAM.
> > Initially installed CentOS-5.2 with Xen-3.0.3 and 2.6.18-128.el5xen
> > kernel.
> > Dom0 with 7 domU paravirtuallized (they have CentOS like os also).
> > One domU is configured like a Firewall, using one of the physicall
> > NICs through pciback, that directly connect with the ISP modem-router.
> > Until here all worked ok and I was happy :)
> > 
> > Later, I was made the next updates through "yum update/upgrade" and
> > "yum install Virtualization": Xen 3.4.1 version, CentOS-5.4 and
> > 2.6.18-164.el5xen kernel.
> > Initially all worked fine, except some stuffs related to bridge name
> > (it came to xenbr0 to eth0).
> > The problem arise when from certain day, the network was freezed,
> > collapsed.
> > Anything of the domUs can answer to ping command, except dom0 that is
> > the only I can access via ssh.
> > Testing some issues, the network recovers if I shutdown the domU
> > Firewall.
> > 
> > I guess that the source of the problem must be pciback kernel module
> > or some incompatibillity with network card driver.
> > I've configured the xend-pci-permissive.sxp file to fix some messages
> > that appears in the boot of the dom0.
> > 
> > The conclusions that I've get analyzing the situation are the next:
> > - at the begining, Firewall works ok since it's overloaded by net
> > traffic
> > - from this moment, exactly 1 hour later from boot/reboot of dom0, the
> > network is blocked...always
> > - once the network is blocked, if I've shutdown the Firewall, the
> > network recovers
> > - when much time the network is blocked, more time the Firewall takes
> > to shutdown
> > 
> > Any suggestion?
> > Thanks in advance.
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> 
> 
> --------------------------------------------
> empelt
> Francisco Barrera
> 
> Móvil - +34 659253221
> francisco.barrera@xxxxxxxxx
> http://www.empelt.es
> 
> 
> ________________________________________________________________________
> 
> 
> 
> 
> Antes de imprimir este e-mail piense en su responsabilidad compromiso
> con el medio ambiente
> 
> AVISO LEGAL
> Este mensaje y los documentos anexos que pudiera incluir se dirige
> exclusivamente a su/s destinatario/s y puede contener información
> privilegiada o confidencial. Si no es ud. el destinatario del mensaje,
> le rogamos que lo comunique inmediatamente al remitente y proceda a su
> destrucción. La utilización, grabación, divulgación, copia o cualquier
> otro uso de la información sin el consentimiento de EMPELT está
> prohibida en virtud de la legislación vigente.
> 
> EMPELT cumple la Ley Orgánica 15/99 de 14 de Diciembre de Protección de
> Datos de Carácter Personal. Su e-mail y datos personales pueden estar
> incluidos en un fichero para su tratamiento. En cualquier momento puede
> ejercer sus derechos de acceso, rectificación, cancelación y oposición,
> mediante el envío de un e-mail o comunicación por escrito.
> 
> ________________________________________________________________________
> 
> 
> 
> Before printing think about your responsability and commitment with the
> environment
> 
> DISCLAIMER
> This message and all its attached documents is intended exclusively for
> its addressee(s) and may contain information that is confidential and
> protected by a professional privilege or whose disclosure is prohibited
> by law. If this message has been received by mistake, please we require
> to notify the sender immediately via e-mail and delete it. Any
> dissemination, copy, disclosure or, in any other way, using any of the
> information without the EMPELT consent is strictly prohibited by law.
> 
> EMPELT meets the Organica Law 15/99 of December 14 for the Protection of
> Personal Data. Your e-mail and personal information can be included in a
> file for treatment. In any moment you can exercise their rigths of
> access, rectification, cancellation and oposition by sending and e-mail
> or written communication.

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


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