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-users

RE [Xen-users] Re: xen-3.0.4 networking problem after migration

To: "Weikuan Yu <weikuan.yu" <weikuan.yu@xxxxxxxxx>
Subject: RE [Xen-users] Re: xen-3.0.4 networking problem after migration
From: Alain BARTHE <alain.barthe@xxxxxxxx>
Date: Tue, 19 Feb 2008 09:29:12 +0100
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx, xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 19 Feb 2008 00:29:53 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47BA698E.1020300@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

xen-users-bounces@xxxxxxxxxxxxxxxxxxx a écrit sur 19/02/2008 06:30:54 :

> I reply to my post earlier. It was a problem on the configuration file.
> It appears that, when not using dhcp, live migration with static mac
> address would cause a problem to IP in migrated domU.


We are also using xen 3.0.x, we are not using DHCP, we have static MAC address in our domU, and we never encountered such a problem in live migrations.

Maybe another explanation ?

>
> --Weikuan
>
> Weikuan Yu wrote:
> > Hello,
> >
> > I am facing an networking problem for xen migration. I used to have it
> > working fine. But as I worked with several trees, I lost track on the
> > correct configuration I should have.
> >
> > The problem is as this, with xen-3.0.4 on CentOS-4.4. I can install xen,
> > start xend, and create domU, all fine.
> > # xend start (on both nodes)
> > # ssh node02 xend start
> >
> > Then create a domU on node01
> > # xm create -c cvm.01
> >
> > At this point, I can ping this domU from many different nodes in the
> > subnet. Then, I migrate it to node02
> > # xm migrate cvm.01 -l node02
> >
> > Right after the migration, I can no long ping the domU. This domU now
> > can only be ping'ed from the new host, node02. Interestingly, if I
> > migrate the same domU back to node01. Pinging works fine again from many
> > different nodes.
> >
> > Anybody has seen this before? I know xen-3.0.4 is old by now. But want
> > to avoid a new installation if possible.
> >
> > Can somebody offer a hint? Any help is appreciated.
> >
> > -- Weikuan
> >
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users