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

[Xen-users] migration questions

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] migration questions
From: "Alan Greenspan" <alan@xxxxxxxxxxx>
Date: Mon, 23 May 2005 09:51:54 -0400
Delivery-date: Mon, 23 May 2005 13:53:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Organization: egenera
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Is there a plan for adding security to migration?  It appears that one can push a domain to any Xen enabled host on the same subnet, thus gaining access to its block devices, etc on the destination host.   It would be reasonable to have a xen.hosts.migrate.allow type file to grant access to hosts wishing to migrate domains into the local machine.
 
It might be useful to have "pre-migrate" mechanism that would validate the resources necessary to migrate a domain.   This might send the domain config to the remote host and receive a descriptor detailing the load on the host and the viability of mem/devices needed to perform the migrate.   This would help build clustering capabilities where a migration choice could be made based on load/resources.
 
After a successful migrate, there appears to be no persisted domain config on the destination.   Seems like there should be a means to have the destination persist the config automatically on a successful migration, so that on host reboot or failure/recovery of the destination host, the migrated domain config is available.   Without an automatic persist of the config, there might be a window where a domain could be lost (crash before an admin has a chance to observe the successful migrate and can extract or copy the config to the destination).
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] migration questions, Alan Greenspan <=