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] Network script handling changes

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Network script handling changes
From: Li Ge <lge@xxxxxxxxxx>
Date: Wed, 2 Nov 2005 13:28:09 -0600
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 02 Nov 2005 19:25:18 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051102171948.GD408@xxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Please see bug #381.

Thanks,
Li
Inactive hide details for Ewan Mellor <ewan@xxxxxxxxxxxxx>Ewan Mellor <ewan@xxxxxxxxxxxxx>


          Ewan Mellor <ewan@xxxxxxxxxxxxx>
          Sent by: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

          11/02/2005 11:19 AM


To

Li Ge/Austin/IBM@IBMUS

cc

Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>

Subject

Re: [Xen-devel] Network script handling changes

On Wed, Nov 02, 2005 at 10:50:44AM -0600, Li Ge wrote:

> Ewan,
> I tried the two bridges topology you described below by following the
> exact steps you suggested, but I could not get it work.
>
> [Snip]
>
> Anything that I could have missed in the settings?

No, the settings look right.  Of course, I presume that you have noticed that
my wrapper script is not quite right -- it does not pass the "start" command
through to network-bridge.

Even when you run network-bridge manually, it still hasn't worked though.  Do
you get any error messages in /var/log/debug, /var/log/syslog, etc?  One
obvious problem is that you have no vif0.1 interface, which is the one that
connects from your new eth1 to xenbr1.  I presume that the script is bailing
out early for some reason -- it would be good if you could figure out where it
stops, and why.

Could you open a bug, and attach the output of

brctl show
ifconfig
route
iptables -L

before and after running

/etc/xen/scripts/network-bridge vifnum=0 start
/etc/xen/scripts/network-bridge vifnum=1 start

This should give us good clues to help with the debugging.

Thanks a lot,

Ewan.

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

GIF image

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>