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
Subject: Re: [Xen-devel] Xen 3.2 bridging broken
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Wed, 13 Feb 2008 11:41:10 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 13 Feb 2008 08:41:37 -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:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=slQQZQs2S7gUnDxnJRL0PnXoHuieZVjQLMqBrPJksEc=; b=SpAFqBHQ0yCteoeYZzee+JDwl+1VJ1SCQ6V8Ll61T2hEJum8rX7Nfr7PH35zfjwAp+ScITprotEjZLN0fe5RQfxYeOvf9vghvkLviUTgUYeTW/T1mJtuCzXreSVxKyS0e+9bdQwgw+Fekx/wijiYaIT0Gq8mTkGBX6dYq2v0kEI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hRabnkynTO8kvq5l4hqNVbr+eyAbj+huuGSPcJMegoySHn9fnwFvpQ1QJmNt6UZjmUtXrnviVPSKRZ6EMcBR1tafq0GJ+XVj4aHgRrzs18vs7hBRgA5kVmVEHfF9f2FNFVgx/kfoohwUaydFhKNX4of/ggNAGbi5JnRa/cNf48w=
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>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

On Feb 13, 2008 12:41 AM,  <pak333@xxxxxxxxxxx> wrote:
>
> Hi
>
> I have 3 nics, 1 onboard nic and 2 other add-in cards. I want to use VT-d to
> hide the add-in nics.
>
> When I boot into Xen, i only see eth0 (the onboard nic).
> The other two nics are hidden from dom0. -------- Great so far....
>
> Now I start xend and behold, it creates xenbr1 and xenbr2. I do NOT want
> those to be created. In fact I   removed the (network-script network-bridge)
> from xend-config.sxp also. but the bridges get created.
> How do I delete them?
>
> 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>
>


ip link set xenbr1 down
brctl delbr xenbr


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


check in ifconfig -a. I have seen in some cases that the hiding
doesn't seem to be fully working.


Regards,
Todd




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

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

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