xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Francisco Barrera <francisco.barrera@empelt.es>
Cc: xen-tools@lists.xensource.com, xen-devel@lists.xensource.com,
	xen-bugs@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: [Xen-bugs] Re: Network problem after updates
Date: Tue, 15 Jun 2010 17:21:00 -0400	[thread overview]
Message-ID: <20100615212100.GA23814@phenom.dumpdata.com> (raw)
In-Reply-To: <1274799896.11522.5.camel@portatil-1>

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@lists.xensource.com
> > http://lists.xensource.com/xen-users
> 
> 
> --------------------------------------------
> empelt
> Francisco Barrera
> 
> Móvil - +34 659253221
> francisco.barrera@empelt.es
> 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@lists.xensource.com
> http://lists.xensource.com/xen-bugs

  reply	other threads:[~2010-06-15 21:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 10:20 Network problem after updates Francisco Barrera
2010-05-25 15:04 ` Francisco Barrera
2010-06-15 21:21   ` Konrad Rzeszutek Wilk [this message]
     [not found]     ` <20100615212100.GA23814-6K5HmflnPlqSPmnEAIUT9EEOCMrvLtNR@public.gmane.org>
2010-06-16 15:24       ` Re: [Xen-users] " Francisco Barrera
2010-06-16 15:50         ` [Xen-devel] Re: [Xen-bugs] " Konrad Rzeszutek Wilk
2010-06-22 14:23           ` Re: [Xen-bugs] Re: [Xen-users] " Francisco Barrera
2010-06-22 14:41             ` [Xen-devel] Re: [Xen-bugs] " Konrad Rzeszutek Wilk
2010-06-22 15:32               ` Re: [Xen-bugs] Re: [Xen-users] " Francisco Barrera
2010-06-23  7:04               ` Francisco Barrera

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100615212100.GA23814@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=francisco.barrera@empelt.es \
    --cc=xen-bugs@lists.xensource.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-tools@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).