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] Set up bridging under Xen 4.1-unstable ( 2.6.31.15 pvops

To: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Set up bridging under Xen 4.1-unstable ( 2.6.31.15 pvops) on top of Ubuntu 10.04 Server
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Wed, 7 Jul 2010 12:11:36 -0700 (PDT)
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Wed, 07 Jul 2010 12:12:32 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1278529896; bh=6Gb0IU2aeIPIiHmvLXoq1RFw292W8fR7d3OaDt5kCwc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=E8jt72p4kwI+7PYCHQfWvaYfRJrQCR5lwjRsmocT92WpXda/U+d/uf8H1jtrk0RkiZSfEukV2jC65i0rWRnZapAaEGuJusxxRLmURTfzo5V1MYqg3xcYdkn75HyvS16G4IKrl/pLIKfvN/vFYp8d2cFvU6sI4u+8pPAQwqjKmxw=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=1jrMeuhzYbHXu2sXNujH+eibUGrgEdROvyu14afKOmlGiacx7Qge6kD+dRPdKwu6hcr6xZlcFqHcJuGO5rkAgJaxju6CFU50c5ZHhNmez6ZH8gMPjpPpVtX2gp1tdQr5Xj3hNO6M0odO0F0UpLZhZqGcVrc0Gfazte1gp7SIMNg=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <585229779.20100707202124@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Sander,

  I believe,  my question is a bit different . I can work with br0 with no problems
  for DomUs networking.
  Up to 4.0.1 i could define bridge in /etc/xen/xend-config.sxp and get this bridge
  reported by "brctl show" , but now i cannot do that. Seems like manual intervention
  in Ubuntu /etc/network/interfaces is required.

Boris.

--- On Wed, 7/7/10, Sander Eikelenboom <linux@xxxxxxxxxxxxxx> wrote:

From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Set up bridging under Xen 4.1-unstable ( 2.6.31.15 pvops) on top of Ubuntu 10.04 Server
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
Date: Wednesday, July 7, 2010, 2:21 PM

Hello Boris,

Dont the default vif scripts connect to xen_br0 and not br0 ?
I specify a different bridge name in the domU config files vif line with bridge=

--
Sander


Wednesday, July 7, 2010, 7:57:13 PM, you wrote:

> After services
>  1.xencommons
>  2.xend
>  3.xendomains
> startup  xen bridge declaration via /etc/xen/xend-config.sxp completely ignored.

> Bridging setup manually via /etc/network/interfaces :-

>  # The loopback network interface
> auto lo
> iface lo inet loopback

> # The primary network interface
> # auto eth0
> # iface eth0 inet dhcp
>  auto br0
>  iface br0 inet static
>          address 192.168.1.7
>          netmask 255.255.255.0
>          network 192.168.1.0
>          broadcast 192.168.1.255
>          gateway 192.168.1.1
>          bridge_ports eth0
>          bridge_stp on
>          bridge_maxwait 0

> # /etc/init.d/networking restart

> Am i missing something here ?

> Boris.




>       



--
Best regards,
Sander                            mailto:linux@xxxxxxxxxxxxxx


_______________________________________________
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