[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] xen-3.0.4 networking problem after migration


  • To: Xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Weikuan Yu <weikuan.yu@xxxxxxxxx>
  • Date: Mon, 18 Feb 2008 14:56:34 -0500
  • Delivery-date: Mon, 18 Feb 2008 11:56:57 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=np0kb4FqPBG7rBebQek4Pk6lTgXQi00MS6f0XZMEgaup7H4dPgKy/ZGZtP8FT1A/nq5n/XZzWKLpfZEtD5luGTTVEME74KeY9upiBxPvIXNfD0dAkTjqAzWABBE/Bp9mqZPNhHEd6SXVt64a90/6Q9MoP/jSJ1JX+DxUogBcyZg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.