From: Francisco Barrera <francisco.barrera@empelt.es>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-tools@lists.xensource.com, xen-devel@lists.xensource.com,
xen-bugs@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Re: [Xen-bugs] Re: [Xen-users] Network problem after updates
Date: Tue, 22 Jun 2010 16:23:13 +0200 [thread overview]
Message-ID: <1277216593.4742.26.camel@portatil-1> (raw)
In-Reply-To: <20100616155013.GA3674@phenom.dumpdata.com>
[-- Attachment #1.1: Type: text/plain, Size: 4100 bytes --]
Hello Konrad,
I follow your suggestion and I downgrade the Xen dom0 and hipervisor to
the 3.1.2 vesion and 2.6.18-194.3.1.el5xen kernel (versions by default
in RHEL 3.5).
At this moment all works fine, but this message in /var/log/mesages
worry me a lot:
pciback 0000:09:00.0: Driver tried to write to a read-only configuration
space field at offset 0x4c, size 2. This may be harmless, but if you
have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of
your device obtained from lspci.
This is the same message that appears in the previous update to xen
3.4.1 that I did make, and at the moment to make it, all works fine
also.
Then, after a lot of network traffic, the system began to freeze, as I
describe in my first message.
The question is if I add the address in the message in the
xend-pci-permissive file can solve this, or if I need to downgrade to
lower version to avoid it.
Thanks for you answers.
Paco.
El mié, 16-06-2010 a las 11:50 -0400, Konrad Rzeszutek Wilk escribió:
> On Wed, Jun 16, 2010 at 05:24:39PM +0200, Francisco Barrera wrote:
> > Hi Konrad,
> >
> > unfortunatelly I still have problems... the sames problems with the
> > network domU Firewall.
>
> You look to have a production type server, so I would recommend you
> actually roll back.
> >
> > Then you propose me to update the dom0 kernel from 2.6.18-164.el5xen to
> > the latest version, isn't it?
>
> Yeah, but it might be lots of trouble for you (compiling, configuring,
> etc).
> > And update the pv-ops also?
> >
> > It's necessary update the domU kernel?
>
> No. The problem you are describing look to be in the netback driver.
> Thought I am not certain of why you are using the netback module when
> you pass in a NIC to the guest? Or does each guest have a bridge?
>
--------------------------------------------
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.
[-- Attachment #1.2: Type: text/html, Size: 4646 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-06-22 14:23 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 ` [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 ` Francisco Barrera [this message]
2010-06-22 14:41 ` 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=1277216593.4742.26.camel@portatil-1 \
--to=francisco.barrera@empelt.es \
--cc=konrad.wilk@oracle.com \
--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).