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 00:04:47 +0800
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 02 May 2011 09:07:02 -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=NQ9TeGMzo9mRKLFUpnkjR6szobmyVAGr+RTyzZTAiZE=; b=psovV+ksgBBTgRaVQQH1M1e3cMB6wcnzigstvNp34TlT+2jbfhGppIZpXEs8rlCQ5c qjqm9rIFJ+0OoVExoCPTAG/E+EAoj3VYsItMICwSBL67BXkbmls4t88xNUUZLecxvvWH vHp2f3+MP0QgD6zCpoOpwHG5jzsiA1fzZ7BoU=
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=Mcex1ndzjFyye/2WXzI63dOrfeKI5HTbWioRkdda2tNlELLiviaqpDR0CnErzGSxY6 WPVglh+i1K05PEU3HoMFAhFVBs8Z7NABxs1yLr5gV88NUQdUOviVARLtNu+xSxwW48vX frZEXUtKBe5Ki8txGwCpxiYV0h6KxJdVRnfWM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DBCED01.6050400@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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Sun, May 1, 2011 at 1:17 PM, Digimer <linux@xxxxxxxxxxx> wrote:
> On 05/01/2011 12:53 AM, Teck Choon Giam wrote:
>> On Sun, May 1, 2011 at 10:04 AM, Digimer <linux@xxxxxxxxxxx> wrote:
>>> On 04/30/2011 08:47 PM, Teck Choon Giam wrote:
>>>> Pasi is right about to use system network configuration so that xend
>>>> and system network are separated.  Can you explain how it was bugged?
>>>> Is it sometimes get set and sometimes not?  Have you try to give a
>>>> small sleep interval such as 3 seconds before setting the related mtu?
>>>> Thanks.
>>> Sure.
>>>  I've got three interfaces in my server;
>>> - eth0; Internet-facing, bridged as xenbr0
>>> - eth1; Storage network, not bridged or used by any domU.
>>> - eth2; Back-channel/internal network, bridged as xenbr2, used by some domU.
>>>  I had a patch[1] in xen-network-common.sh's setup_bridge_port()
>>> function that would look at the $dev passed in, parse it and pull the
>>> MTU from the corresponding bridge. The bug was that this $dev matched
>>> the ethX device in the domU rather than the bridge, so when the second
>>> interface (xenbr2 <-> domU's eth1) would look for the MTU of 'xenbr1',
>>> which didn't exist.
>> Your domUs are all HVM or PV or both in mix with the same problem?
>> Thanks.
>> Kindest regards,
>> Giam Teck Choon
> They're a mix, and the issue was across the board.

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?


Kindest regards,
Giam Teck Choon

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>