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

[Xen-users] DomU after migration


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: mail4dla@xxxxxxxxxxxxxx
  • Date: Wed, 13 Jun 2007 18:08:03 +0200
  • Delivery-date: Wed, 13 Jun 2007 09:06:11 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=h1pUYqO7vpiWvEfIZCd97M8JgRQRa9yinXarvuBnkQprOW1zmxksXKLHqwOCVvVxnDA0zDNhpIvtS9YGiK+z77Inu3FbNaZQMMNho2CANJ7zLtp9wqTvaZBeN4SKoTqG+EIirmJ5u4hq/L1Gx6Or3Bbf4Vr0fmrkDT7bpGDbEqI=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello all,

I did some tests with DomU live migration and it worked quite well :-)
However, there remains one question: Is it possible to (reliably) get programatically aware of the DomU's ID on the host it is migrated to?
Could anybody give me a hint how the NIC frontends are created and configured after migration, e.g., are the network scripts called or is a different mechanism invoked?

Regards,
dla
_______________________________________________
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®.