Xen devel - May 2010 - Network problem after updates

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

Can anybody help me with this problem?


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-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

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

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

Hi Konrad,

unfortunatelly I still have problems... the sames problems with the
network domU Firewall.

Then you propose me to update the dom0 kernel from 2.6.18-164.el5xen to
the latest version, isn''t it?
And update the pv-ops also?

It''s necessary update the domU kernel?

Thanks very much!!




El mar, 15-06-2010 a las 17:21 -0400, Konrad Rzeszutek Wilk escribió:
> 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
> 

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

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?


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

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.


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

On Tue, Jun 22, 2010 at 04:23:13PM +0200, Francisco Barrera
wrote:
> 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.
Well, do the second. Get the ''lspci -vvv'' output of the device
and lets
take a look at what offset 0x4c is? If might be complelty benign at
which point your problem is with something else.
> 
> 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.
Just to make sure I comprehend this properly.
 1). You are running the same software setup you did months ago after
     a brief update.
 2). Your machine freezes. But it did not freeze months ago when you
     ran the same software setup?
> 
> 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.
I am definitly missing something here. You did have a stable version at
some point that did not exhibit any problems, correct? Is that the
version you are running now?

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

El mar, 22-06-2010 a las 10:41 -0400, Konrad Rzeszutek Wilk escribió: 
> On Tue, Jun 22, 2010 at 04:23:13PM +0200, Francisco Barrera wrote:
> > 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.
> 
> Well, do the second. Get the ''lspci -vvv'' output of the
device and lets
> take a look at what offset 0x4c is? If might be complelty benign at
> which point your problem is with something else.


This is the output of ''lspci -vvv'' of the device: 

09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
Subsystem: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (16000ns min), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 19
Region 0: Memory at d2000000 (64-bit, non-prefetchable) [size=32M]
Capabilities: [40] PCI-X non-bridge device
Command: DPERE- ERO- RBC=512 OST=8
Status: Dev=09:00.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=512
DMOST=8 DMCRS=32 RSCEM- 266MHz- 533MHz-
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold
+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-
Address: ffedf9efbfff9fec  Data: de3f

Anything appears in reference of 0x4c, or I don''t understand you.

> > 
> > 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.
> 
> Just to make sure I comprehend this properly.
>  1). You are running the same software setup you did months ago after
>      a brief update.
>  2). Your machine freezes. But it did not freeze months ago when you
>      ran the same software setup?


No, I don''t explain correctly, I''m sorry for my English.
1). The software version running actually is the above I write, 3.1.2 in
xen hypervisor and 2.6.18-194.3.1.el5xen in kernel, that are the
versions by default in CentOS 3.5.
The software version running before the update to xen 3.4.1 was
CentOS-5.2 with Xen 3.0.3 and 2.6.18.128.el5xen kernel.
I''ve installed CentOS 3.5 because I assumed this versions are stables.
2). Now my machine don''t freezes, but I suspect that will freezes when
network traffic overloads some buffer



> > 
> > 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.
> 
> I am definitly missing something here. You did have a stable version at
> some point that did not exhibit any problems, correct? Is that the
> version you are running now?

Ok, I''ve a stable version running now (that cames in CentOS 3.5), and
at
the moment I don''t have any problem, only the message that I comment
above.


--------------------------------------------
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-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Konrad, 
the version that I refer in all my comments is 5.5, not 3.5.
I'' sorry.


El mar, 22-06-2010 a las 10:41 -0400, Konrad Rzeszutek Wilk escribió:
> On Tue, Jun 22, 2010 at 04:23:13PM +0200, Francisco Barrera wrote:
> > 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.
> 
> Well, do the second. Get the ''lspci -vvv'' output of the
device and lets
> take a look at what offset 0x4c is? If might be complelty benign at
> which point your problem is with something else.
> > 
> > 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.
> 
> Just to make sure I comprehend this properly.
>  1). You are running the same software setup you did months ago after
>      a brief update.
>  2). Your machine freezes. But it did not freeze months ago when you
>      ran the same software setup?
> 
> > 
> > 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.
> 
> I am definitly missing something here. You did have a stable version at
> some point that did not exhibit any problems, correct? Is that the
> version you are running now?

--------------------------------------------
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-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel