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-devel] Re: [Xen-bugs] Re: Network problem after updates
Date: Wed, 16 Jun 2010 11:50:13 -0400 [thread overview]
Message-ID: <20100616155013.GA3674@phenom.dumpdata.com> (raw)
In-Reply-To: <1276701879.4051.12.camel@portatil-1>
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?
next prev parent reply other threads:[~2010-06-16 15:50 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 ` Konrad Rzeszutek Wilk [this message]
2010-06-22 14:23 ` Re: [Xen-bugs] " 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=20100616155013.GA3674@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).