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

[Xen-devel] Network issues

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Network issues
From: "Shaun R." <mailinglists@xxxxxxxxxxxxxxxx>
Date: Mon, 21 Jul 2008 11:52:39 -0700
Delivery-date: Mon, 21 Jul 2008 12:08:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
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?

~Shaun


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

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