Re: [XenPPC] xend and routes

To:	jimix@xxxxxxxxxxxxxx
Subject:	Re: [XenPPC] xend and routes
From:	poff <poff@xxxxxxxxxxxxxx>
Date:	Mon, 11 Dec 2006 10:52:43 -0500
Cc:	xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Mon, 11 Dec 2006 07:52:38 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<C9D2BAA4-D7EA-4E74-AE17-24BFCFD10E62@xxxxxxxxxxxxxx> (jimix@xxxxxxxxxxxxxx)
List-help:	<mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id:	Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post:	<mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
References:	<45771141.40505@xxxxxxxxxxxxxx> <BF945D59-198C-4339-A5B5-AC4FCDE41671@xxxxxxxxxxxxxx> <200612082324.kB8NONT929848@xxxxxxxxxxxxxxxxxxxx> <C9D2BAA4-D7EA-4E74-AE17-24BFCFD10E62@xxxxxxxxxxxxxx>
Sender:	xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx

> I think the problem is that the bridge favors the default route, so I  
> do not think swapping would work.

On my victim JS21, eth0 is the default, and xen scripts work as written.
However, in this case, DomU accesses the 9.2x network, rather than 192.x


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

Previous by Date:	Re: [XenPPC] xend and routes, poff
Next by Date:	Re: [XenPPC] xend and routes, poff
Previous by Thread:	Re: [XenPPC] xend and routes, Jimi Xenidis
Next by Thread:	Re: [XenPPC] xend and routes, poff
Indexes:	[Date] [Thread] [Top] [All Lists]

WARNING - OLD ARCHIVES

xen-ppc-devel

Re: [XenPPC] xend and routes