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] xen0=2.6.7 network problem in xenU (SOLVED)

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] xen0=2.6.7 network problem in xenU (SOLVED)
From: James Harper <JamesH@xxxxxxxxxxxxxxxx>
Date: Mon, 23 Aug 2004 22:42:50 +1000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, <Ian.Pratt@xxxxxxxxxxxx>
Delivery-date: Mon, 23 Aug 2004 13:59:25 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1BzBKl-0006Ud-00@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <E1BzBKl-0006Ud-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcSJDrMplLecj43ETfmM7rjObdcrtw==
Thread-topic: [Xen-devel] xen0=2.6.7 network problem in xenU (SOLVED)
I probably should clarify, I can't get xenU to talk on the network in any way (it listens but doesn't talk) when xen0 has the ipv6 module loaded.
 
simply having the ipv6 module there in dom0 seems to break things
 
james


From: Ian Pratt
Sent: Mon 23/08/2004 7:41 PM
To: James Harper
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx; Ian.Pratt@xxxxxxxxxxxx
Subject: Re: [Xen-devel] xen0=2.6.7 network problem in xenU (SOLVED)

> hmmm... loading the ipv6 module caused this problem. I think maybe i've seen that before too.

Our netfront/netback drivers should be transparent to the actual
protocol that you're running over them. 

We've never tested them with ipv6, but I'd be kinda surprised if
they were at fault.

I wander if this is some sort of ipv6 interaction with either the
bridge or ebtables code? I'd wager that they haven't been well
tested with ipv6.
 
> Can someone please test a 2.6.7-xen0 kernel with ipv6 loaded and then a 2.6.7-xenU kernel in another domain and see if they can get any network traffic?

Is it just the act of having the module installed that break
things, or do you need to configure one of the two domains with
an ipv6 interface address? 

Ian