From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Shaun R." Subject: Re: Network issues Date: Tue, 22 Jul 2008 10:22:12 -0700 Message-ID: References: <200807212137.14131.mark.williamson@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200807212137.14131.mark.williamson@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > 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? Yep, thats what's happening. I cant say if it's a issue on the network end or if it has somthing to do with Xen. There are over 300 regular servers on this network though and none of them have this problem, course they are not running Xen. I figured it was a problem with the old xen version i was running (3.0.4) but now i just packaged/deployed newer versions of Xen on hosts and still seeing the problem. It's weird that it doesnt affect the primary ip of the DomU, but only the aliases. ~Shaun