xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Francisco Barrera <francisco.barrera@empelt.es>
To: xen-tools@lists.xensource.com, xen-devel@lists.xensource.com,
	xen-bugs@lists.xensource.com, xen-users@lists.xensource.com
Subject: Network problem after updates
Date: Mon, 24 May 2010 12:20:42 +0200	[thread overview]
Message-ID: <1274696442.6507.2.camel@portatil-1> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1761 bytes --]

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.



[-- Attachment #1.2: Type: text/html, Size: 2214 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

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

             reply	other threads:[~2010-05-24 10:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 10:20 Francisco Barrera [this message]
2010-05-25 15:04 ` Network problem after updates Francisco Barrera
2010-06-15 21:21   ` [Xen-bugs] " Konrad Rzeszutek Wilk
     [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=1274696442.6507.2.camel@portatil-1 \
    --to=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).