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 issues

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Network issues
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Mon, 21 Jul 2008 21:37:13 +0100
Cc: "Shaun R." <mailinglists@xxxxxxxxxxxxxxxx>
Delivery-date: Mon, 21 Jul 2008 13:37:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <g62mpk$cth$1@xxxxxxxxxxxxx>
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>
References: <g62mpk$cth$1@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.9
That's interesting.  Some clarification seems in order so we can understand 
exactly what your problem is.

On Monday 21 July 2008, Shaun R. wrote:
> I have a weird problem when deploying new hosts.  If i boot a host on a
> normal kernel, then install xen and reboot it and then deploy DomU's for
> some reason eth0 aliases dont work on the DomU's.  The primary ip (main ip
> of the eth0 interface) works fine but for some reason aliases dont work
> until you arping -s <eth0:alias_IP> 0.0.0.0 and then they only work for a
> short time (until arp times out).  The only solution i've found to
> resolving this is too hard reboot the host, and then after that everything
> works as it should.  Anybody else seen anything like this?

OK.  So if I'm reading you right, what you're saying is that you see:

1. boot with normal kernel (networking enabled)
2. reboot into Xen kernel (networking enabled)
3. start domUs
4. IP aliases don't work properly in domUs
5. power cycle the host
6. boot into Xen kernel (networking enabled)
7. IP aliases *do* work properly in domUs?

Is that correct?  Sounds like a fairly weird problem but networks are good at 
creating those :-)

Cheers,
Mark

-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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

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