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

Re: [Xen-users] alternative ways to trigger a domain migration


  • To: mr_ala <mr_ala@xxxxxxxxxxxxx>
  • From: "Tim Wood" <twwood@xxxxxxxxx>
  • Date: Thu, 11 May 2006 13:03:53 -0400
  • Cc: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 11 May 2006 10:04:31 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=nzCph3SkLh8MI9FICfSNp6YN47xgvUVaVxQ94lcyQWczAGdArQ7SDKzKNLSWm0q8uH1lGfdiwd6DRfXkKZAo+zFK6R8jJFqbT/D6ribv2Fyur9tNnPaGC85XQYdoYvbtZB5iLzy80wp3TptmBoaQ+u+sXt88yvzx3fT0VFZoUVM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


On 5/11/06, mr_ala <mr_ala@xxxxxxxxxxxxx> wrote:
Hello

I wonder whether there are other ways than "xm migrate <domainname> ..." to
migrate a domain somewhere else. It would be great if the migration could be
triggered by the domain itself, not from dom0.


From what I understand, this kind of direct communication is not possible. 

On the other hand, the xen commands for doing things like migration are written in python, so if you are willing to get your hands a little dirty you can pretty easily write a server app which runs in domain0 and listens for requests to migrate from the unpriveliged domains.  The server could then run the actual migration commands through the python xen api.
 

Thanks for any hints

Ales Cervenka


_______________________________________________
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

 


Rackspace

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