WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen 3.2 bridging broken

To: "pak333@xxxxxxxxxxx" <pak333@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.2 bridging broken
From: "pradeep singh rautela" <rautelap@xxxxxxxxx>
Date: Wed, 13 Feb 2008 11:45:57 +0530
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 12 Feb 2008 22:16:20 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=1rU7rhm59GaUPs/hMKa8ruae/ZleLChCogq67GFq9qM=; b=GRIPeau81CFvO7cLgPhHuRHibGx29C4n4sar279JOb0ZAEs9vdc14FtSbn15IXXDWZuGiD9eoj5wWpnbGs8K2tCt7nFM5j+yc+DWRqa7y1PW/ISBaZUKqAmIc2BhHXJlyT5dYaA5eqqNByZvlf3Y0h+/53QALZfbP3IkC6adoNk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=vcjFIDc4VZS9oCcwSraWzPHQgk+/3TTgmTTrD/ArXEAKz2/eG07fog5XDf3HqhXJqqNDCS/SKW5VYQzNGdbS7Dt81yhWmBmsVgAtYJDUOUpT5o5vM5VMskl8w3KVG8DssinYW2fQkYoID43QFULQYC6tJw7iCSm58NFWtvFkrGE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <021320080541.13147.47B283250007497F0000335B2213539653CCCCCC050E9F@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <021320080541.13147.47B283250007497F0000335B2213539653CCCCCC050E9F@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[...]
>
> brctl shows
>
> bridge name   bridge id                              STPenabled
>          interfaces
> xenbr0        8000.000000000000                 no
> xenbr1        8000.000000000000                 no
> xenbr2         8000.000000000000                 no
>
> if i do "brctl delbr xenbr1"
> >xenbr1 is still up: can't delete it.
> and ifdown xenbr1
> > <usage> ifdown <device name>
>
> So basically i can't get rid of xenbr1 and xenbr2. ( never needed them in
> the first place). and it appears that xenbr1 and xenbr2 are tied to the two
> add-in nics and hence the guest cannot use those nics.
>
> Questions: Is there a simple way to tell Xend NOT to create any bridges? It
> is picking the interfaces from somewhere?

it picking them up from /etc/xen/scripts/* by using network-bridge and
vif-bridge scripts.You can replace them with your own scripts in
xend-config.sxp for invocation.

HTH

Thanks,
          --Pradeep
>
> Thanks in advance for your help
> -Prabha
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>


-- 
Pradeep Singh Rautela
http://eagain.wordpress.com
http://emptydomain.googlepages.com

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

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