This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Trouble with manual bridging on Xen3/CentOS 5

To: Digimer <linux@xxxxxxxxxxx>
Subject: Re: [Xen-users] Trouble with manual bridging on Xen3/CentOS 5
From: Teck Choon Giam <giamteckchoon@xxxxxxxxx>
Date: Tue, 3 May 2011 01:33:18 +0800
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 02 May 2011 10:34:41 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=dg+4fc3ZH7eSV3aSVpo8IPF4soPynJnBp3cmq19zOcc=; b=pLIAc7fhurX8mlYVfuM99tr/d3Rf2XIGSeYGWRqaJVh87TqHMUhevUynkJeCEhfr7M WHlggOviyHHv59OdlqshOKAGEFcNgp/M+t2adNCC50oZBLXi3vZmbWApwa6NW8N6wYRu Ppqf2aJZSJy+SzhKbgwb+LXzClEVHoQypzUSQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=bw04K+H6UW5jyg1CUWM0LCuJvC4Yd8S1CvP7dQVWwT4wc5sR0fH2Y78pxj606TZGED xhH+TBffp+mMaS+EiO8XI/AUyarSXuFSJrlV2SzMLFxVJU7s4F10yzxytOyWJdsq+M3C Vdd7wDymWX0xHA5QbNiC/oxUaQmiJLnC5vefk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DBED778.2070008@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4DBB36EA.2030202@xxxxxxxxxxx> <BANLkTimE1YDM86_rYj6PHWqgDyRa1gQoHw@xxxxxxxxxxxxxx> <4DBC3DCE.4060206@xxxxxxxxxxx> <BANLkTi=Gjp7OdfTyF7DE9SVZ3uFn2W5uxA@xxxxxxxxxxxxxx> <4DBC7FE2.8010609@xxxxxxxxxxx> <BANLkTin0YEz0HDvnGYJ4Dt5pWRAGeaR61Q@xxxxxxxxxxxxxx> <4DBCBFB5.7070700@xxxxxxxxxxx> <BANLkTikZFwijVaz-N+i_dWvJKMee7NUsug@xxxxxxxxxxxxxx> <4DBCED01.6050400@xxxxxxxxxxx> <BANLkTikVvssbsifOJqOzzCfyuak_MW5d_Q@xxxxxxxxxxxxxx> <4DBED778.2070008@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, May 3, 2011 at 12:10 AM, Digimer <linux@xxxxxxxxxxx> wrote:
> On 05/02/2011 12:04 PM, Teck Choon Giam wrote:
>> Ok, mind to show me your brctl show output?  I am curious about what
>> is the vif?.? assignment to your xenbr2 especially.  It is either
>> vif?.1 or vif?.2.  Have you tried with vifname set in your domU
>> configs to see whether the same problem persist?
>> Thanks.
> To get that info, I'd need to reconfigure a test cluster with the bugged
> patch. If it's curiosity only, I'd like to set it aside. If it could
> help with development though, let me know and I'll do so tonight.

Curious only though but that might helps to determine one or more of
your patches issue.  One of your patch at least is using vif?.N to get
its physical ethN if I am not mistaken:


pdev=`echo $dev | sed -e "s/^vif\(.*\)\.\(.*\)$/peth\2/"`

So if $dev is vif?.N here, the pdev will be pethN right?  However,
since you are using system network configuration to configure your
bridge, your physical ethN remain the same as it is and there isn't
any pethN here I believe.  Correct me if I am wrong though :p

And your next line is:

mtu=`cat /sys/class/net/$pdev/mtu`

So if $pdev not set or empty or pethN not found, you will have issue here... ...

Now let said you are using xen provided to do the bridging instead of
using system network configuration... so pethN will be set by xen or
rename real ethN to pethN and setup bridge name as ethN if I remember
correctly... ... now if vif?.N where N is 1 for your xenbr2/peth2 you
will have issue as well :p

You might want to try setting vifname for your testing domU config to
see whether does it resolve your issue?

I haven't look closely for your other patches though and what I stated
above hopefully make sense :p


Kindest regards,
Giam Teck Choon

Xen-users mailing list